Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1133879

Summary: JMS queues already exist
Product: [Retired] JBoss BPMS Platform 6 Reporter: Ivo Bek <ibek>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED WORKSFORME QA Contact: Ivo Bek <ibek>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.2CC: ibek, jholmes, kverlaen, smcgowan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-04 08:47:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
server log none

Description Ivo Bek 2014-08-26 11:25:43 UTC 
Description of problem:

When I first time start BPMS 6.0.3.ER1 I get a few exceptions in the server log saying the JMS queues already exist.

JMS API works, however this should not happen.

13:06:52,816 ERROR [org.hornetq.core.server] (Thread-2 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.SESSION]

13:06:52,835 ERROR [org.hornetq.core.server] (Thread-2 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.TASK]

13:06:53,071 ERROR [org.hornetq.core.server] (Thread-6 (HornetQ-remoting-threads-HornetQServerImpl::serverUUID=f02adfe5-2d07-11e4-9518-8f6f55d2038b-446685093-1981011786)) HQ224016: Caught exception: HornetQException[errorType=QUEUE_EXISTS message=HQ119019: Queue already exists jms.queue.KIE.AUDIT]

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Ivo Bek 2014-08-26 11:27:01 UTC 
Created attachment 930826 [details]
server log
Comment 2 Kris Verlaenen 2014-08-26 11:54:38 UTC 
Is this breaking any functionality or is this an error message that shouldn't be there only?
Comment 3 Ivo Bek 2014-08-26 12:22:38 UTC 
Kris, AFAIK it does not break anything. I will add a comment if it changes. Right now, it just does not look nice in the server log.
Comment 4 Justin Holmes 2014-09-10 20:23:12 UTC 
I am experiencing the same issue on BPMS 6.0.2.GA. It appears to happen after periods of inactivity on the server. It causes sharp CPU spike and very slow reaction time when the error occurs in the log which is very noticeable to the end user. Server log attached as Holmes_server.log.
Comment 5 Justin Holmes 2014-09-10 20:25:51 UTC 
Created attachment 936320 [details]
Holmes_server.log
Comment 6 Marco Rietveld 2014-09-17 11:45:14 UTC 
Justin, could you attach the full server log? (startup to shutdown)

Thanks!
Comment 7 Justin Holmes 2014-09-18 02:21:37 UTC 
Created attachment 938714 [details]
Logs For Days
Comment 12 Ivo Bek 2016-01-04 08:47:19 UTC 
Works well in the current releases 6.1.0 and 6.2.0, hence closing this issue.