activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "farheen (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-1126) The Resource Adapter ignores the JMSXGroupID when dispatching to MDBs
Date Fri, 10 Feb 2012 14:26:59 GMT


farheen commented on AMQ-1126:

I too am facing the same issue with implementing message grouping with JBoss 4.0.3 and ActiveMQ
5.4.3. I have  addded the JMSXGroupID to the JMS mesage being sent from the producer. Also
added below line in the broker-config.xml 

<policyEntry queue=">" consumersBeforeDispatchStarts="5" timeBeforeDispatchStarts="5000"

But when i try to send 2 groups of messages each group haing 5 messages each from a client,
I find that the messages are consumed by differernt consumers(COnsumer in my case is an MDB
 deployed in JBoss server. ActiveMQ started when JBoss starts). There are differernt instances
of MDBs created for each message and all are processed in parallel. 

Altho' I expected that the messages in 1 group be processed by one particular consumer .i.e.
one instance of MDB. 

Can you please help me out. I cant understand what I might be doing incorrectly here 

> The Resource Adapter ignores the JMSXGroupID when dispatching to MDBs
> ---------------------------------------------------------------------
>                 Key: AMQ-1126
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JCA Container
>    Affects Versions: 4.0.1
>         Environment: Java 1.4.2_08
> JBoss 4.0.4
> ActiveMQ 4.0.1
>            Reporter: John Robinson
>             Fix For: NEEDS_REVIEWED
>         Attachments:
> Integrate AMQ into JBoss using the data source, and resource adapter.  Create an outbound
queue and an MDB with a pool size of 100.  Dispatch several messages to the outbound queue,
setting the JMSXGroupID property on the message to be the same value each time.  In the MDB's
onMessage method print out the MDBs toString (don't override toString) and you should see
something that looks like:
> OutQueueProcessorBean@19a7266
> Observe two things:
> a) Many messages are processed in parallel
> b) Many different values will occur after the @ in the above message, denoting that more
than on MDB instance is being handed messages.
> The correct behavior would be to dispatch messages with the same group id to the same
MDB instance in sequence.  This would allow messages from different groups to be processed
in parallel, but messages in any one group would be processed serially, in the order in which
they were placed into the queue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message