Bug 778896 (SOA-1338) - Queue configuration for JBPM missing
Summary: Queue configuration for JBPM missing
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-1338
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBPM - within SOA
Version: 4.3 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP02
Assignee: Alejandro Guizar
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On: SOA-1310
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-28 10:18 UTC by trev
Modified: 2009-08-25 10:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-25 10:42:26 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1338 0 None None None Never

Description trev 2009-05-28 10:18:47 UTC 
Date of First Response: 2009-06-12 12:13:10
project_key: SOA

The default configuration in the jbpm-jpdl-3.2.5SP5 package only contains the queue configuration for JBossMQ in /deploy/server/default/deploy/jbpm/jbpm-destinations-service.xml file.

This breaks the deployment on JBoss EAP 4.3 which comes with JBM. An alternative config file should be included in the distribution:

 <mbean code="org.jboss.jms.server.destination.QueueService"
    name="jboss.mq.destination:service=Queue,name=JbpmJobQueue"
    xmbean-dd="xmdesc/Queue-xmbean.xml">
    <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
  </mbean>
  
 <mbean code="org.jboss.jms.server.destination.QueueService"
    name="jboss.mq.destination:service=Queue,name=JbpmCommandQueue"
    xmbean-dd="xmdesc/Queue-xmbean.xml">
    <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
  </mbean>
Comment 1 trev 2009-05-28 10:19:12 UTC 
Link: Added: This issue depends JBPM-2288
Comment 2 Len DiMaggio 2009-06-12 16:13:10 UTC 
From an IRC chat with Alejandro:

<aguizar> ldimaggi_: it does not affect an installation that uses the job executor
<aguizar> ldimaggi_: it would only affect one that used JMS

Accordingly, linking this as being dependent on SOA-1310
Comment 3 Len DiMaggio 2009-06-12 16:13:22 UTC 
Link: Added: This issue depends SOA-1310
Comment 4 Kevin Conner 2009-06-17 15:20:14 UTC 
There is no need to do this if we are going with the ESB inflow integration as we define our own queues, albeit with the same names.

We are defining the following

    <mbean code="org.jboss.jms.server.destination.QueueService"
           name="jboss.esb.destination:service=Queue,name=JbpmJobQueue"
           xmbean-dd="xmdesc/Queue-xmbean.xml">
        <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
    </mbean>
    <mbean code="org.jboss.jms.server.destination.QueueService"
           name="jboss.esb.destination:service=Queue,name=JbpmCommandQueue"
           xmbean-dd="xmdesc/Queue-xmbean.xml">
        <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
    </mbean>
    <mbean code="org.jboss.jms.server.destination.QueueService"
           name="jboss.esb.destination:service=Queue,name=JbpmDLQ"
           xmbean-dd="xmdesc/Queue-xmbean.xml">
        <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
    </mbean>
Comment 5 Julian Coleman 2009-08-25 10:42:26 UTC 
We are using the ESB inflow integration solution for 4.3 CP02, so this is no longer an issue.
Note You need to log in before you can comment on or make changes to this bug.