On Mon, Mar 4, 2013 at 10:34 AM, helander <[email protected]> wrote: > I have a web application that creates a couple of camel contexts. I was > surprised to see that when I redeployed my application, the camel contexts > created by the "old" application instance was still visible via jconsole > after having redeployed the application (along with the set of contexts > created by the "new" application instance. I was even more surprised when I > found that after having undeployed the application (no instance available on > the server) the camel contexts are still visible via jconsole. > > Is this behaviour to be expected, or ....? >
Yes as Camel is so self-aware that it has a built-in defense mehanism to stay alive ;) Well of course this is not desired. What version of JBoss AS do you use? And how do you deploy Camel? as a WAR or some other way? And if you use WAR do you use a spring xml file or something as we show here http://camel.apache.org/tutorial-on-using-camel-in-a-web-application.html > Thanks > > Lars > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-contexts-not-removed-when-WAR-deployed-on-JBoss-AS-7-tp5728435.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
