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

Bug 977382

Summary: Missing queues for JMS remote API
Product: [Retired] JBoss BPMS Platform 6 Reporter: Ivo Bek <ibek>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED CURRENTRELEASE QA Contact: Ivo Bek <ibek>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: ibek, mbaluch, mrietvel, rzhang, smcgowan
Target Milestone: ER2   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:07:09 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
bpms-jms.xml none

Description Ivo Bek 2013-06-24 12:25:24 UTC 
Description of problem:

The RequestMessageBean (https://github.com/droolsjbpm/droolsjbpm-integration/blob/master/kie-remote/kie-services-remote/src/main/java/org/kie/services/remote/jms/RequestMessageBean.java) uses following queues which aren't in standalone-full.xml where I would expect them.

<jms-destinations>
      
      <!-- general session, task, response -->
      <jms-queue name="KIE.SESSION">
        <entry name="queue/KIE.SESSION.ALL" />
        <entry name="java:jboss/exported/jms/queue/KIE.SESSION" />
      </jms-queue>
      <jms-queue name="KIE.TASK">
        <entry name="queue/KIE.TASK.ALL" />
        <entry name="java:jboss/exported/jms/queue/KIE.TASK" />
      </jms-queue>
      <jms-queue name="KIE.RESPONSE">
        <entry name="queue/KIE.RESPONSE.ALL" />
        <entry name="java:jboss/exported/jms/queue/KIE.RESPONSE" />
      </jms-queue>
      
      <!-- wildcard session, task, response -->
      <jms-queue name="KIE.SESSION.#">
        <entry name="queue/KIE.SESSION" />
      </jms-queue>
      <jms-queue name="KIE.TASK.#">
        <entry name="queue/KIE.TASK" />
      </jms-queue>
      <jms-queue name="KIE.RESPONSE.#">
        <entry name="queue/KIE.RESPONSE" />
      </jms-queue>
      
</jms-destinations>

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Marco Rietveld 2013-06-26 08:35:51 UTC 
Ivo, we expect users to manage jms queues themselves. 

The documentation for the REST/JMS services will include what queues users should set up. Unfortunately, this documentation has not been completed yet. 

Would it be okay to close this bug as a NOTABUG?
Comment 2 Ivo Bek 2013-06-26 14:20:24 UTC 
Marco, personally I think the queues belong to the standalone-full.xml profile since it's the FULL profile. And the documentation can contain just information about them in standalone-full.xml and a user will copy the queues when he needs them in another profile but he has still the choice to start the full BPMS with all the abilities, which can offer. So, I would let the decision on PM what they prefer.
Comment 3 Marco Rietveld 2013-06-28 15:00:17 UTC 
Hi Ivo, that seems like a reasonable request. I've started talking to Julian and Doug about how the B*MS servers are configured and made them aware that the queues need to be created. 

Unfortunately, they are still in the process of creating the (server configuration) component that would create these JMS queues. Once that component has been created (in a couple weeks?), I'll let you know.
Comment 7 Ryan Zhang 2013-07-31 09:01:05 UTC 
Created attachment 781020 [details]
bpms-jms.xml
Comment 8 Marco Rietveld 2013-08-01 11:23:46 UTC 
Fixed with the following commit on the 6.0.x branch of the kie-wb-distributions repository: 

https://github.com/droolsjbpm/kie-wb-distributions/commit/2bd914024f7e8bd8ecd04ac10bb1548a78c0e983
Comment 9 Marek Baluch 2013-09-05 10:01:16 UTC 
Verified on ER2.