Red Hat Bugzilla – Bug 977382
Missing queues for JMS remote API
Last modified: 2016-09-20 01:04:43 EDT
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.
<!-- general session, task, response -->
<entry name="queue/KIE.SESSION.ALL" />
<entry name="java:jboss/exported/jms/queue/KIE.SESSION" />
<entry name="queue/KIE.TASK.ALL" />
<entry name="java:jboss/exported/jms/queue/KIE.TASK" />
<entry name="queue/KIE.RESPONSE.ALL" />
<entry name="java:jboss/exported/jms/queue/KIE.RESPONSE" />
<!-- wildcard session, task, response -->
<entry name="queue/KIE.SESSION" />
<entry name="queue/KIE.TASK" />
<entry name="queue/KIE.RESPONSE" />
Version-Release number of selected component (if applicable):
Steps to Reproduce:
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?
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.
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.
Created attachment 781020 [details]
Fixed with the following commit on the 6.0.x branch of the kie-wb-distributions repository:
Verified on ER2.