Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of aleriospresidente@gmail.com)
Date: Wed, 10 Oct 2012 13:22:56 -0700 (PDT)
From: alerios <aleriospresidente@gmail.com>
To: users@camel.apache.org
Message-ID: <1349900576207-5720862.post@n5.nabble.com>
In-Reply-To: <1349843135492-5720824.post@n5.nabble.com>
References: <1349819353996-5720818.post@n5.nabble.com>
 <1349843135492-5720824.post@n5.nabble.com>
Subject: Re: Removing an Endpoint from a route
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Guru, thanks for your reply.


I think using the failover load balancer is not an option for me, since my
Bean will not throw an exception when it fails. I want to disable the
Endpoint when I want, based on health checks, for example.  Also, I would
like to use the weigthed loadbalancer instead, maybe I would have to
implement my own LoadBalancer class, but then I don't see any value in using
Camel at all for my escenario.

I tested the JMX console to stop an endpoint processor, but it happens the
same as when removing the Endpoint from the Registry:

Caused by: java.lang.IllegalStateException: SendProcessor has not been
started: sendTo(Endpoint[bean://tmi3?method=sendResponse])

I guess camel is not designed to remove endpoints at runtime. Maybe I should
try removing, and adding the route again, but I'm afraid that could cause a
race condition because of many threads trying to do the same.


--
View this message in context: http://camel.465427.n5.nabble.com/Removing-an-Endpoint-from-a-route-tp5720818p5720862.html
Sent from the Camel - Users mailing list archive at Nabble.com.