Client Java Crash1
Client Java Crash1
IBM Ireland
IBM Ireland
IBM Ireland
Why is javacore*.txt and *.dmp not created in in the workspace\logs directory and how to fix it.
Java files will always be created under: C:\Program Files\IBM\lotus\notes\data\workspace\logs\javacore.xxxx.xxxx.txt But is Configurable in the rcplauncher.properties filercp.data=<workspace path> We collecting data most customer just send in the nsds , we should always advice to us ethe ADC tool as it collect all the files related for debugging, java cores and only applicable to the notes2.exe process Starting in 8.5.2, NSD will detect if the FATAL stack has JVM libraries loaded and dump a full system core dump Java frame found in fatal thread stack. Setting up core flags for use with IBM JVM diagnostic tools. To disable set DisableAutoJavaCore=1 in the nsd.ini. To customize set AutoJavaCoreFlags in the notes.ini
>
IBM Ireland
IBM Ireland
IBM Ireland
Identify reason for OutOfMemoryError: In ENVINFO section, check minimum and maximum heap size settings: 2CIUSERARG 2CIUSERARG 1STHEAPFREE -Xms48m -Xmx256m
In MEMINFO section, check Heap Space Free and Heap Space Allocated Bytes of Heap Space Free: 28CB58 1STHEAPALLOC Bytes of Heap Space Allocated: 10000000
If heap space allocated is close to max heap size, the java heap was filled to capacity If the heap has not reached maximum size, the problem could be lack of native memory, such as when creating a thread. java.lang.OutOfMemoryError: Failed to create a thread.
IBM Ireland
Start->All Programs->Lotus Applications-> Support->Collect Lotus Notes diagnostics data and leave Notes running.
This will collects two rounds of calls stack in the NSD and 2 java cores 15 seconds between each collection On the command line: nsd -hang -repeat=<number of collections> -delay=<milliseconds between collections> See nsd -help for additional details on the -hang switch. Starting in 8.5.2 nsd can find the notes.ini of the current user automatically
IBM Ireland
Hangs
keys: 1. Compare the two NSD logs, see if the UI thread for NLNOTES is stuck in same stack. 2. In javacore THREADS section, check the stack and state for java UI thread: "main" TID:0x00140200, j9thread_t:0x000166F4, state:B, prio=6 Java core dump , search for state:B, BLOCKED 3. Since the UI thread main in in B (blocked) state, go to LOCKS section in core dump to find out what blocked it In this example, javacore LOCKS section shows main thread is waiting for a monitor held by Worker-1: 2LKMONINUSE sys_mon_t:0x059C2514 infl_mon_t: 0x059C254C:
3LKMONOBJECT com/ibm/rcp/accounts/internal/AccountsManagerImpl@114BEBF8/114BEC04: Flat locked by "Worker-1" (0x05C03500), entry count 1 3LKWAITERQ 3LKWAITER 3LKWAITER 3LKWAITER Waiting to enter: "main" (0x00140200) "Worker-3" (0x05F0E900) "Worker-6" (0x05F40D00)
IBM Ireland
10
IBM Ireland
Good References
(1) Expeditor - Troubleshooting trace logs http://w3.tap.ibm.com/medialibrary/media_view?id=95984 (2) Javacore Analysis (Nik Brauer) http://w3.tap.ibm.com/medialibrary/media_view?id=98850 (covers some XPD log analysis)
11