Consultor Eletrônico



Kbase 21574: OutOfMemoryError: Cannot Create Any More Threads - AIX
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   16/10/2008
Status: Unverified

FACT(s) (Environment):

IBM AIX
Progress 9.1A
Progress 9.1B

SYMPTOM(s):

Unhandled exception caught in <threadName>. (8419)

Using Java version installed by Progress.

The following errors (displayed within log files) are seen with AppServer/WebSpeed broker(s) running ~100 servers/agents

ERRORS:
Unhandled exception caught in L-7120. (8419)
java.lang.OutOfMemoryError: cannot create any more threads
at com.progress.ubroker.broker.
ubListenerThread.mainline(Compiled Code)
at com.progress.ubroker.broker.
ubListenerThread.run(Compiled Code)

Unhandled exception caught in S-0105. (8419)
java.lang.OutOfMemoryError: cannot create any more threads
at java.lang.UNIXProcess.<init>(Compiled Code)
at java.lang.Runtime.exec(Compiled Code)
at java.lang.Runtime.exec(Compiled Code)
at com.progress.ubroker.broker.ubServerThread.
startServer(Compiled Code)
at com.progress.ubroker.broker.
ubServerThread.processStartup(Compiled Code)
at com.progress.ubroker.broker.
ubASserverThread.processStartup(Compiled Code)
at com.progress.ubroker.broker.
ubServerThread.processEvent(Compiled Code)
at com.progress.ubroker.broker.
ubServerThread.mainline(Compiled Code)
at com.progress.ubroker.broker.
ubServerThread.run(Compiled Code)

CAUSE:

Progress 9.1A and 9.1B install Java 1.1.8 (JRE and JDK). IBM's Java version 1.1.8 seems to require more resources from the system to start threads, causing the error described depending on users system settings.

Verify the following System Settings:

1) Kernel parameter MAXUPROC is set properly
2) Increase the ulimit data area for the user that starts the AdminServer.

For instance: ulimit -d unlimited

3) Set the Java parameters -ss and -oss in the $DLC/bin/java_env script, in the JVMARGS variable.

For example: JVMARGS="-ms1m -oss100k -ss50k"

Decreasing the values for both parameters will require less resources for each Java thread.

FIX:

The problem is not seen in Progress 9.1C, which runs JRE/JDK version 1.3. Upgrade to Progress 9.1C