Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of rajdavies@gmail.com
 designates 66.249.92.168 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer;
        b=gW7OuEQmEMTh0G3YMwmMMLNhQQW3kAw01VD8urNnSWRS3dCIOpFclc0CozTDua7XB95A7V5RpAawkVx/a4Rw5f5KK0HNkMCbwUU8zwQJzv1VQG42VQik554ei+1OPQULR4BLZ0G1PfzXijzJh86uHKb+6BG1JRsgvrhOEC9PCx4=
Message-Id: <F97A10E1-6CB9-492C-BC0C-D8BC939FE9ED@gmail.com>
From: Rob Davies <rajdavies@gmail.com>
To: users@activemq.apache.org
In-Reply-To: <17495601.post@talk.nabble.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: Message Groups: Not working with Mule 2.0.1 feeding AMQ 5.1
Date: Tue, 27 May 2008 19:01:55 +0100
References: <17493075.post@talk.nabble.com>
 <74e15baa0805270917w256aabfcn107194c943c0e330@mail.gmail.com>
 <17495601.post@talk.nabble.com>


On 27 May 2008, at 18:18, jcarreira wrote:

>
> I have no idea what the problem is... It could be something in the  
> way Mule
> feeds into AMQ and how the sequence number on the messages is always  
> zero...

That would do it ;)
>
>
>
> Aaron Mulder wrote:
>>
>> FWIW, Message Groups were working for me on a 5.1 server with a  
>> broker
>> and one producer and several consumers all running in separate apps.
>> So a test case would be really helpful (unless you think the problem
>> is just when you have multiple producers).
>>
>> Thanks,
>>       Aaron
>>
>> On Tue, May 27, 2008 at 11:27 AM, jcarreira <jcarreira@gmail.com>  
>> wrote:
>>>
>>> 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.
>>>
>>> Anyone have any idea why it might be doing that or how to fix it?
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Message-Groups%3A-Not-working-with-Mule-2.0.1-feeding-AMQ-5.1-tp17493075s2354p17493075.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>>
>>>
>>>
>>
>>
>
> -- 
> View this message in context: http://www.nabble.com/Message-Groups%3A-Not-working-with-Mule-2.0.1-feeding-AMQ-5.1-tp17493075s2354p17495601.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>