server dump command
Creates a snapshot of a server and saves the result into an archive file for further tuning and diagnosis.
Useful for problem diagnosis of an Open Liberty server because the result file contains server configuration, log information, and details of the deployed applications in the work area directory. The command can be applied to either a running or a stopped server.
For a running server, the following information is also included:
State of each OSGi bundle in the server
Wiring information for each OSGi bundle in the server
Component list that is managed by the Service Component Runtime (SCR) environment
Detailed information of each component from SCR
Configuration administration data of each OSGi bundle
Information about registered OSGi services
Runtime environment settings such as Java virtual machine (JVM), heap size, operating system, thread information, and network status
Create a dump file of thread information from the
myserver server in a ZIP archive called
server dump myserver --archive="myserver.zip" --include=thread
Create a snapshot of the
myserver server status in a ZIP archive called
server dump myserver --archive=myserver.zip --include=heap
Run the command from the
server dump serverName [options]
The name of the server to run the command against. If no server is specified, a server called
defaultServeris automatically created to run the command against.
One or more optional parameters.
Specifies a target file for the
Specifies the type of diagnostic information to be captured. The value of
The thread dump type is supported only when the server is running on the Java SDK. If the server is started with a JRE, an error is reported indicating that the server does not support the dump type. This restriction applies to HotSpot virtual machines only; the thread Java dump type is supported on any IBM JVM (JRE or SDK).
The following exit codes are available for the
server dump command and the equivalent executable JAR file
OK. 0 indicates successful completion of the requested operation.
1 indicates that the JVM options that were used are not valid.
2 indicates that the server does not exist.
Exit codes greater than or equal to 20 indicate that an error occurred while performing the request. Messages are printed and captured in log files with more information about the error.