Bug 778896 (SOA-1338)

Summary: Queue configuration for JBPM missing
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: trev <tkirby>
Component: JBPM - within SOAAssignee: Alejandro Guizar <alex.guizar>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 CP01   
Target Milestone: ---   
Target Release: 4.3 CP02   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1338
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-25 10:42:26 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:
Bug Depends On: 778868    
Bug Blocks:    

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.