https://bz.apache.org/bugzilla/show_bug.cgi?id=62185
BogdanD <bogdan.du...@enghouse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |---
Status|RESOLVED |REOPENED
--- Comment #4 from BogdanD <bogdan.du...@enghouse.com> ---
(In reply to Mark Thomas from comment #1)
> That is an (OS) configuration error, not a Tomcat bug.
>
> Generally, OOME are not expected to be recoverable. If Tomcat experiences
> one it needs to be shutdown (if it isn't already) and restarted.
Hi guys, thanks for the replies. I understand the root cause is the
"misconfiguration" but do you consider it as normal behavior to have the Apache
process(after the exception) up and running but not accepting any request since
it's Acceptor thread is gone forever?
We consider this an improper handling of the case when Tomcat cannot create new
worker threads(The OOME thrown by the JVM is also a bit misleading in this
case, because is not a memory issue).
We encountered this in a production environment, during a spike and also
because there were other processes running and forking in the same UID as
Tomcat. The Tomcat process was still up but it couldn't accept new connections.
--
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
