Presence Of A Global-Thread-Pool Entry In Server.Xml Causes Hang on Console

(Doc ID 396800.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Containers for J2EE - Version: 10.1.3
This problem can occur on 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


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms