https://bz.apache.org/bugzilla/show_bug.cgi?id=66531
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
The deadlocks described are application issues, not Tomcat issues.
Generally, using a non-blocking API to simulate blocking I/O can lead to issues
such as these. If a WebSocket application needs blocking I/O, it is much better
to use the blocking I/O API.
If you really want to fail tasks if there are no spare threads, then configure
an Executor with maxQueueSize="0".
--
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
