There has been some netty fixes, so try with latest SNAPSHOT code or build from source
On Mon, Jul 20, 2015 at 6:33 PM, V4Vaithi <[email protected]> wrote: > I am using camel netty for TCP IP Communication. > > Consuming from Websphere MQ and trying to send it to TCP Server. Every thing > went fine unless Server is up and running. > > Problem occurs when server closes the connection without sending > Acknowledgement back (As it is Sync communication). So thread is getting > hung and cannot able to complete the route life cycle for the particular > message. > > using Camel 2.14 (Also tried with Camel 2.15). same is the case. > > As a workaround i am throwing exception explicitly when it is not thrown by > default implementation. in channelDisconnect method. > > Any suggestions on this? or is it a known issue .. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Netty-producer-Doesn-t-throw-Exception-in-case-Server-closes-the-connection-tp5769603.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2nd edition: http://www.manning.com/ibsen2
