Hello Claus,
Thanks for the suggestion, setting the exchange pattern to InOut helped with
the timeout issue. Great tip allaround, wasn't aware of the possibility to
explicitly influence the MEP type of the exchange, thanks.
Got another problem though, I'm putting the acknowledgement messages I
mentioned into Out part of the exchange (exchange.getOut().setBody("ACK")
in myRoutePolicy.onExchangeDone()) expecting that is the proper way to make
a route send a response for the incoming messages. Partly, I think it's
working. These do appear in the logs:
Route2 log:
Channel: [id: 0x9c1f061a, /127.0.0.1:52671 => /127.0.0.1:9010] writing body:
Nak
Route1 log:
Channel: [id: 0xb32b3cf5, /127.0.0.1:52671 => localhost/127.0.0.1:9010]
received body: Nak
Looking at this, I see that netty endpoint from Route 1 received body "Nak".
But the "Nak" message also ends up on "myQueue" which is wrong for my
usecase. How can I make it stop getting routed to "myQueue" and keep the
rest of the behavior?
Regards,
Slavisa
--
View this message in context:
http://camel.465427.n5.nabble.com/Netty-component-and-acknowledgement-message-tp5767915p5767964.html
Sent from the Camel - Users mailing list archive at Nabble.com.
