Hi But that said, we could likely take a look if we could detect if the route endpoint is used by other routes, and avoid shutting it down, as we have that logic for endpoints used within the route.
You are welcome to log a JIRA ticket then we can take a stab at improving this. On Thu, Mar 26, 2015 at 9:31 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > You should favor to keep state on the component and then delegate from > endpoints on add/remove etc, then you can keep track of what are in > use and when there is no users of the resource, you can cleanup. > > This is what other camel components does, such as seda / jetty etc. > > On Thu, Mar 26, 2015 at 12:42 PM, Atanas Shindov > <atanas.shin...@gmail.com> wrote: >> Hi Claus, >> >> I just checked the 2.15 code and it's the same: >> >> /// endpoints should only be stopped when Camel is shutting down >> // see more details in the warmUp method >> ServiceHelper.stopAndShutdownServices(route.getEndpoint());/ >> >> Looks like you are still closing an endpoint on route removal? >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Route-removal-triggers-endpoint-shutdown-tp5764796p5764821.html >> Sent from the Camel - Users mailing list archive at Nabble.com. > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > Email: cib...@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/ -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@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/
