SOA 11g Admin - Resolving Message Failure Caused by Too Many Open Files

SOA 11g Admin - Resolving Message Failure Caused by Too Many Open Files

You can receive the following error at runtime or compilation time, depending on the number of JAR files being used, the use of file descriptors by JDK 6/JRE, or both.

Message send failed: Too many open files

To resolve this error, increase the number of file descriptors to at least 4096.

Use the limit command (for the C shell) or the ulimit command (for the Bash shell) to identify the value for descriptors. A value of 1024 is typically too low, especially for JDK 6.

·                     % limit

·          

·                      cputime      unlimited

·                      filesize     unlimited

·                      datasize     unlimited

·                      stacksize    10240 kbytes

·                      coredumpsize unlimited

·                      memoryuse    unlimited

·                      vmemoryuse   unlimited

·                      descriptors  1024

·                      memorylocked 500000 kbytes

·                      maxproc      46720

Log in as the root user on your operating system.

Edit the /etc/security/limits.conf file to increase the value for descriptors.

For this example, the limits.conf file appears as follows after increasing the limit for all users to 4096:

#                

#

#*               soft    core            0

#*               hard    rss             10000

#@student        hard    nproc           20

#@faculty        soft    nproc           20

#@faculty        hard    nproc           50

#ftp             hard    nproc           0

#@student        -       maxlogins       4

# End of file

@svrgroup    soft    memlock         500000

@svrgroup    hard    memlock         500000

*           soft    nofile          4096

*           hard    nofile          4096

Close your terminal and reopen for the change to take effect. A system restart is not required.