Return-Path: 
 <users-return-8317-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 11805 invoked from network); 19 Aug 2009 17:57:35 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 19 Aug 2009 17:57:35 -0000
Received: (qmail 57677 invoked by uid 500); 19 Aug 2009 17:57:54 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 57657 invoked by uid 500); 19 Aug 2009 17:57:54 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 57647 invoked by uid 99); 19 Aug 2009 17:57:53 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Aug 2009 17:57:53 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Aug 2009 17:57:43 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1MdpPW-0002cB-SG
	for users@camel.apache.org; Wed, 19 Aug 2009 10:57:22 -0700
Message-ID: <25049040.post@talk.nabble.com>
Date: Wed, 19 Aug 2009 10:57:22 -0700 (PDT)
From: "allen.lau" <guyagl@gmail.com>
To: users@camel.apache.org
Subject: Re: JMSExceptions from jms component?
In-Reply-To: <5380c69c0908182306k3a401fb6q69b7f5c9298854f7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Nabble-From: guyagl@gmail.com
References: <25036666.post@talk.nabble.com>
 <5380c69c0908182306k3a401fb6q69b7f5c9298854f7@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org


Claus,  you 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.

Thanks for the help.
Allen.


Claus Ibsen-2 wrote:
>=20
> Hi
>=20
> AMQ have a failover protocol that can "self heal".
>=20
> 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.
>=20
>=20
>=20
> On Wed, Aug 19, 2009 at 4:10 AM, allen.lau<guyagl@gmail.com> wrote:
>>
>> Hi, =C2=A0I'm testing out the jms component using a route like so:
>>
>> =C2=A0<camelContext id=3D"producer" trace=3D"true"
>> xmlns=3D"http://camel.apache.org/schema/spring">
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0<route>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<from uri=3D"file:src/data?noop=
=3Dtrue"/>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<loop>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<constant>200</co=
nstant>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<to uri=3D"jms:LO=
AD_TEST" pattern=3D"InOnly"/>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0</loop>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<stop/>
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0</route>
>> =C2=A0 =C2=A0</camelContext>
>>
>> I have also configured the activeMQ broker to fail send if no space usin=
g
>> the option: =C2=A0<systemUsage sendFailIfNoSpace=3D"true">
>>
>> What I was hoping to achieve is to capture the exception that is thrown
>> from
>> ActiveMQ in the Camel route and retry accordingly. =C2=A0 It seems thoug=
h that
>> the Camel route never sees the exception.
>>
>> Is my understanding incorrect or is this a bug in Camel? =C2=A0I'm using
>> 2.0-M3
>> and ActiveMQ 5.2.0 in my tests.
>=20
> 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.
>=20
> So ask at the AMQ forum to get attention of the AMQ experts.
>=20
> Camel uses Spring JMS underneath so if someone have a pure Spring JMS
> solution it should be possible with Camel as well.
>=20
>=20
>>
>> Thanks,
>> Allen
>> --
>> View this message in context:
>> http://www.nabble.com/JMSExceptions-from-jms-component--tp25036666p25036=
666.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>=20
>=20
>=20
> --=20
> Claus Ibsen
> Apache Camel Committer
>=20
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>=20
>=20

--=20
View this message in context: http://www.nabble.com/JMSExceptions-from-jms-=
component--tp25036666p25049040.html
Sent from the Camel - Users mailing list archive at Nabble.com.