You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jason Carreira (JIRA)" <ji...@apache.org> on 2008/05/27 18:15:02 UTC
[jira] Created: (AMQ-1750) Message Groups: Not working with Mule
2.0.1 feeding AMQ 5.1
Message Groups: Not working with Mule 2.0.1 feeding AMQ 5.1
-----------------------------------------------------------
Key: AMQ-1750
URL: https://issues.apache.org/activemq/browse/AMQ-1750
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.1.0
Environment: Mule 2.0.1 feeding AMQ 5.1
Reporter: Jason Carreira
I was trying to use Mule 2.0.1 to read a directory and feed the file contents into an AMQ 5.1 Queue. The issue is that I need to handle files with the same first part of the file name (before the extension) serially so as to not have race conditions and optimistic concurrency exceptions. Therefore I built a special Transformer to transform the Object I built from the file into a JMS message which sets the JMSXGroupID property. When running all in one process, I see it finding the groupID and looking up the consumer, but when I run it on 3 processes (feeder, AMQ, and processor) the messages are getting read by different consumers / Threads and I get concurrent modification exceptions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1750) Message Groups: Not working with Mule
2.0.1 feeding AMQ 5.1
Posted by "James Strachan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Strachan resolved AMQ-1750.
---------------------------------
Resolution: Won't Fix
It looks like this isn't a bug in ActiveMQ from this thread
http://www.nabble.com/Message-Groups%3A-Not-working-with-Mule-2.0.1-feeding-AMQ-5.1-tp17493075s2354p17495601.html
as setting zero for the sequence ID effectively closes the message group (so that the message can be dispatched to any consumer since each message is always the start of a *new* message group).
The work around is to remove the sequence ID or use some non zero value
> Message Groups: Not working with Mule 2.0.1 feeding AMQ 5.1
> -----------------------------------------------------------
>
> Key: AMQ-1750
> URL: https://issues.apache.org/activemq/browse/AMQ-1750
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: Mule 2.0.1 feeding AMQ 5.1
> Reporter: Jason Carreira
>
> I was trying to use Mule 2.0.1 to read a directory and feed the file contents into an AMQ 5.1 Queue. The issue is that I need to handle files with the same first part of the file name (before the extension) serially so as to not have race conditions and optimistic concurrency exceptions. Therefore I built a special Transformer to transform the Object I built from the file into a JMS message which sets the JMSXGroupID property. When running all in one process, I see it finding the groupID and looking up the consumer, but when I run it on 3 processes (feeder, AMQ, and processor) the messages are getting read by different consumers / Threads and I get concurrent modification exceptions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.