Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

Hi Claus, Thanks for creating a ticket. I think Service Unavaliable should be find for load balancer (LB). In my particular case load balancer will be checking some predefined healthcheck/status page with a status info that can be parsed by LB. E.g. every 5 seconds the LB will issue a GET request

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

Hi Just refreshed my 2.3-SNAPSHOT, and I'm still getting the exceptions if I omit Defer option in my route. I'm going to wait some time and try again later, perhaps your changes are not in the latest snapshot yet. Thank you. Ilya. On Wed, Apr 21, 2010 at 2:10 AM, Claus Ibsen wrote: > Hi > > I

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

Hi Claus, Thanks again for making this work! I tried the latest code from trunk directly, and everything seems to work fine with my test case/prototype. Ilya. On Wed, Apr 21, 2010 at 8:47 AM, Ilya S wrote: > Hi > > Just refreshed my 2.3-SNAPSHOT, and I'm still getting the exc

InterceptionStrategy: target vs nextTarget (camel 2.3.0)

I'm implementing a global InterceptStrategy that is supposed to wrap only some of the processors (in particular I'm interested in the processors that implement particular interface). When debugging my strategy, I noticed that in most cases the *target *object does not contain the actual object I'm

Creating a Polling JMS consumer in Java DSL route

I'm on Camel 2.3 with ActiveMQ 5.3.2. I am working with a set of slow JMS consumers, and I'd like to be able to create them as polling consumers in my route defined in Java DSL. Is this possible? Can anyone show an example? The reason I want polling jms consumers is because I cannot set "prefetch

JMS transactions between multiple routes

Hi All, I'm using Camel 1.6.1 (cannot use 2.0) , with Spring 2.5.6, and ActiveMQ 5.2. I'm trying to set up Transaction Manager so that my transactions are rolled back on error. Here is my camel xml config adopted from the examples: =

Re: JMS transactions between multiple routes

Hi Fintan, I basically took Camel spring example from 1.6.1 (apache-camel-1.6.1\examples\camel-example-spring-jms) and modified it. I would like camel to propagate my exception (or jms fault) that happen in some nested route up to the original producer(client). I thought I can do this with transa

Re: JMS transactions between multiple routes

eue before the TX is comitted. > > > > On Tue, Aug 25, 2009 at 1:55 AM, Ilya S wrote: >> Hi All, >> >> I'm using Camel 1.6.1 (cannot use 2.0) , with Spring 2.5.6, and ActiveMQ 5.2. >> >> I'm trying to set up Transaction Manager so that my transact

Re: JMS transactions between multiple routes

Claus, I think 'transferException' option is only available in Camel 2.0? I have to use 1.6.1... On Tue, Aug 25, 2009 at 8:50 AM, Claus Ibsen wrote: > See transferException option on Camel JMS > > > On Tue, Aug 25, 2009 at 5:47 PM, Ilya S wrote: >> Hi Claus, >

Re: JMS transactions between multiple routes

Hi Fintan, Thanks for clarifying. I thought that when TransactionErrorHandler is used, there is no dead letter queue, and when exception is thrown it is propagated back. Claus has suggested to use 'transferException=true' param to accomplish what I want, however I think it is available only since

Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

Hi All, Fist of all, thank you for this great product! Every new release brings excellent new features just in time. I'm currently investigating Graceful Shutdown feature, and I'm am wondering if graceful shutdown is supported for Camel-Jetty component? I was able to successfully shut down JMS co

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

ghts. I can only > think of if you use the aggregator or some custom code which > can cause the exchange to be completed in Camels point of view. > > Can you post your entire route? > > And as always report which version of Camel you are using? And try > with the latest stable

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

Let me add that I see around 5-6 inflight exchanges in the jconsole (via JMX) before I hit stop(). So there are exchanges, but the log statements say there are none.. Thanks again, Ilya On Thu, Apr 15, 2010 at 8:37 AM, Ilya S wrote: > Here is my full route: > > >        from

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

> > Can you post your entire route? > > And as always report which version of Camel you are using? And try > with the latest stable and even with 2.3-SNAPSHOT. > > > On Wed, Apr 14, 2010 at 7:41 PM, Ilya S wrote: >> Hi All, >> >> Fist of all, thank you for

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

RACE Message sent since last write check, resetting flag [ InactivityMonitor ReadCheck] InactivityMonitor DEBUG 30004 ms elapsed since last read check. [ InactivityMonitor ReadCheck] InactivityMonitor TRACE Message received since last read check, resetting flag: On Th

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

I'd like to bump this thread up, and see if anyone has any suggestions. Thanks. On Thu, Apr 15, 2010 at 10:24 AM, Ilya S wrote: > Here is a more detailed log (with TRACE level on) if that can help: > > [CP Connection(4)-10.58.123.154] DefaultCamelContext            INFO > A

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

7:52 PM, Claus Ibsen wrote: >> Hi >> >> Just defer shutting down the Jetty route. >> http://camel.apache.org/graceful-shutdown.html >> >> On Mon, Apr 19, 2010 at 7:08 PM, Ilya S wrote: >>> I'd like to bump this thread up, and see if anyone has any

Re: Graceful shutdown of Camel-Jetty component. (Camel 2.2.0)

Hi Claus, The test cases were helpful. However, the reason I cannot use "Defer" option is because my Jetty input point is public, and if I have this option set, then the new messages will keep comming from the clients and the context will never be done. My goal is stop processesing gracefully whi