Force/Abrupt Shutdown (SIGKILL) Of Coherence JVMs Using IMB Protocol On Exalogic Linux Compute Nodes May Lead To Kernel Panic
(Doc ID 1519871.1)
Last updated on MARCH 29, 2019
Applies to:Oracle Coherence - Version 3.7.1 and later
Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.0 and later
In Exalogic Linux physical & virtual releases running with Oracle Enterprise Linux operating system, a forced/abrupt shutdown (SIGKILL) of Coherence JVMs running the IMB transport protocol may lead to a system panic if the system is configured with Large Pages (the default setting in Exalogic). Commands like “kill -9” or any system level calls which trigger SIGKILL signal to force shutdown Coherence JVM instances may lead to this kernel panic situation. Graceful shutdown (SIGTERM) of Coherence JVMs doesn’t show this behavior. The following message appears in syslog at the time of the issue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document