activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan (JIRA)" <>
Subject [jira] Resolved: (AMQ-1750) Message Groups: Not working with Mule 2.0.1 feeding AMQ 5.1
Date Sun, 01 Jun 2008 05:34:00 GMT


James Strachan resolved AMQ-1750.

    Resolution: Won't Fix

It looks like this isn't a bug in ActiveMQ from this thread

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

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:
>             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.

View raw message