You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Leomar <le...@finsterblitz.de> on 2016/03/08 14:53:28 UTC
Re: Netty deadlock during connection interrupt
Hallo,
the described behavior still occures sporadic. Even with version 2.16.2. Can
be reporoduces with the example above. Occures sporadic.
--
View this message in context: http://camel.465427.n5.nabble.com/Netty-deadlock-during-connection-interrupt-tp5778317p5778738.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Netty deadlock during connection interrupt
Posted by JS <jo...@trinnovative.de>.
The issue is still present in Camel 2.16.2 and can be reproduced with the
example code above. Please note that this happens approx. every 10th run.
I've enabled trace logging for NettyProducer and got the following output:
11:27:46.668 [main] DEBUG org.apache.camel.impl.ProducerCache - >>>>
Endpoint[direct://in] Exchange[][Message: 1]
11:27:46.668 [main] DEBUG org.apache.camel.processor.SendProcessor - >>>>
Endpoint[tcp://127.0.0.1:20225]
Exchange[ID-FOO-55476-1459762065679-0-4][Message: 1]
11:27:46.669 [main] TRACE org.apache.camel.component.netty4.NettyProducer -
Pool[active=0, idle=1]
11:27:46.669 [main] TRACE org.apache.camel.component.netty4.NettyProducer -
activateObject channel: [id: 0xe5d5a984, /127.0.0.1:55493 =>
/127.0.0.1:20225] -> {}
11:27:46.669 [main] TRACE org.apache.camel.component.netty4.NettyProducer -
Validating channel: [id: 0xe5d5a984, /127.0.0.1:55493 => /127.0.0.1:20225]
-> true
11:27:46.669 [main] TRACE org.apache.camel.component.netty4.NettyProducer -
Got channel from pool [id: 0xe5d5a984, /127.0.0.1:55493 => /127.0.0.1:20225]
11:27:46.669 [main] DEBUG org.apache.camel.component.netty4.NettyProducer -
Channel: [id: 0xe5d5a984, /127.0.0.1:55493 => /127.0.0.1:20225] writing
body: 1
11:27:46.672 [Camel Thread #16 - NettyClientTCPWorker] TRACE
org.apache.camel.component.netty4.NettyProducer - Operation complete
DefaultChannelPromise@5f6e85fe(failure:
java.nio.channels.ClosedChannelException)
11:27:46.680 [Camel Thread #16 - NettyClientTCPWorker] TRACE
org.apache.camel.component.netty4.NettyProducer - Channel closed: [id:
0xe5d5a984, /127.0.0.1:55493 :> /127.0.0.1:20225]
My first guess would be that the issue is related to NettyProducer line 246
where the ClosedChannelExceptionis not handled by
ClientChannelHandler#exceptionCaught and the callback is not set to done.
Is there any possibility to fix this?
Thanks
John
--
View this message in context: http://camel.465427.n5.nabble.com/Netty-deadlock-during-connection-interrupt-tp5778317p5780402.html
Sent from the Camel - Users mailing list archive at Nabble.com.