https://issues.apache.org/bugzilla/show_bug.cgi?id=55144
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution|--- |INVALID
--- Comment #10 from Mark Thomas <ma...@apache.org> ---
Next question - are those threads blocking for more than 30 minutes after the
write attempt? If yes, that is points to a JVM bug. If not, then everything is
working as designed.
Given the above, I don't see a Tomcat bug here so I am resolving this as
INVALID. Feel free to continue this discussion on the users list. If your
investigation does discover a bug (e.g. Tomcat fails to act on a something
(e.g. an exception) that should result in the socket being closed) then feel
free to re-open this issue.
I'd suggest that the CleanResourceTask sets the timeout a lot lower (e.g. 20s)
before trying to write to the socket. While 30mins is OK for a read timeout it
is way too high for a blocking write.
--
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
