7.3.12 dump
This subcommand outputs the javacore of an active logical server.
The following table lists and describes the argument that can be specified for the dump subcommand.
|
Argument |
Explanation |
Target specification |
|
|---|---|---|---|
|
Logical server |
Host |
||
|
server [addition]# |
Outputs the javacore (active time information) for the logical server specified by the -t option. Only a J2EE server (including a J2EE cluster member), a J2EE server cluster, CTM, or the naming service can be specified as the logical server. If addition is specified, the subcommand acquires a core file for the logical server specified in the -t option. In Windows, do not specify addition. |
Y |
-- |
- Legend:
-
Y: Can be specified.
--: Cannot be specified.
- #
-
When server addition is specified, the method of monitoring the activity of the specified logical server switches to process existence checking only.
The commands that are executed to output the javacore and the javacore file output destinations are described for each OS type.
- Organization of this subsection
(1) In Windows
The table below shows the commands that are executed to output the javacore and the javacore file output destinations for each logical server type in Windows.
|
Logical server |
addition specified |
Command to be executed |
Output information |
javacore file output destination directory |
|---|---|---|---|---|
|
J2EE server (including server cluster) |
Not specified |
cjdumpsv |
javacore |
J2EE-server-work-directory\ejb\executing-server-name\ |
|
CTM |
Specified or not specified#1 |
hdumpns |
javacore#2 |
Cosminexus-installation-directory\TPB\logj\ |
|
Naming service |
Specified or not specified#1 |
hdumpns |
javacore |
Cosminexus-installation-directory\TPB\logj\ |
- #1
-
The addition specification is ignored and the activity monitoring method is not changed.
- #2
-
The javacore that is output when CTM is specified in the logical server, is not the information about the CTM daemon, but is the information about the Naming Service started for the CTM.
(2) In UNIX
The table below shows the commands that are executed to output the javacore and the javacore file output destinations for each logical server type in UNIX.
|
Logical server |
addition specified |
Command to be executed |
Output information |
javacore file output destination directory |
|---|---|---|---|---|
|
J2EE server (including cluster) |
Specified |
javacore -f -p#1 |
javacore, core |
J2EE-server-work-directory/ejb/real-server-name/ |
|
Not specified |
cjdumpsv |
javacore |
J2EE-server-work-directory/ejb/real-server-name/ |
|
|
CTM |
Specified or not specified#2 |
kill -3 |
javacore#3 |
/opt/Cosminexus/TPB/logj/ |
|
Naming service |
Specified or not specified#2 |
kill -3 |
javacore |
/opt/Cosminexus/TPB/logj/ |
- #1
-
The gdb package must be installed.
- #2
-
The addition specification is ignored and the activity monitoring method is not changed.
- #3
-
The javacore that is output when CTM is specified in the logical server, is not the information about the CTM daemon, but is the information about the Naming Service started for the CTM.