Asankha, I think found the related issue: https://issues.apache.org/jira/browse/SYNAPSE-600
According to your comment the fix has only been applied to the 1.3 branch. Is there any reason to not (yet) apply this change to the trunk? ________________________________ From: Hubert, Eric [mailto:[email protected]] Sent: Monday, December 07, 2009 7:44 AM To: [email protected] Subject: RE: Advice on choosing http core NIO version for Synapse 1.2 Hi Oleg, Eric Me neither, but from what I've seen, in HttpCoreNIOSender Synapse logs the thrown IOReactorException including the cause information as early as it has a chance to do so: Eric - you are looking at a previous version of the code, when we enabled auto-restart on unexpected shutdown, we improved this logic. However the real cause is the ClosedChannelException issue. We can neatly log fatal causes when such a restart is performed, so that we will know in future, what caused such a filure Asankha, I actually was also a bit confused as I expected to find the code which attempts the restart. But if I’m not wrong I was really looking at trunk. Is it possible, that the change has only been applied to the Synapse 1.3 branch and not yet forward ported to the trunk? Lets work on getting this fix into HttpComponents, probably as you switch to the new HttpCore version, since this is a quite common scenario you encounter in your deployment Which fix are you referring to regarding HttpCompoents? Do you mean the one regarding the ClosedChannelException? This one has already been fixed for beta-3 and will be fine in 4.0.1. What other fix do you see which can be applied to HttpComponents directly? Sorry, maybe I’m a bit to tired this morning… Thanks, Eric
