Re: Route removal triggers endpoint shutdown

Hi, Claus, I saw that the fix won't make it into the product. Do you see any risks with the workaround below: // descendant of DefaultEndpoint public void stop() throws Exception { if (isSingleton()

Re: Route removal triggers endpoint shutdown

Thanks, Claus. I will go ahead and change my logic so that I keep the state in the component. -- View this message in context: http://camel.465427.n5.nabble.com/Route-removal-triggers-endpoint-shutdown-tp5764796p5764917.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Route removal triggers endpoint shutdown

I guess you are referring to this entry: Removing a route now also remove its static Endpoint's from the EndpointRegistry (if those endpoints are not shared and used by other routes). Mind that any dynamic endpoint created during routing from dynamic EIPs such as recipient list, routing slip,

Re: Route removal triggers endpoint shutdown

2.12.1 -- View this message in context: http://camel.465427.n5.nabble.com/Route-removal-triggers-endpoint-shutdown-tp5764796p5764800.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Route removal triggers endpoint shutdown

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? --

Route removal triggers endpoint shutdown

Hello, I have a custom singleton endpoint which manages a resource used by all consumers created by this endpoint. I open and close the resource in the start() and stop() methods of the endpoint assuming that this way I would prevent illegal states, i.e. the resource is closed, but a consumer is

Re: FTP Component configuration

Hi Claus and fidoedidoe, thanks for your answers. I was more interested in why the component is designed like this from a conceptual point of view, otherwise - yes, using the properties component would allow me to achieve the same effect. Thanks again. Best regards, Atanas -- View this

Re: FTP Component configuration

That's also my understanding. We could have a behavior similar to camel-jms: do the configuration once on the component level - connection factory, JNDI configurations if necessary, etc., and have it reused by each endpoint instance create with the component. -- View this message in context:

FTP Component configuration

Hi guys, After I've watched the Riding Camel https://skillsmatter.com/skillscasts/2450-riding-camel presentation by James Strachan I tried to implement a route where all endpoints are FTP based, but instead of configuring each FTP endpoint with hostname, port, and login credentials, I wanted

Forcing Camel to use synchronous processing

Hi guys, according to the Asynchronous routing engine http://camel.apache.org/asynchronous-routing-engine.html documentation page Camel can be forced to use synchronous processing via the synchronous=true option. The DefaultEndpoint

Re: Avoiding duplicate messages

Hi Richard, thanks for your prompt reply. It looks like the Idempotent Consumer might help, especially if in it's File/JDBC based implementations the message ids are durably persisted (it seems quite logical to be so), so that they are available after a JVM restart for example. However, the