-
Type:
Bug
-
Status: Resolved
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: Messaging/Client, Messaging/Internode
-
Labels:None
-
Bug Category:Availability - Process Crash
-
Severity:Normal
-
Complexity:Low Hanging Fruit
-
Discovered By:Code Inspection
-
Platform:All
-
Impacts:None
-
Since Version:
-
Source Control Link:
-
Test and Documentation Plan:
Netty (at least, and perhaps elsewhere in Executors) catches all exceptions, so presently there is no way to ensure that an OOM reaches the JVM handler to trigger a crash/heapdump.
It may be that the simplest most consistent way to do this would be to have a single thread spawned at startup that waits for any exceptions we must propagate to the Runtime.
We could probably submit a patch upstream to Netty, but for a guaranteed future proof approach, it may be worth paying the cost of a single thread.