https://bz.apache.org/bugzilla/show_bug.cgi?id=62515
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
OS| |All
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
There are a couple of points it is worth clarifying before starting a
discussion on any potential changes.
Currently, the point where the socket is bound and unbound is controlled by
bindOnInit. By default, the socket is bound when the connector is initialised
and unbound when it is destroyed.
On stop, the connector is first paused. Any new connections from that point
will sit in the TCP backlog. Shutdown continues with the web applications being
stopped followed by the host and engine. Then the connectors are stopped.
Everything is then destroyed (same order). The connections in the backlog will
be dropped when the server socket is unbound.
The behaviour reported in the description is consistent with the current
implementation.
Effectively, what is being requested is that the server socket is unbound
earlier in the process.
Some investigation is required to see what might be possible.
--
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
