https://issues.apache.org/bugzilla/show_bug.cgi?id=56724
Bug ID: 56724
Summary: Restart Container background thread if it died
unexpectedly
Product: Tomcat 8
Version: 8.0.9
Hardware: PC
Status: NEW
Severity: enhancement
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: knst.koli...@gmail.com
To address the issue that has been raised several times on the mailing lists,
e.g.
http://tomcat.markmail.org/thread/xooxcq56ehki63dh
"ContainerBackgroundProcessor and compounding OOMEs"
http://tomcat.markmail.org/thread/f6b6vicg7kusckra
"Background thread died; no errors in log; invoking backgroundProcess via JMX
has no effect"
I think it is OK to start a new background thread after some delay. If the
start succeeds, it will be a new thread with its own (clean) stack.
It may help for StackOverflowError.
It might partially help with OutOfMemoryError thread death if nothing else is
available, but a better strategy for an admin to handle an OutOfMemoryError is
to start JVM with -XX:OnOutOfMemoryError flag with a script that shuts down
(and restarts) Tomcat.
--
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
