Hi, There is a connectTimeout parameter in Camel that allows you to configure a Netty endpoint to timeout a connection due to inactivity.
If you have wide variances in the time you backend application sends responses, you may use keepAlives to keep the connection going until you receive a response. A better option would be to create a simple one directional netty socket producer on either side (this would mean the backend app has to change as well) and use a correlationId to correlate requests against responses. Netty supports both sync and async modes. Hope this helps. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com http://fusesource.com Blog: http://opensourceknowledge.blogspot.com http://opensourceknowledge.blogspot.com --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/RE-netty-questions-tp3046038p3047101.html Sent from the Camel - Users mailing list archive at Nabble.com.
