Hi The code in trunk has been improved when stopping/shutting down a service as it will detect tis state pre action and only initiate the operation if necessary. That is only applicable if the service carries a state, such as extending ServiceSupport (which most components does).
And I have just commited a fix in camel-jms to avoid that NPE. On Tue, Feb 15, 2011 at 9:23 PM, Barry Kaplan <grou...@memelet.com> wrote: > > I'm having problems getting a clean shutdown of my jms routes. I am seeing > messages like: > > Route: caef5400-393f-11e0-96f5-001bfc9b4a1b suspended and shutdown deferred, > was consuming from: > Endpoint[jms://topic:utilization.device.*.timeline.lifecycle] > > And then later on getting: > > :18:39,967 WARN o.a.c.impl.DefaultShutdownStrategy - Error occurred while > shutting down route: > Consumer[jms://topic:device.4d5ade52c87fc0c0f9741781.utilization.cycleintervals.crud.*]. > This exception will be ignored. [Camel Thread 0 - ShutdownTask] > java.lang.NullPointerException: null > at > org.apache.camel.component.jms.JmsConsumer.doStop(JmsConsumer.java:130) > ~[camel-jms-2.5.0.jar:2.5.0] > > Looking at the JmsConsumer code this can only happen if doStop() is called > twice on the same instance. > > Is this an FAQ issue, or do I need to some debugging to figure out what is > going on? > -- > View this message in context: > http://camel.465427.n5.nabble.com/NPE-on-JmsConsumer-shutdown-tp3386582p3386582.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
