AppServer crash

Posted by Riverside Software on 16-Oct-2017 08:53

Hello all,

If an appserver (running 11.x) broker crashes due to an uncaught exception (let's say an OutOfMemoryException or a division by zero), would there be a log file somewhere ? Where do stdout and stderr go when the broker is started ? To the *.broker.log ? 


All Replies

Posted by Arun Kumar Mohapatra on 17-Oct-2017 09:26

Hi Gilles,

Normally OutOfMemoryException exception logged in broker.log file, with very less information like below:


[13/04/25@13:55:59.169-0500] P-015604 T-L-9401 3 UB Basic Got a connection:: (8125)

[13/04/25@13:55:59.170-0500] P-015604 T-L-9401 1 UB ---------- Unhandled exception caught in L-9401. (8419)

[13/04/25@13:55:59.170-0500] P-015604 T-L-9401 1 UB ---------- java.lang.OutOfMemoryError: unable to create new native thread

[13/04/25@13:55:59.170-0500] P-015604 T-L-9401 1 UB ---------- at java.lang.Thread.start0(Native Method)

[13/04/25@13:55:59.170-0500] P-015604 T-L-9401 1 UB ---------- at java.lang.Thread.start(

[13/04/25@13:55:59.170-0500] P-015604 T-L-9401 1 UB ---------- at

[13/04/25@13:55:59.170-0500] P-015604 T-L-9401 1 UB ---------- at


If you really need to know exact reason of OOM, then heap dump file is needed for that you need to set jvmArgs for your broker.

Go to DLC/properties/

Then go to the broker section and add jvmArgs there.



      # Sample AppServer Broker definition





               jvmArgs=-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=<Path_Where_to dump>

After that restart you broker.

Please let me know if you have any other question.



This thread is closed