Hi Thanks yeah its a bug I have logged a ticket https://issues.apache.org/jira/browse/CAMEL-9569
On Fri, Feb 5, 2016 at 3:17 PM, fss.coc <fss....@gmail.com> wrote: > Regarding the idempotent, using as an example the MemoryIdempotentRepository > and had the same behavior. > The new test therefore shows two problems: Services and Produces growing > infinitely. > > LeakOfMemory.java > <http://camel.465427.n5.nabble.com/file/n5777278/LeakOfMemory.java> > > > > For the service (MemoryIdempotentRepository or JdbcMessageIdRepository), my > resolution was to save the instance of IdempotentRepository, and removal of > the route (LifecycleStrategy), manually remove the service > > public void removeRoute(final String routeId) throws Exception { > final RouteContext routeContext = > routeContextByRouteId.remove(routeId); > assert routeContext.routeId.equals(routeId); > if (routeContext != null) { > > camelContext.removeService(routeContext.jdbcMessageIdRepository); > } > } > > @Override > public void onRoutesRemove(final Collection<Route> routes) { > for (final Route route : routes) { > try { > removeRoute(route.getId()); > } catch (final Exception e) { > logger.error("Error on remove > jdbcMessageIdRepository"); > } > } > } > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Leak-of-Memory-using-JdbcMessageIdRepository-tp5777242p5777278.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
