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.216.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1397514281883-5750224.post@n5.nabble.com>
References: <1397514281883-5750224.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Tue, 15 Apr 2014 06:01:34 -0700
Message-ID: 
 <CAGB5yN=wq-P530KoOhuuC2arnf4f1w=7xssoAXL7PeDFEXZuXQ@mail.gmail.com>
Subject: Re: Camel transaction handler forces reconnecting to ActiveMQ
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 3:24 PM, nqbeel <a.nabeelahamed@gmail.com> wrote:
> Trying to set up a route with transaction handling on a camel, this leads to
> connection to the activeMQ drop and reconnect every few milliseconds is this
> expected, is there a work around?
>

Do you use caching as recommended here, eg see that 2nd box on the top
of the page
http://camel.apache.org/jms


> Logs showing repeatedly reconnecting to ActiveMQ server:
>
> ActiveMQ FailoverTransport Successfully connected to
> ssl://serveraddress:61617
> ActiveMQ FailoverTransport Successfully connected to
> ssl://serveraddress:61617
> ActiveMQ FailoverTransport Successfully connected to
> ssl://serveraddress:61617
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-transaction-handler-forces-reconnecting-to-ActiveMQ-tp5750224.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/