A
Arun Kumar Mohapatra
Guest
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(Thread.java:574) [13/04/25@13:55:59.170-0500] P-015604 T-L-9401 1 UB ---------- at com.progress.ubroker.broker.ubListenerThread.mainline(ubListenerThread.java:679) [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/ubroker.properties. Then go to the broker section and add jvmArgs there. Example: # # Sample AppServer Broker definition # [UBroker.AS.asbroker1] ..... ..... jvmArgs=-XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath= After that restart you broker. Please let me know if you have any other question. Thanks, Arun
Continue reading...
Continue reading...