Hubert, Eric wrote:
Hi all,
we are currently using Synapse 1.2 with http-core-nio 4.0 beta2. From time to time and unfortunately not reproducible we encounter IOReactor shutdowns in our production environment. I would like to track down the actual cause of these shutdowns, but the logs reveal no detail.
I quickly went through the release notes of http core 4.0-beta3, 4.0 and 4.0.1.
HTTPCORE-169 looked quite interesting. I remember that some time back we tried
out 4.0 but stumbled across an issue related to chunked encoding. Unfortunately
my memory has flashed. It could be that it was related to HTTPCORE-175.
Would it be advisable to check out updating to 4.0.1? Is there any chance to
get some information about the actual cause in case of IOReactor terminations?
Thanks,
Eric
Hi Eric
I cannot think of any good reason to continue using HttpCore older than
4.0.1. Upgrade would be quite recommended.
The process of an I/O reactor shutdown is quite complex and therefore
lots of things can go sideways if a particular I/O worker terminates
abnormally due to a runtime or a fatal I/O error. To help deal with
postmortem analysis I/O reactors maintain so called exception log that
contains all exceptions thrown in the process of reactor shutdown
including the one that triggered it.
http://hc.apache.org/httpcomponents-core/tutorial/html/nio.html#d0e1287
Whenever an I/O reactor terminates it is advisable to examine the audit
log and if it contains any entries print them out to the application log.
Hope this helps
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
