Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.220.177 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=RYjLMxwM17I+OwqV3iDIstW8CsqWrJicQVXkxtLRH64gPzRXp8al3/0hXCL9ZHdKii
         vSXpFUOVAZM3C4vwgWQGnwh+ukpz9gHt7B1v+/0TM3PWRHeuLucD8m6TMmU1HkK0gvJv
         NjOMUjh0OLRitQJx5tyFx2SxwvOSc4k0SVm6Q=
MIME-Version: 1.0
In-Reply-To: <23012582.post@talk.nabble.com>
References: <22981898.post@talk.nabble.com> <22986139.post@talk.nabble.com>
	<23012582.post@talk.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Fri, 1 May 2009 09:24:17 +0200
Message-ID: <5380c69c0905010024h6184d855q443e9ed3e9b8d1ac@mail.gmail.com>
Subject: Re: Router Blocked by full Destination Route Queue
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi

I was looking into another matter and the problem with the sending to
JMS hangs is explained a bit here:
http://www.nabble.com/Do-the-send-timeouts-actually-work--td20583221.html

The other matter is this one:
http://fusesource.com/issues/browse/MR-170

On Sun, Apr 12, 2009 at 6:47 PM, yesnid <nsimi@pelco.com> wrote:
>
> Hello,
>
> Below you will find a simplified example, of what my router is doing,
> basically recieving on one queue and then resending on another in this
> example, now to get the test working properly, have a producer send messa=
ges
> to the recieving queue and no one listening to the destination queue
> eventually the router will hang.
>
> My producers are connecting with the following, settings to the broker;
> Delivery Mode =3D persistent, Message TTL =3D 0 (Essentially infinite),
> transacted =3D false, session =3D auto acknowledge.
>
> To see the problem faster you can set the memory in the policy entry for =
you
> queue to lower, I suggest really low so that the problem appears really f=
ast
> and you don't have to wait to see it appear.
>
> public class TestCamelRouter extends RouteBuilder
> {
> =A0 =A0 =A0 =A0final static String BEAN_NAME =3D "TestCamelRouter";
> =A0 =A0 =A0 =A0final static String BEAN_METHOD =3D "route";
>
> =A0 =A0 =A0 =A0@RecipientList
> =A0 =A0 =A0 =A0public List<String> route(Exchange exchange)
> =A0 =A0 =A0 =A0{
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0ArrayList<String> returnSet =3D new ArrayL=
ist<String>();
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0returnSet.add("JMS-BROKER" + ":queue:" + "=
TestDeliveryQueue");
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return returnSet;
> =A0 =A0 =A0 =A0}
>
> =A0 =A0 =A0 =A0@Override
> =A0 =A0 =A0 =A0public void configure() throws Exception
> =A0 =A0 =A0 =A0{
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0from("JMS-BROKER" + ":queue:" +
> "RecievingQueue").beanRef(TestCamelRouter.BEAN_NAME,
> TestCamelRouter.BEAN_METHOD);
> =A0 =A0 =A0 =A0}
>
> =A0 =A0 =A0 =A0public static void main(String[] args)
> =A0 =A0 =A0 =A0{
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0JndiContext jndiContext =3D null;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0try
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0{
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0jndiContext =3D new JndiCo=
ntext();
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0jndiContext.bind(TestCamel=
Router.BEAN_NAME, new TestCamelRouter());
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0}
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0catch (Exception e)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0{
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0e.printStackTrace();
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0}
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0CamelContext context =3D new DefaultCamelC=
ontext(jndiContext);
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0ActiveMQConnectionFactory factory =3D new
> ActiveMQConnectionFactory("tcp://localhost:61616");
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0factory.setDispatchAsync(true);
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0context.addComponent("JMS-BROKER",
> JmsComponent.jmsComponentAutoAcknowledge(factory));
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0try
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0{
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0context.addRoutes(new Test=
CamelRouter());
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0context.start();
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0while (true)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Thread.sle=
ep(60000);
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0}
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0catch (Exception e)
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0{
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0e.printStackTrace();
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return;
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0}
> =A0 =A0 =A0 =A0}
>
> }
>
>
>
>
>
>
>
> huntc wrote:
>>
>> Can you please provide the route's specification in code or XML. This wi=
ll
>> give us a better chance of answering your question.
>>
>> Having said that, sounds like you've got an internal seda queue... I wou=
ld
>> have thought that an exception would be thrown once the queue becomes
>> full. By default a seda queue can only hold 1000 items.
>>
>> If it is a JMS queue, then would setting the time to live option be usef=
ul
>> to you?
>>
>
> --
> View this message in context: http://www.nabble.com/Router-Blocked-by-ful=
l-Destination-Route-Queue-tp22981898p23012582.html
> Sent from the Camel - Users (activemq) 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
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration