Java.lang.OutOfMemoryError: Unable To Create New Native Thread While Starting SOA/OSB Managed Servers
(Doc ID 2244964.1)
Last updated on DECEMBER 15, 2023
Applies to:
Oracle SOA Suite - Version 12.1.3.0.0 and laterOracle Service Bus - Version 12.1.3.0.0 and later
Information in this document applies to any platform.
Symptoms
A new clustered 12c domain has been created with AdminServer, WSM Servers, OSB servers, and SOA servers.
The AdminServer and WSM Servers are starting up fine, but when the OSB or SOA servers are started, the errors below are seen:
(thread=[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: (Wrapped) java.lang.OutOfMemoryError: unable to create new native thread
at com.tangosol.coherence.component.util.Daemon.start(Daemon.CDB:46)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:8)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.startSystemServices(Cluster.CDB:11)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:53)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:12)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:32)
at com.tangosol.coherence.component.util.SafeCluster.getRunningCluster(SafeCluster.CDB:7)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:5)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:537)
at weblogic.coherence.service.internal.WLSCoherenceConfigurator.configureCoherence(WLSCoherenceConfigurator.java:142)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
at com.tangosol.coherence.component.util.Daemon.start(Daemon.CDB:46)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:8)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:6)
at com.tangosol.coherence.component.net.Cluster.startSystemServices(Cluster.CDB:11)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:53)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:12)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:4)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:10)
at com.tangosol.coherence.component.util.SafeCluster.ensureRunningCluster(SafeCluster.CDB:32)
at com.tangosol.coherence.component.util.SafeCluster.getRunningCluster(SafeCluster.CDB:7)
at com.tangosol.coherence.component.util.SafeCluster.start(SafeCluster.CDB:5)
at com.tangosol.net.CacheFactory.ensureCluster(CacheFactory.java:537)
at weblogic.coherence.service.internal.WLSCoherenceConfigurator.configureCoherence(WLSCoherenceConfigurator.java:142)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
and
The WebLogic Server encountered a critical failure
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at com.octetstring.vde.LDAPServer.run(LDAPServer.java:199)
Reason: There is a panic condition in the server. The server is configured to exit on panic
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(Thread.java:714)
at com.octetstring.vde.LDAPServer.run(LDAPServer.java:199)
Reason: There is a panic condition in the server. The server is configured to exit on panic
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 |
| Cause |
| Solution |
| References |