Presence Of A Global-Thread-Pool Entry In Server.Xml Causes Hang on Console
(Doc ID 396800.1)
Last updated on FEBRUARY 23, 2019
Applies to:Oracle Containers for J2EE - Version 10.1.3.0.0 and later
Information in this document applies to any platform.
OC4J hangs at startup when global-thread-pool element has been set in server.xml
This happens usually when editing Global-Thread-Pool in AS Control
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