https://issues.apache.org/bugzilla/show_bug.cgi?id=50360
--- Comment #3 from Martin Grotzke <martin.grot...@googlemail.com> 2010-11-30
16:24:43 EST ---
I debugged this and found the following path of execution:
Connector.stopInternal():
-> protocolHandler.stop() (Http11Protocol, stop() implemented in
AbstractHttp11Protocol)
-> endpoint.stop() (JIoEndpoint)
-> pause()
-> unlockAccept()
-> shutdownExecutor()
A problem here seems to be that JIoEndpoint.stop() does not close the
serverSocket (only destroy is doing this).
Therefore, if the implementation of AbstractHttp11Protocol.stop() is changed to
invoke
endpoint.destroy();
instead of endpoint.stop() also fixes the issue.
Not sure if this is the correct solution.
How can we proceed with this?
Thanx && Cheers,
Martin
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
