Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.218.216 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=NWJ8gAkFCs0dgsqyyFMNiQihS90mwCIu7OXLmXJwOrMUucdzxgAkeqQhx99Op/RTUA
         5rcFTp/ueFQDuTjTZRUOm+DY+b/ZWCIeMENI4L3CzwwcUvk9nrfx56dls9BpezjSSlbE
         lmKP0geN1Yva0LD6LXgAsl+YVmjLLFHCCaa3s=
MIME-Version: 1.0
In-Reply-To: <25230306.post@talk.nabble.com>
References: <25036666.post@talk.nabble.com>
 <5380c69c0908182306k3a401fb6q69b7f5c9298854f7@mail.gmail.com>
	<25049040.post@talk.nabble.com>
 <5380c69c0908311227k1b594390t2f71ff1f781996ab@mail.gmail.com>
	<25230306.post@talk.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 1 Sep 2009 05:56:51 +0200
Message-ID: <5380c69c0908312056y4ff5ffd3s26e851715757f375@mail.gmail.com>
Subject: Re: JMSExceptions from jms component?
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Aug 31, 2009 at 10:56 PM, allen.lau<guyagl@gmail.com> wrote:
>
>
>
> Claus Ibsen-2 wrote:
>>
>> On Wed, Aug 19, 2009 at 7:57 PM, allen.lau<guyagl@gmail.com> wrote:
>>>
>>> Claus, =A0you are right, I had to set "alwaysSynSend=3Dtrue" in
>>> ActiveMQConnectionFactory to see the exception.
>>>
>>> Now it is a matter of figuring out whether I can only force it for
>>> certain
>>> queues.
>>
>> You can use 2 different queue connection factories. With and without
>> the sync sending.
>> Or how did you go around this issue?
>>
>> Thanks Claus for the suggestion.
>>
>> Decided it was best to use either sync or async. =A0It is not possible i=
n
>> ActiveMQ to set sendFailIfNoSpace for each individual queue. =A0It looks
>> like system setting.

Have you suggested this new feature on the AMQ forums?


>>
>> Allen
>>
>>
>>>
>>> Thanks for the help.
>>> Allen.
>>>
>>>
>>> Claus Ibsen-2 wrote:
>>>>
>>>> Hi
>>>>
>>>> AMQ have a failover protocol that can "self heal".
>>>>
>>>> I suggest to ask on the AMQ forum as its a AMQ question whether it can
>>>> signal back to the client when it cannot accept any new messages due
>>>> to out of space.
>>>>
>>>>
>>>>
>>>> On Wed, Aug 19, 2009 at 4:10 AM, allen.lau<guyagl@gmail.com> wrote:
>>>>>
>>>>> Hi, =A0I'm testing out the jms component using a route like so:
>>>>>
>>>>> =A0<camelContext id=3D"producer" trace=3D"true"
>>>>> xmlns=3D"http://camel.apache.org/schema/spring">
>>>>> =A0 =A0 =A0 =A0<route>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0<from uri=3D"file:src/data?noop=3Dtrue"/>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0<loop>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<constant>200</constant>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<to uri=3D"jms:LOAD_TEST" pattern=3D"I=
nOnly"/>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0</loop>
>>>>> =A0 =A0 =A0 =A0 =A0 =A0<stop/>
>>>>> =A0 =A0 =A0 =A0</route>
>>>>> =A0 =A0</camelContext>
>>>>>
>>>>> I have also configured the activeMQ broker to fail send if no space
>>>>> using
>>>>> the option: =A0<systemUsage sendFailIfNoSpace=3D"true">
>>>>>
>>>>> What I was hoping to achieve is to capture the exception that is thro=
wn
>>>>> from
>>>>> ActiveMQ in the Camel route and retry accordingly. =A0 It seems thoug=
h
>>>>> that
>>>>> the Camel route never sees the exception.
>>>>>
>>>>> Is my understanding incorrect or is this a bug in Camel? =A0I'm using
>>>>> 2.0-M3
>>>>> and ActiveMQ 5.2.0 in my tests.
>>>>
>>>> No its not a bug in Camel as AMQ do not signal back to Camel that it
>>>> cannot accept the message.
>>>> However AMQ have a ton of options and it can be a bit hard to find it
>>>> and configure it so it work.
>>>>
>>>> So ask at the AMQ forum to get attention of the AMQ experts.
>>>>
>>>> Camel uses Spring JMS underneath so if someone have a pure Spring JMS
>>>> solution it should be possible with Camel as well.
>>>>
>>>>
>>>>>
>>>>> Thanks,
>>>>> Allen
>>>>> --
>>>>> View this message in context:
>>>>> http://www.nabble.com/JMSExceptions-from-jms-component--tp25036666p25=
036666.html
>>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> Apache Camel Committer
>>>>
>>>> Open Source Integration: http://fusesource.com
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Twitter: http://twitter.com/davsclaus
>>>>
>>>>
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/JMSExceptions-from-jms-component--tp25036666p2504=
9040.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>>
>>
>
> --
> View this message in context: http://www.nabble.com/JMSExceptions-from-jm=
s-component--tp25036666p25230306.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>


--=20
Claus Ibsen
Apache Camel Committer

Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus