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 james.strachan@gmail.com
 designates 64.233.178.245 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=jv25MiM3CGKXf18vvcajBiczlvrYoZotqfsrXBVEV5JcK3q19dPAffatmSWzUb6V/qUTUYaZvdPFC8zmgreXAQHC80tn1yZStE4xdQMkaaxZiP29gw8qb8cV8FDNwJaKG6j+SNK8syHH6m7U9ZN3dITHyy5HBbiZ0rSsWyXwdOU=
Message-ID: <ec6e67fd0805312231w1bacf0c0xfbba296438e58af2@mail.gmail.com>
Date: Sun, 1 Jun 2008 06:31:12 +0100
From: "James Strachan" <james.strachan@gmail.com>
To: users@activemq.apache.org
Subject: Re: Message Groups: Not working with Mule 2.0.1 feeding AMQ 5.1
In-Reply-To: <F97A10E1-6CB9-492C-BC0C-D8BC939FE9ED@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <17493075.post@talk.nabble.com>
	 <74e15baa0805270917w256aabfcn107194c943c0e330@mail.gmail.com>
	 <17495601.post@talk.nabble.com>
	 <F97A10E1-6CB9-492C-BC0C-D8BC939FE9ED@gmail.com>

FWIW zero means 'close the message group down'. Just make sure its not
zero (or remove the header) and you're sorted

2008/5/27 Rob Davies <rajdavies@gmail.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.
>>
>
>


-- 
James
-------
http://macstrac.blogspot.com/

Open Source Integration
http://open.iona.com