Re: Camel 3.20.1 // Events ExchangeCreated and ExchangeCompleted seem to be repeated

2023-01-31 Thread ski n
Maybe it's a good aidea to add a graph/explanation about the Exchange lifecycle to: https://camel.apache.org/manual/lifecycle.html and/or https://camel.apache.org/manual/exchange.html On Mon, Jan 30, 2023 at 3:56 PM Claus Ibsen wrote: > It has always been like that, when an exchange is create

Re: Camel 3.20.1 // Events ExchangeCreated and ExchangeCompleted seem to be repeated

2023-01-30 Thread Claus Ibsen
It has always been like that, when an exchange is created an event is fired. Multicast / split create exchange (sub exchanges) and thus events. You can see if its a sub exchange as it has exchange property CORRELATION_ID that points to its parent. So if you only want parent exchanges, then filter

Re: Camel 3.20.1 // Events ExchangeCreated and ExchangeCompleted seem to be repeated

2023-01-30 Thread Ephemeris Lappis
Hello. After more tests I think I have more or less an idea of the origin of the events, but an explanation should be welcome. In some cases, the 3rd route produces two files, and in some of these cases, they use a multicast. The multicast seems to be the cause of the repeated events. I've tried

Re: Camel 3.20.1 // Events ExchangeCreated and ExchangeCompleted seem to be repeated

2023-01-30 Thread Claus Ibsen
Hi This is expected as you use seda, that creates a new exchange If you use direct then no exchange is created On Mon, Jan 30, 2023 at 1:51 PM Ephemeris Lappis wrote: > Hello. > > Debugging some routes with an EventNotifier it seems that the event > ExchangecReated and ExchangeCompleted are rep

Camel 3.20.1 // Events ExchangeCreated and ExchangeCompleted seem to be repeated

2023-01-30 Thread Ephemeris Lappis
Hello. Debugging some routes with an EventNotifier it seems that the event ExchangecReated and ExchangeCompleted are repeated twice (I mean 3 times instead of 1). My tested application routes are all on the same pattern : - route 1 : from JMS queue1 to JMS queue2 - route 2 : from JMS queue2 to se