https://bz.apache.org/bugzilla/show_bug.cgi?id=61831
Oleg <yaol...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |---
Status|RESOLVED |REOPENED
--- Comment #2 from Oleg <yaol...@gmail.com> ---
Hi,
I realize that thread dump might look fine and this is the most confusing part:
even simple curl command from the same host receives no response from this
connector and it starts working fine after tomcat restart. At the same time
tomcat in overall looks to be healthy and another connector works fine, as this
happens from time to time on different servers, this doesn't look like to be OS
or hardware issue but something which is tomcat NIO2 specific.
And when we do any request to this NIO2 endpoint connector in a bad state - no
thread is triggered in tomcat, while looking into tomcat source code it looks
like that countdownlatch was not simply updated and service just hangs because
of this but the root cause is still not clear.
So curious what additional information we can provide to help investigate this
issue together with tomcat apache dev team?
Also, I'm not sure about your remark about custom executor - we don't use
custom one, we just configure the one form tomcat.
Regards,
Oleg.
--
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
