========================================================================
Applies To:
Linux Version: OEL-6.5
WLS - 10.3.6
OSB - 11.1.1.7
========================================================================
Problem:
OSB becomes unavailable/unresponsive under heavy load.
Error:
java.lang.OutOfMemoryError: Resource temporarily unavailable in tsStartJavaThread (lifecycle.c:1097).
Attempting to allocate 8096M bytes
There is insufficient native memory for the Java
Runtime Environment to continue.
Possible reasons:
The system is out of physical RAM or swap space
In 32 bit mode, the process size limit was hit
Possible solutions:
Reduce memory load on the system
Increase physical memory or swap space
Check if swap backing store is full
Use 64 bit Java on a 64 bit OS
Decrease Java heap size (-Xmx/-Xms)
Decrease number of Java threads
Decrease Java thread stack sizes (-Xss)
Disable compressed references (-XXcompressedRefs=false)
========================================================================
Cause:
/etc/security/limits.conf file nproc value is overwritten by /etc/security/limits.d/90-nproc.conf and setting max user processes 1024
========================================================================
Resolution:
We need to change nproc value in /etc/security/limits.d/90-nproc.conf
Default Values:
# Default limit for number of user's processes to prevent
# accidental fork bombs.
# See rhbz #432903 for reasoning.
* soft nproc 1024
root soft nproc unlimited
New Values:
# Default limit for number of user's processes to prevent
# accidental fork bombs.
# See rhbz #432903 for reasoning.
* soft nproc unlimited
root soft nproc unlimited
Applies To:
Linux Version: OEL-6.5
WLS - 10.3.6
OSB - 11.1.1.7
========================================================================
Problem:
OSB becomes unavailable/unresponsive under heavy load.
Error:
java.lang.OutOfMemoryError: Resource temporarily unavailable in tsStartJavaThread (lifecycle.c:1097).
Attempting to allocate 8096M bytes
There is insufficient native memory for the Java
Runtime Environment to continue.
Possible reasons:
The system is out of physical RAM or swap space
In 32 bit mode, the process size limit was hit
Possible solutions:
Reduce memory load on the system
Increase physical memory or swap space
Check if swap backing store is full
Use 64 bit Java on a 64 bit OS
Decrease Java heap size (-Xmx/-Xms)
Decrease number of Java threads
Decrease Java thread stack sizes (-Xss)
Disable compressed references (-XXcompressedRefs=false)
========================================================================
Cause:
/etc/security/limits.conf file nproc value is overwritten by /etc/security/limits.d/90-nproc.conf and setting max user processes 1024
========================================================================
Resolution:
We need to change nproc value in /etc/security/limits.d/90-nproc.conf
Default Values:
# Default limit for number of user's processes to prevent
# accidental fork bombs.
# See rhbz #432903 for reasoning.
* soft nproc 1024
root soft nproc unlimited
New Values:
# Default limit for number of user's processes to prevent
# accidental fork bombs.
# See rhbz #432903 for reasoning.
* soft nproc unlimited
root soft nproc unlimited
No comments:
Post a Comment