[
https://issues.apache.org/jira/browse/HTTPCORE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCORE-60.
---------------------------------------
Resolution: Fixed
Anthony
It turned out ClosedChannelException is a checked I/O exception so it cannot
kill the I/O dispatch thread. So, apparently I was wrong in my initial
assertion about the cause of the Synapse I/O transport lockup. I tweaked
HttpCore code a little and changed the IOSessionImpl to catch all
ChannelClosedException-s thrown by the underlying byte channel just in case.
Please review the changes and let me know if it is okay to proceed with the
release
Oleg
> Transport appears to be hanging because an unchecked exception caused the I/O
> dispatch thread to terminate
> ----------------------------------------------------------------------------------------------------------
>
> Key: HTTPCORE-60
> URL: https://issues.apache.org/jira/browse/HTTPCORE-60
> Project: HttpComponents Core
> Issue Type: Bug
> Affects Versions: 4.0-alpha4
> Reporter: ant elder
> Assigned To: Oleg Kalnichevski
> Fix For: 4.0-alpha4
>
>
> See discussion on synapse-dev mailing list:
> http://www.nabble.com/Intermittent-IO-Errors-using-Synapse-tf3439957.html
> The transport appears to be hanging because an unchecked exception
> caused the I/O dispatch thread to terminate. I believe there are several
> different types of problems (at least two) that we are seeing here.
> [I/O reactor worker thread 5] ERROR ServerHandler - I/O Error : null
> > java.nio.channels.ClosedChannelException
> > at
> > sun.nio.ch.SocketChannelImpl.ensureReadOpen(SocketChannelImpl.java:112)
> > at
> > sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:139)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
