My Oracle Support Banner

Gateway Fails With "java.lang.OutOfMemoryError: unable to create new native thread." (Doc ID 2108877.1)

Last updated on MAY 06, 2019

Applies to:

Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.

Symptoms

An Oracle API Gateway (OAG) instance fails with

java.lang.OutOfMemoryError: unable to create new native thread

 

Changes

The problem is more likely to occur on Windows, where the maximum process address space for 32-bit Java applications is a mere 2 GBytes.

The problem is more likely to occur when the initial and minimum size of the Java heap has been increased by setting -Xms to a large value.

The problem is more likely to occur during high load.

The problem is more likely to occur when the system is undersized (not enough memory).

The problem is more likely to occur on newer Linux versions, where changed glibc behavior
massively increases the memory usage of multithreaded applications.

Cause

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
Symptoms
Changes
Cause
Solution
 32-bit Gateway
 32-bit Gateway: Check that size of Java heap and permanent generation is not too large
 Use the 64-bit Gateway on 64-bit Linux
 32-bit Gateway on Linux or Solaris: check stack size (ulimit -s)
 32-bit Gateway on Solaris, large number of threads
 Is the system low on memory?
 Gateway uses unexpectedly large amount of memory on Linux
 User quotas and resource caps
 Solaris specific: zones configuration
 Linux specific: max user processes
References


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