activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich (JIRA)" <>
Subject [jira] Commented: (AMQ-1126) The Resource Adapter ignores the JMSXGroupID when dispatching to MDBs
Date Wed, 12 Aug 2009 19:06:35 GMT


Rich commented on AMQ-1126:

I don't believe this is fixed with issue 2016.  I have downloaded the latest SNAPSHOT of 5.3
specifically for that issue since it was fixed in that release.  I was able to see using a
simple producer/consumer, that message groups did work as advertised.  My consumer created
10 threads much like JBoss would do by default and create 10 instances of an MDB.  It just
seems that message groups aren't working with JBoss 4.2.2 at least, I have tried any other
version of JBoss.  I even noticed that the workaround discussed in issue 2016 doesn't work
either (starting the consumers before any messages on the queue).  The workaround worked fine
for the simple producer/consumer case, but just doesn't work with JBoss.  Has anyone looked
into this?

> 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: 5.4.0
>         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.
You can reply to this email to add a comment to the issue online.

View raw message