[jira] Commented: (AMQ-1126) The Resource Adapter ignores the JMSXGroupID when dispatching to MDBs

["anish pathadan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/AMQ-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39928 ] 

anish pathadan commented on AMQ-1126:
-------------------------------------

Hi,
    In this case the Message Listener is the MDB container not the individual MDB instances. MDB container is free to select any mdb instance to process the message it received.So I think  the JMSXGroupID has no significance here. I feel this is not a bug and can be closed. 

What is the opinion of others?.

Best Regards,
Anish Pathadan

> The Resource Adapter ignores the JMSXGroupID when dispatching to MDBs
> ---------------------------------------------------------------------
>
>                 Key: AMQ-1126
>                 URL: https://issues.apache.org/activemq/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
>
> 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.