My Oracle Support Banner

Unable To Connect To Discoverer Plus / Viewer Intermittently With '500 Internal Server Error Java.Lang.OutOfMemoryError: Unable To Create New Native Thread' Errors (Doc ID 1332528.1)

Last updated on SEPTEMBER 27, 2016

Applies to:

Oracle Discoverer - Version to [Release 10.1.2]
Information in this document applies to any platform.
*** Checked for relevance on 04-Dec-2014 ***


Intermittently users are unable to connect to Discoverer, getting error messages like

500 Internal Server Error
java.lang.OutOfMemoryError: unable to create new native thread


A connection error has occurred.
- An error occurred while creating the session. Please check for other errors.
- java.lang.OutOfMemoryError
Unable to retrieve connection list
- The connection list could not be retrieved. See other error messages for details.

contains errors:

11/04/28 12:35:50 Discoverer Model -
11/04/28 12:35:53 java.lang.OutOfMemoryError: unable to create new native thread
11/04/28 12:35:53 at java.lang.Thread.start(Native Method)
11/04/28 12:35:53 at com.evermind.util.ReleasableResourcePooledExecutor.addThread(
11/04/28 12:35:53 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor.execute(
11/04/28 12:35:53 at com.evermind.util.ThreadPool.launch(
11/04/28 12:35:53 at com.evermind.server.http.SessionAsyncInvalidateHandler.addSession(
11/04/28 12:35:53 at com.evermind.server.http.HttpApplication.checkSessionTimeouts(
11/04/28 12:35:53 at com.evermind.server.http.HttpSite.checkSessionTimeouts(
11/04/28 12:35:53 at com.evermind.server.http.SessionTimeoutTask.checkSessionTimeouts(
11/04/28 12:35:53 at
11/04/28 12:35:53 at
11/04/28 12:35:53 at com.evermind.util.ReleasableResourcePooledExecutor$
11/04/28 12:35:53 at
11/04/28 12:57:05 Logkeys: exceptions discoiv.servlet_exceptions
11/04/28 12:57:05 Discoverer Model -
<201104281203024219>: Unexpected error in state machine: java.lang.OutOfMemoryError: unable to create new native thread
<201104281203024219>: Unexpected exception in state machine: java.lang.IllegalStateException: Rollback outside started state

The only way to get around this is to bounce the mid-tier.


OC4J_BI_Forms initial heap memory had been increased from default -Xms128M to -Xms256M


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.