OC4J Fails to Shutdown Gracefully when Using Log4J in the Application
(Doc ID 353354.1)
Last updated on MARCH 18, 2020
Applies to:Oracle Containers for J2EE - Version 10.1.2.0.0 and later
Information in this document applies to any platform.
This problem can occur on any platform.
An OC4J instance, hosting a J2EE Application that uses Log4J for logging, hangs when shutdown is issued using the OPMN command, opmnctl, or the Application Server Console. The OC4J instance process has to be killed forcefully to shut it down.
Another symptom noticed is that OC4J starts leaking memory due to the hanging threads - this can especially be seen if one attempts a deploy & undeploy of the application in question.
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