'No Backend Server Available for Connection' Error in OFSAA & Java.lang.OutOfMemoryError: Java Heap Space (Doc ID 1567840.1)

Last updated on MAY 15, 2024

Applies to:

Symptoms

In Oracle Financial Services Analytical Applications (OFSAA) infrastructure, you are getting memory errors in Weblogic.  The errors appear at least once during the day as users work within OFSAA Infrastructure.  The following message appears on the screen:

Message from the NSAPI plugin:
No backend server available for connection: timed out after 10 seconds or idempotent set to OFF.

Additionally, the following errors are output to the Weblogic startup log (ex. nohup.out):

<Jul 2, 2013 10:57:53 AM CDT> <Critical> <Health> <BEA-310003> <Free memory in the server is 1,828,480 bytes. There is danger of OutOfMemoryError>

Exception in thread "ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" java.lang.OutOfMemoryError: Java heap space
Exception in thread "[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: Java heap space
Exception in thread "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: Java heap space
<Jul 2, 2013 11:27:44 AM CDT> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
 java.lang.OutOfMemoryError: Java heap space.
java.lang.OutOfMemoryError: Java heap space

You can resolve the errors by stopping and re-starting Weblogic.  However, the errors appear again after several hours.  As a result, users are having difficultly getting their work done.

Changes

Cause

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