You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by amitr <am...@gmail.com> on 2015/06/15 10:13:32 UTC
Getting "Cannot determine current route from Exchange with id"
message
Hi,
I'm currently working with camel 2.14.3 release and using camel-netty4-http
and getting some strange behaviour:
After using routing-slip and getting an error from the target endpoint, I'm
getting the message: "Cannot determine current route from Exchange with id:
<myId>" - 2 minutes after the error.
The accompaniment netty exception (after the 2 minutes) is below.
Any ideas?
Thx,
Amit.
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[na:1.8.0_11]
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[na:1.8.0_11]
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[na:1.8.0_11]
at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[na:1.8.0_11]
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:375)
~[na:1.8.0_11]
at
io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:447)
~[netty-buffer-4.0.28.Final.jar:4.0.28.Final]
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:881)
~[netty-buffer-4.0.28.Final.jar:4.0.28.Final]
at
io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:242)
~[netty-transport-4.0.28.Final.jar:4.0.28.Final]
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)
~[netty-transport-4.0.28.Final.jar:4.0.28.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
[netty-transport-4.0.28.Final.jar:4.0.28.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
[netty-transport-4.0.28.Final.jar:4.0.28.Final]
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
[netty-transport-4.0.28.Final.jar:4.0.28.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
[netty-transport-4.0.28.Final.jar:4.0.28.Final]
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
[netty-common-4.0.28.Final.jar:4.0.28.Final]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
--
View this message in context: http://camel.465427.n5.nabble.com/Getting-Cannot-determine-current-route-from-Exchange-with-id-message-tp5768242.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Getting "Cannot determine current route from Exchange with
id" message
Posted by Willem Jiang <wi...@gmail.com>.
Can you show us the camel route that you have?
What kind of error that target endpoint get?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On June 15, 2015 at 4:17:03 PM, amitr (amitrokah@gmail.com) wrote:
> Hi,
> I'm currently working with camel 2.14.3 release and using camel-netty4-http
> and getting some strange behaviour:
> After using routing-slip and getting an error from the target endpoint, I'm
> getting the message: "Cannot determine current route from Exchange with id:
> " - 2 minutes after the error.
>
> The accompaniment netty exception (after the 2 minutes) is below.
> Any ideas?
> Thx,
> Amit.
>
> java.io.IOException: Connection reset by peer
> at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[na:1.8.0_11]
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[na:1.8.0_11]
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[na:1.8.0_11]
> at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[na:1.8.0_11]
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:375)
> ~[na:1.8.0_11]
> at
> io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:447)
> ~[netty-buffer-4.0.28.Final.jar:4.0.28.Final]
> at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:881)
> ~[netty-buffer-4.0.28.Final.jar:4.0.28.Final]
> at
> io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:242)
> ~[netty-transport-4.0.28.Final.jar:4.0.28.Final]
> at
> io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)
> ~[netty-transport-4.0.28.Final.jar:4.0.28.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
> [netty-transport-4.0.28.Final.jar:4.0.28.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
> [netty-transport-4.0.28.Final.jar:4.0.28.Final]
> at
> io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
> [netty-transport-4.0.28.Final.jar:4.0.28.Final]
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
> [netty-transport-4.0.28.Final.jar:4.0.28.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
> [netty-common-4.0.28.Final.jar:4.0.28.Final]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_11]
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Getting-Cannot-determine-current-route-from-Exchange-with-id-message-tp5768242.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>