10.1 Troubleshooting data output by Application Server : Hitachi Application Server V10 User's Guide (For Windows Systems)

What is the system information collection function?

The system information collection function collects all the information about a system configured with Application Server. If a failure occurs, you can use this function to collect a dump from when the failure occurred and collect a set of information (such as files, logs, and traces) that is necessary to identify the causes of the failure.

Required troubleshooting data to be collected

The table below lists troubleshooting data that is required when Application Server is installed, when a failure occurs while an application program is being developed, and while the system is running. Troubleshooting data is collected by using the system information collection functionality. If information cannot be collected using this functionality, you must collect it manually.

No.	An error occurs when	Content of troubleshooting data	Whether data can be collected by the system information collection functionality
1	Application Server is installed	Installation log	--
2	An application program is being developed, an Application Server system is being constructed, and the system is running	Log trace of each process	Y
3		Memory dump	Y
4		Definition and configuration information (product version information, product configuration files, etc.)	Y
5		Work directory contents	N
6		Screenshot	N
7		Standard error output	N
8		OS log (syslog)	Y
9		OS log (event log)	N
10		OS statistics (CPU usage ratio, memory consumption, number of threads, etc.)	N
11		OS status information (environment variables, results of commands including `netstat`, `ps` and `sar`)	Y

Legend:

Y: Can be collected by using the system information collection functionality.

N: Cannot be collected by using the system information collection functionality.

Categories of troubleshooting data output by Application Server

Troubleshooting data output by Application Server when an error occurs in a system where Application Server is used is categorized as below. Collect and investigate the data if necessary.

Message log: This is log information output by Java EE servers or web servers. You can use this information to check failure causes and the operating status.

Performance analysis traces

This is trace information that can track the flow of processing requests across processes. You can use this information to analyze failures or performance.

You can track request processing by comparing performance analysis data, which has IDs output by Java EE servers, with the ID identifying a request output to the request log of a web server.

Troubleshooting data for each process

This is log data or trace information output to troubleshooting data according to the characteristics of each process. The following figure illustrates the composition of a process.

[Figure]

The following table lists the troubleshooting data according to process characteristics.

No.	Process	Process characteristics and usage of data	Troubleshooting data
1	All processes	Run on the OS. You can use information output by the OS as troubleshooting data.	OS logs OS statistics OS status information Memory dump (core dump)
2	Java processes: Java EE server Domain administration server asadmin Eclipse	Run on Java VM. For Java VM layers, in addition to general Java troubleshooting data, as troubleshooting data you can use Java log or thread dump information extended for the product.	Java VM log Stack trace log Thread dump Error report file
3	Processes that handle requests: Web server Java EE server	Requests are processed across multiple processes. You can check the flow of processing requests across multiple processes.	Access log of web servers Request log of a web server Performance analysis trace
4	Java EE server	Use the explicit memory management functionality to manage session objects. In the log you can check the occurrence of events of the explicit memory management functionality.	Explicit memory management functionality event log
5		MQ Broker operates in a process. In the log you can check MQ Broker messages.	MQ Broker message log
6		Provides commands that are used during development of JSP or JAX-WS. You can check error messages in the standard error output.	Standard error output
7	Java EE server (asadmin)	Starts a Java EE server. You can check failure information before the Java EE server logger is initialized.	Process startup log
8	Eclipse	User GUI operations. You can check information (such as error information) that is output during GUI operations.	Console information Error dialog boxes
9	Eclipse	You can check Eclipse log data for further investigation.	Eclipse error log Trace log for Eclipse plug-ins

Troubleshooting data for domain administration servers

The following table lists the troubleshooting data for domain administration servers.

No.	Log name	Output destination directory	File name	Wrap time (initial value)	Size (initial value)	Number of files (initial value)	How to specify the log
1	Domain administration server message log^#	`installation_directory_for_Application_ Server/javaee/logs/domains/domain_name`	`das_messagen.log`	00:00:00	16 megabytes	8	Specify the log in a parameter of the `set-log-attributes` subcommand of the `asadmin` utility command.
2	Domain administration server stack trace log^#	`installation_directory_for_Application_ Server/javaee/logs/domains/domain_name`	`das_stacktracen.log`	00:00:00	16 megabytes	8	Specify the log in a parameter of the `set-log-attributes` subcommand of the `asadmin` utility command.
3	Domain administration server Java VM log	`installation_directory_for_Application_ Server/javaee/logs/domains/domain_name`	`das_javavmn.log`	00:00:00	128 megabytes	8	Specify the log in a parameter of the `create-jvm-options` subcommand of the `asadmin` utility command.
4	Domain administration server thread dump	`installation_directory_for_Application_ Server/javaee/logs/domains/domain_name/config`	`javacoreprocess_id.date_and_time.txt`	Output when users perform operations No limit on the size No deletion according to the number of hours or files			(No specification method)
5	Domain administration server error report file	`installation_directory_for_Application_ Server/javaee/logs/domains/domain_name/config`	`hs_err_pidprocess_id.log`	Output when a process terminates abnormally No limit on the size No deletion according to the number of hours or files			(No specification method)

#:: Part of the stack trace data is output to a message log.

Troubleshooting data for Java EE servers (server instances)

The following table lists troubleshooting data for Java EE servers (server instances).

No.	Log name	Output destination directory	File name	Wrap time (initial value)	Size (initial value)	Number of files (initial value)	How to specify the log
1	Server instance message log^#	`installation_directory_for_Application_ Server/javaee/logs/nodes/node_name/server_instance_name`	`je_messagen.log`	00:00:00	16 megabytes	8	Specify the log in a parameter of the `set-log-attributes` subcommand of the `asadmin` utility command.
2	Server instance stack trace log^#		`je_stacktracen.log`	00:00:00	16 megabytes	8	Specify the log in a parameter of the `set-log-attributes` subcommand of the `asadmin` utility command.
3	Server instance Java VM log		`je_javavmn.log`	00:00:00	128 megabytes	8	Specify the log in a parameter of the `create-jvm-options` subcommand of the `asadmin` utility command.
4	Server instance explicit memory management functionality event log		`je_eheap_eventn.log`	00:00:00	128 megabytes	8	Specify the log in a parameter of the `create-jvm-options` subcommand of the `asadmin` utility command.
5	Server instance thread dump log	`installation_directory_for_Application_ Server/javaee/glassfish/nodes/node_name/server_instance_name/config`	`javacoreprocess_id.date_and_time.txt`	Output when users perform operations No limit on the size No deletion according to the number of hours or files			(No specification method)
6	Server instance error report file		`hs_err_pidprocess_id.log`	Output when a process terminates abnormally No limit on the size No deletion according to the number of hours or files			(No specification method)

#:: Part of the stack trace data is output to a message log.

Troubleshooting data of Java EE servers (asadmin)

The following table lists the troubleshooting data for Java EE servers (asadmin).

No.	Log name	Output directory	File name	Wrap time (initial value)	Size (initial value)	Number of files (initial value)	How to specify the log
1	asadmin message log^#	`installation_directory_for_Application_ Server/javaee/ logs/commands/asadmin`	`asadmin_messagen.log`	00:00:00	16 megabytes	8	Specify the log in the `asenv` environment variable.
2	asadmin stack trace log^#		`asadmin_stacktracen.log`	00:00:00	16 megabytes	8	Specify the log in the `asenv` environment variable.
3	asadmin thread dump	`current_directory_when_command_was_executed`	`javacoreprocess_id.date_and_time.txt`	Output when users perform operations No limit on the size No deletion according to the number of hours or files			(No specification method)
4	asadmin error report file	`current_directory_when_command_was_executed`	`hs_err_pidprocess_id.log`	Output when a process terminates abnormally. No limit on the size No deletion according to the number of hours or files			(No specification method)
5	Log collected when the asadmin process was started	`installation_directory_for_Application_ Server/javaee/logs/commands/asadmin`	`asadmin_launchn.log`	00:00:00	16 megabytes	8	Specify the log in the `asenv` environment variable.

#:: Part of stack trace data is output to a message log.

Troubleshooting data for Java EE servers (application clients)

The following table lists the troubleshooting data for Java EE servers (application clients).

No.	Log name	Output directory	File name	Wrap time (initial value)	Size (initial value)	Number of files (initial value)	How to specify the log
1	Application client thread dump log	`current_directory` (the directory where the `appclient` command started)	`javacoreprocess_id.date_and_time.txt`	Output when users perform operations No limit on the size No deletion according to the number of hours or files.			(No specification method)
2	Application client error report file		`hs_err_pidprocess_id.log`	Output when a process terminates abnormally. No limit on the size No deletion according to the number of hours or files.			(No specification method)

Troubleshooting data for Java EE servers (MQ Broker)

The following table lists the troubleshooting data for Java EE servers (MQ Broker).

No.	Log name	Output directory	File name	Wrap time (initial value)	Size (initial value)	Number of files (initial value)	How to specify the log
1	MQ Broker message log	`installation_directory_for_Application_ Server/javaee/nodes/node_name/server_instance_name/imq/instances/MQ_instance_name/log`	`log_n^#.txt`	00:00:00	16 megabytes	8	Specify the log in the `config.properties` file.

#:: n = 0 to number_of_files - 1

Troubleshooting data for web servers

The following table lists the troubleshooting data for web servers.

No.	Log name	Output directory	File name	Wrap time (initial value)	Size (initial value)	Number of files (initial value)	How to specify the log
1	Access log	`installation_directory_for_Application_ Server/javaee/logs/nodes/node_name/web_server_name`	`access.n^#1`	24 hours	2 gigabytes (max.)	8	Specify the log in the `TransferLog` directive or the `CustomLog` directive.
2	Request log		`hwsrequest.n^#1`	24 hours	2 gigabytes (max.)	8	Specify the log in the `HWSRequestLog` directive.
3	Error log		`error.n^#1`	24 hours	2 megabytes (max.)	8	Specify the log in the `ErrorLog` directive.
4	Process ID log		`httpd.pid`	--	--	--	Specify the log in the `PidFile` directive.
5	Internal trace		`hws.trclog.n^#2`	--	--	2	Specify the log in the `HWSTraceLogFile` directive.
6	Shared memory ID log		`hws.trcid`	--	--	--	Specify the log in the `HWSTraceIdFile` directive.

Legend:: --: Not applicable

#1:: n = time_when_log_collection_started

#2:: n = 01 to 02

Troubleshooting data for performance tracer

The following table lists the troubleshooting data for performance tracer.

No.	Log name	Output directory	File name	Wrap time (initial value)	Size (initial value)	Number of files (initial value)	(No specification method)
1	Message log	`$PRFSPOOL/log/PRF_identifier`	`prf_messagen^#`	00:00:00	10 megabytes	8	Follow the settings on the PRF identifier and the `PRFSPOOL` environment variable specified for the process to output the log.

#:: n = 01 to 32

Troubleshooting data for application development environments (including Eclipse environments)

The following table lists the troubleshooting data for application development environments (including Eclipse environments).

No.	Log name	Output directory	File name	Wrap time (initial value)	Size (initial value)	Number of files (initial value)	How to specify the log
1	Server construction error file	`installation_directory_for_Application_Server_for_Developers/dev`	`BuildEnvironment.err`	Does not wrap according to the time.	N/A	1	(No specification method)