activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharath Komarla (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1126) The Resource Adapter ignores the JMSXGroupID when dispatching to MDBs
Date Thu, 20 Nov 2008 23:49:05 GMT

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

Sharath Komarla commented on AMQ-1126:
--------------------------------------

Man.. I'm so glad I stumbled on this issue. I've been pulling my hair out over this.  I use
JBoss 4.2.2 with the 5.1.0 activemq rar and I see that the RA completely ignores the group
id.  we are using spring's jms:listener-container and not MDB's, but I see the exact same
behavior.  I even have a unit test that exhibits this behavior using an vm://localhost broker
on 5.1.0 and RC3 of 5.2.0

Based on the last comment from John,  I agree that the MDB container/spring container is real
endoint of the queue and I don't care which MDB instance the message is delagated to, but
the container should respect the grouping!

> 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
>             Fix For: 5.3.0
>
>
> 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.


Mime
View raw message