[ https://issues.apache.org/jira/browse/AMQ-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266117#comment-17266117 ]
Matt Pavlovich commented on AMQ-1126: ------------------------------------- Closing this issue due to inactivity. To re-open, please test with 5.16.1 or newer. > The Resource Adapter ignores the JMSXGroupID when dispatching to MDBs > --------------------------------------------------------------------- > > Key: AMQ-1126 > URL: https://issues.apache.org/jira/browse/AMQ-1126 > 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 > Assignee: Matt Pavlovich > Priority: Major > Labels: close-pending > Fix For: NEEDS_REVIEW > > Attachments: amq_reproducer.zip, msg-group-test.zip > > > 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 was sent by Atlassian Jira (v8.3.4#803005)