activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mohan pindyala (Commented) (JIRA)" <>
Subject [jira] [Commented] (AMQ-1126) The Resource Adapter ignores the JMSXGroupID when dispatching to MDBs
Date Thu, 02 Feb 2012 01:39:53 GMT


mohan pindyala commented on AMQ-1126:

we are in a similar situation .

we have network of brokers

Producers send to Broker 1,2 and 3
Brokers 1,2,3 forward messages to Broker 4

We are using apachemq 5.5  Spring DMLC for listeners .
Broker 1,2,3 are hosted within tomcat container

Consumers consume from Broker 4

we have three consumers each receiving only a specific groupId using message selector expressions
JMSXGroupID='0' for consumer1
JMSXGroupID='1' for consumer2
JMSXGroupID='2' for consumer3

Producers tag these messages with JMSXGroupID and forward that to broker 4.

Issue is we are seeing  messages tagged with JMSXGroupID '0' are ending up in consumer2 or
cosumer3,or JMSXGroupID '1' endign up in consumer 0 or 3

when cut down our consumers to 2 and tag messages with 0 or 1 it works like a charm.

Can any help us with this issue?

> 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