Custom component : route not completing on second call

2022-09-26 Thread Stefan Kok
Hi I have created a custom camel compent. Problem: I have listed snippets of the relevant code below. At present, the first call to the code will return the correct result. However, on the second call it seems the Route is not returning i.e the out message is never sent. Despite the asyncC

Re: Custom component : route not completing on second call

2022-09-29 Thread Stefan Kok
Hi Claudio Thank you for your response. I can share just need to remove some sensitive words. I will post the code to my GitHub account and post the link here. Stefan On Wed, 2022-09-28 at 12:46 -0300, Claudio Miranda wrote: > On Tue, Sep 27, 2022 at 3:45 AM Stefan Kok > wrote: >

Re: Custom component : route not completing on second call

2022-09-29 Thread Stefan Kok
A copy of the project is available at https://github.com/koksj/ws-connector On Wed, 2022-09-28 at 12:46 -0300, Claudio Miranda wrote: > On Tue, Sep 27, 2022 at 3:45 AM Stefan Kok > wrote: > > > > I have listed snippets of the relevant code below.  At present, the > >

Re: Custom component : route not completing on second call

2022-10-03 Thread Stefan Kok
meout. On Thu, 2022-09-29 at 11:57 +0200, Stefan Kok wrote: > A copy of the project is available at > > https://github.com/koksj/ws-connector > > > On Wed, 2022-09-28 at 12:46 -0300, Claudio Miranda wrote: > > On Tue, Sep 27, 2022 at 3:45 AM Stefan Kok > > wrote: >

ExchangeTimedOutException

2022-10-10 Thread Stefan Kok
Hi All I am having great difficulty making sense of the below log entry: 10-10-2022 11:53:11.497 WARN [ForkJoinPool.commonPool-worker-2] com.experflow.service.OcepService.lambda$changeAgentState$3(OcepService .java:115) - Exception Message: org.apache.camel.ExchangeTimedOutException: The OUT mes

Re: ExchangeTimedOutException

2022-10-10 Thread Stefan Kok
se of that. > > What kind of messaging protocol do you use? JMS, http, etc? > > On Mon, Oct 10, 2022 at 12:20 PM Stefan Kok > > wrote: > > > Hi All > > > > I am having great difficulty making sense of the below log entry: >

Re: ExchangeTimedOutException

2022-10-10 Thread Stefan Kok
> > On Mon, Oct 10, 2022 at 12:33 PM Claus Ibsen > wrote: > > > It says that the message did not arrive, and that a timeout was > > triggered > > because of that. > > > > What kind of messaging protocol do you use? JMS, http, etc? > > > > On M

Re: ExchangeTimedOutException

2022-10-11 Thread Stefan Kok
On Mon, 2022-10-10 at 13:27 +0200, Stefan Kok wrote: The reason why the second call to the route failed is that my code did not update the rerence to the second exchang's exchange asyncCallback i.e I used the previous asyncCallback. > Hi Claus > > Thank you for the response. &

Re: ExchangeTimedOutException

2022-10-11 Thread Stefan Kok
t it created a new blank message > and you loose everything from the original message.   > > -Original Message- > From: Stefan Kok > Sent: Monday, October 10, 2022 5:36 AM > To: users@camel.apache.org > Subject: Re: ExchangeTimedOutException > > Think

Camel Producer receiving messages asynchronously from Web Socket Server

2022-10-12 Thread Stefan Kok
Hi All Background: I have a custom camel producer receiving messages asynchronously from a web socket server. The next phase requires that we respond to events emitted from the web socket server which we did not initiate from a client perspective on the open web sockets. Question: When we recei