uCosminexus Application Server, Maintenance and Migration Guide

[Contents][Glossary][Index][Back][Next]

3.3.17 Settings for Collecting a User Dump

This section describes the settings to acquire user dumps in Windows.

Organization of this subsection
(1) When the task manager or the Windows debug tool is used (in Windows Server 2008 or Windows Vista)
(2) When using Dr. Watson (in Windows XP)
(3) Using the cjstopsv command (in Windows Server 2012, Windows Server 2008, Windows 8, Windows 7, or Windows Vista)
(4) Using the mngsvrutil command
(5) When the user dump is obtained for the forced termination of a logical server (in Windows Server 2012, Windows Server 2008, Windows 8, Windows 7, or Windows Vista)

(1) When the task manager or the Windows debug tool is used (in Windows Server 2008 or Windows Vista)

When the product hangs up, the user dump becomes necessary as the data required for troubleshooting. To obtain the user dump, use the task manager or the Windows debug tool. For details, see the Microsoft website.

Note that if you want to instantly obtain the user dump when JavaVM terminates abnormally, specify the following settings in the registry before you start the product. The registry settings affect the entire system, so take adequate precautions when you specify the settings. However, cjstartsv.exe, cjstartweb.exe, cjclstartap.exe, and adminagent.exe are automatically set up when the product is installed.

(2) When using Dr. Watson (in Windows XP)

We recommend that you use Dr. Watson (drwtsn32) as the Windows debug tool in Windows XP. When acquiring user dumps using Dr. Watson, you need to set Dr. Watson so that you can use Dr. Watson. Set up Dump symbol table, Dump all thread context, and Create the crash dump file as options of Dr. Watson. For details about how to use Dr. Watson, see the manual provided with the OS.

Note that if you want to instantly obtain the user dump when JavaVM terminates abnormally, specify the following settings:

  1. Execute drwtsn32 -i to install Dr. Watson as the prescribed application debugger.
    When you execute this command, the value Auto in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug key of the registry, changes to 1.
  2. In the Windows Control Panel, select System, and in the Details Preference tab, click the Error Report button, and specify the following settings:
    • Select the Disable error report radio button
    • Clear the Report the serious errors check box

To collect a user dump when process hang up occurs, obtain userdump.exe provided by Microsoft. For details, see the homepage of Microsoft Corp.

(3) Using the cjstopsv command (in Windows Server 2012, Windows Server 2008, Windows 8, Windows 7, or Windows Vista)

When acquiring user dumps using the -fd option of the cjstopsv command, you must set up the output destination directory of the user dump in the environment variable CJMEMDUMP_PATH. File name of the user dump is cjmemdump.dmp.

The following is a setup example of the environment variable CJMEMDUMP_PATH:

Setup example of the environment variable CJMEMDUMP_PATH
set CJMEMDUMP_PATH=C:\temp
In the above-mentioned example, cjmemdump.dmp is created under C:\temp.

When specifying the environment variable CJMEMDUMP_PATH, note the followings:

(4) Using the mngsvrutil command

When acquiring user dumps using the sub command dump of the mngsvrutil command, obtain userdump.exe provided by Microsoft Corp. to acquire user dumps when process hang up occurs. For details, see the homepage of Microsoft Corp.

Note
If the version of the obtained userdump.exe is Microsoft "User Mode Process Dumper Version 8.1", implement the following after installation:
  • As a preparatory operation before using the mngsvrutil command to acquire the user dump, check whether userdump.exe exists in the operating environment.
  • If multiple userdump.exe exists, change the system environment variable PATH in such way so that the storage location of userdump.exe provided by Microsoft, appears at the beginning.
To apply the details changed in the system environment variables, restart the OS.
Also, when a J2EE server is started as a logical server from Management Server, do not use this command for forced termination. If this command is used for forced termination, Management Server determines that the J2EE server terminated abnormally and executes the operations.

(5) When the user dump is obtained for the forced termination of a logical server (in Windows Server 2012, Windows Server 2008, Windows 8, Windows 7, or Windows Vista)

When you use Management Server to set up the system, specify the output destination directory of the user dump in the environment variable CJMEMDUMP_PATH to obtain the user dump for the forceful termination of the logical server. If you specify this environment variable, the user dump can be collected beneath the directory specified in this environment variable when the logical J2EE server and logical SFO server (compatibility functionality) are terminated forcefully. The user dump file name is cjmemdump.dmp. For details, see 4.1.11 Setting environment variables of the system in the uCosminexus Application Server System Setup and Operation Guide.