My Oracle Support Banner

32-bit Oracle API Gateway Runs out of Process Address Space (Doc ID 1609304.1)

Last updated on JULY 11, 2023

Applies to:

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


The 32-bit Oracle Enterprise Gateway or Oracle API Gateway fails runs out of process address space.  A large variety of messages are possible.

One example from a Gateway trace file

ERROR   <TIMESTAMP> [<THREAD ID>]                   
java.lang.OutOfMemoryError: unable to create new native thread
      at java.lang.Thread.start0(Native Method)
      at java.lang.Thread.start(
      at com.sun.jndi.ldap.Connection.<init>(
      at com.sun.jndi.ldap.LdapClient.<init>(
      at com.sun.jndi.ldap.LdapClient.getInstance(
      at com.sun.jndi.ldap.LdapCtx.connect(
      at com.sun.jndi.ldap.LdapCtx.<init>(
      at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(
      at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(
      at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(
      at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(

One example from an hs_err log file:

# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 901000 bytes for Chunk::new



This document applies only to the 32-bit Gateway.


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.