4.3.1 Acquiring the Cosminexus Component Container Logs

This section describes the types and output destinations of Cosminexus Component Container logs. The Cosminexus Component Container logs include the following logs:

J2EE server, server management command logs
Administration agent, Management agent, Management Server logs
Internal setup tool of the virtual server manager and Server Communication Agent logs
Integrated user management logs
Cosminexus JMS Provider logs

The output destination of each of the log is described below.

Organization of this subsection

(1) Acquiring the J2EE server, server management command logs
(2) Acquiring the log of Administration agent, Management agent, and Management Server
(3) Acquiring the logs of the internal setup tool of the virtual server manager and Server Communication Agent
(4) Acquiring the integrated user management log
(5) Collecting Cosminexus JMS Provider logs
(6) Required information to be acquired other than a log

(1) Acquiring the J2EE server, server management command logs

This section describes the method for acquiring the J2EE server, server management command logs.

Also, in Cosminexus Component Container, the migration command logs are output besides these logs. When the resource depletion monitoring function is used, the resource depletion monitoring log is output.

The five types of J2EE server logs are the message log, user log, exception log, access log, and maintenance log. Note that in addition to these logs, event log or syslog are output in the case of starting, stopping, and abnormal termination of a J2EE server.
The three types of server management command logs are message log, exception log, and maintenance log.
In the resource adapter version up command (cjrarupdate) log, there are three types of logs, message log, exception log, and maintenance log.
The three types of migration command logs are message log, exception log, and maintenance log.

Each of these logs is described below:

Message log

The operation status of a J2EE server, server management command, and migration command is output. Message log is used as the operation monitoring information for various types of servers and commands.

User log

The information of the standard output and the standard error output in the application is output in the user log. Use this log to check the operation when developing the application. Note that if you specify the java.security.debug property and start the server, the standard output and standard error output information is not output to the user log. This log also includes the JavaVM memory related logs.

Exception log

The exception information of Cosminexus Component Container is output when a problem occurs in the system. Note that you need not monitor the exception log in daily operations. Use this log to reference exception information if a message is output to the log.

Access log

The processing results of requests to Web applications and the communication history of WebSocket are output.

Maintenance log

The error maintenance information of Cosminexus Component Container is output when a problem occurs in the system. Maintenance personnel use this log to analyze the errors that occur in Cosminexus Component Container.

Event log (in Windows)

The information indicating start, stop, or abnormal termination of a J2EE server is output to this log. The output destination differs depending on the Windows event log settings.

Note that the event log is not output depending on how the J2EE server has been stopped. In the following cases, there are times when the log is not output correctly:

When a problem occurs in JavaVM itself when the J2EE server is running
When the J2EE server process is stopped externally by TerminateProcess
When the J2EE server terminates abnormally due to insufficient memory when the -XX:+HitachiOutOfMemoryAbort option is specified to start the JavaVM.

Note that the -XX:+HitachiOutOfMemoryAbort option is set by default.

syslog (in UNIX)

The information indicating start, stop, or abnormal termination of a J2EE server is output to this log. The output destination differs depending on the settings in the UNIX syslog.

Note that the syslog is not output depending on how the J2EE server has been stopped. In the following cases, there are times when the log is not output correctly:

When a problem occurs in JavaVM itself when the J2EE server is running
When the J2EE server process is stopped externally by the SIGKILL signal (such as kill -9)
When the J2EE server terminates abnormally due to insufficient memory when the -XX:+HitachiOutOfMemoryAbort option is specified to start the JavaVM.

Note that the -XX:+HitachiOutOfMemoryAbort option is set by default.

Resource depletion monitoring log

When using the resource depletion monitoring function, the resource depletion monitoring information about the resources being monitored is output. Use it for investigating the cause if the resource usage or the used resource quantity exceeds the threshold value.

The log is recorded in an order starting from the log file attached with the smallest file number. When one log file size attains the maximum size for one file, the log is recorded in the log file attached with the next file number. When the last log file (log file attached with the file count number) size attains the maximum size for one file, the log file of file number 1 is made empty and the log is recorded in that file. Thereafter, the log is recorded in the log files in the order of the file number by emptying those log files before recording a new log.

The following table describes the default of log output destination. The Cosminexus Component Container log can be acquired according to the server or command.

The working-directory shown in the log output destination indicates a directory specified in the ejb.public.directory parameter in the <configuration> tag of the logical J2EE server (j2ee-server) of the Easy Setup definition file. The default value is Cosminexus-installation-directory\CC\server\public (in Windows) or /opt/Cosminexus/CC/server/public (in UNIX).

(a) J2EE server log

Table 4‒3: Output destination of the J2EE server log (Default)
Category	Contents	Log output destination and log file name^#1	Default size × number of files	Channel name
Message log	Operation log	In Windows `ejb.server.log.directory`^#2`\cjmessage[n].log` In UNIX `ejb.server.log.directory`^#2`/cjmessage[n].log`	1MB × 2	MessageLogFile
	Log operation log^#3	In Windows `<ejb.server.log.directory>`^#2`\cjlogger.log` In UNIX `<ejb.server.log.directory>`^#2`/cjlogger.log`	1MB × 2	--
	Operation log of resource adapter that is deployed and used as a J2EE resource adapter^#⁴	In Windows (Resource adapter of Connector 1.0 specifications) `ejb.server.log.directory`^#2`\connectors\resource-adapter-display-name[n].log` (Resource adapter of Connector 1.5 specifications) `<ejb.server.log.directory>`^#2`\connectors\resource-adapte-display-name_connection-defintion-arrangement-order_[n].log` In UNIX (Resource adapter of Connector 1.0 specification) `ejb.server.log.directory`^#2/`connectors/resource-adapter-display-name[n].log` (Resource adapter of Connector 1.5 specification) `<ejb.server.log.directory>`^#2`/connectors/resource-adapter-display-name_connetion-definition-arrangement-order_[n].log`	2 MB × 4	--
	Operation log of resource adapter used in a J2EE application^#⁴	In Windows (Resource adapter of normal mode/Connector 1.0 specifications) `<ejb.server.log.directory>`^#2`\connectors\J2EE` `application-name\resource-adapter-display-name[n].log` (Resource adapter of test mode/Connector 1.0 specifications) `<ejb.server.log.directory>`^#2`\connectors\test#J2EE-application-name\resource-adapter-display-name[n].log` (Resource adapter of `normal mode/Connector 1.5` specifications) `<ejb.server.log.directory>`^#2`\connectors\J2EE-application-name\resource-adapter-display-name_connection-defintion-arrangement-order_[n].log` (Resource adapter of test mode/Connector 1.5 specifications) `<ejb.server.log.directory`^#2`>\connectors\test#J2EE-application-name\resource-adapter-display name_connection-defintion-arrangement-order_[n].log` In UNIX (Resource adapter of normal mode/Connector 1.0 specifications) `<ejb.server.log.directory>`^#2`/connectors/J2EE-application-name/resource-adapter-display-name[n].log` (Resource adapter of test mode/Connector 1.0 specifications) `<ejb.server.log.directory>`^#2`/connectors/test#J2EE- application-name/resource-adapter-display-name [n].log` (Resource adapter normal mode/Connector 1.5 specifications) `<ejb.server.log.directory>`^#2`/connectors/J2EE-application-name/resource-adapter-display-name_connection-defintion-arrangement-order_[n].log` (Resource adapter of test mode/Connector 1.5 specifications) `<ejb.server.log.directory>`^#2`/connectors/test#J2EE-application-name/resource-adapter-display-name _connection-definition-arrangement-order_[n].log`	2 MB × 4	--
User log	Web servlet log^#⁵	In Windows `ejb.server.log.directory`^#2`\web_servlet[n].log` In UNIX `ejb.server.log.directory`^#2`/web_servlet[n].log`	4MB × 4	WebServletLogFile
	User output log	In Windows `ejb.server.log.directory`^#2`\user_out[n].log` In UNIX `ejb.server.log.directory`^#2`/user_out[n].log`	1MB × 2	UserOutLogFile
	User error log	In Windows `ejb.server.log.directory`^#2`\user_err[n].log` In UNIX `ejb.server.log.directory`^#2`/user_err[n].log`	1MB × 2	UserErrLogFile
	JavaVM maintenance information and GC log	In Windows `ejb.server.log.directory`^#2`\javalog[nn].log` In UNIX `ejb.server.log.directory`^#2`/javalog[nn].log`	4MB × 4	--
	Event log of Explicit Memory Management functionality	In Windows `ejb.server.log.directory`^#2`\ehjavalog[nn].log` In UNIX `ejb.server.log.directory`^#2`/ehjavalog[nn].log`	4MB × 4	--
Exception log	Exception information when an error occurs	In Windows `ejb.server.log.directory`^#2`\cjexception[n].log` In UNIX `ejb.server.log.directory`^#2`/cjexception[n].log`	1MB × 2	ExceptionLogFile
Maintenance log	Maintenance information	In Windows `<ejb.server.log.directory>`^#2`\CC\maintenance\cjmaintenance[n].log` In UNIX `ejb.server.log.director`^#2`/CC/maintenance/cjmaintenance[n].log`	16MB × 4	MaintenanceLogFile
	Console message	In Windows `<ejb.server.log.directory>`^#2`\CC\maintenance\cjconsole[n].log` In UNIX `ejb.server.log.directory`^#2`/CC/maintenance/cjconsole[n].log`	1MB × 2	ConsoleLogFile
	EJB container maintenance information	In Windows `<ejb.server.log.directory>`^#2`\CC\maintenance\cjejbcontainer[n].log` In UNIX `ejb.server.log.directory`^#2`/CC/maintenance/cjejbcontainer[n].log`	1MB × 2	EJBContainerLogFile
	Web container maintenance information	In Windows `<ejb.server.log.directory>`^#2`\CC\maintenance\cjwebcontainer[n].log` In UNIX `ejb.server.log.directory`^#2`/CC/maintenance/cjwebcontainer[n].log`	1MB × 2	WebContainerLogFile
	Start process standard output information^#⁶	In Windows <ejb.server.log.directory>^#2`\CC\maintenance\cjstdout.log` In UNIX `ejb.server.log.directory`^#2`/CC/maintenance/cjstdout.log`	--	--
	Start process standard error information^#⁶	In Windows `<ejb.server.log.directory>`^#2`\CC\maintenance\cjstderr.log` In UNIX `ejb.server.log.directory`^#2`/CC/maintenance/cjstderr.log`	--	--
	Termination process information	In Windows `<ejb.server.log.directory>`^#2`\CC\maintenance\cj_shutdown[n].log` In UNIX `ejb.server.log.directory`^#2`/CC/maintenance/cj_shutdown[n].log`	4KB × 2^#⁷	--
	Trace log for Web container maintenance	In Windows `<ejb.server.log.directory>`^#2`\CC\maintenance\cjweb_access[n].log` In UNIX `<ejb.server.log.directory>`^#2`/CC/maintenance/cjweb_access[n].log`	4 MB × 16	WebAccessLogFile
	RMI communication log of J2EE server	In Windows `<ejb.server.log.directory>`^#2`\CC\rmi\cjrmi[n].log` In UNIX `<ejb.server.log.directory>`^#2`/CC/rmi/cjrmi[n].log`	1MB × 4	--
Event log	Log showing J2EE server start, stop or abnormal termination	Application log of Windows event viewer^#⁸	--	--
syslog	Log showing J2EE server start, stop or abnormal termination	Depends on UNIX syslog settings.^#⁹	--	--
Debug log	Log for checking development	In Windows `<ejb.server.log.directory>`^#2`\cjdevelopment[n].log` In UNIX `<ejb.server.log.directory>`^#2`/cjdevelopment[n].log`	1 MB × 4	DevelopmentLogFile
Access log	Processing results of HTTP communication	In Windows `<ejb.server.log.directory>`^#2`\cj_access_niohttp[n].log` In UNIX `<ejb.server.log.directory>`^#2`/cj_access_niohttp[n].log`	4 MB × 16	NIOHTTPAccessLogFile
Access log	Processing results of WebSocket communication	In Windows `<ejb.server.log.directory>`^#2`\cj_access_websocket[n].log` In UNIX `<ejb.server.log.directory>`^#2`/cj_access_websocket[n].log`	4 MB × 16	WebSocketAccessLogFile

Legend:

--: Not applicable

Note:

Channel name is the name to identify the output destination of the log. Use it as a key value when changing log attributes (size, number of files).

#1

In the part of the log file name [n], the file number (number of files from 1 (maximum 16)) is added.

However, when using the sub directory shared mode of an EJB client application, the maximum number of files is 64.

Moreover, in the [nn] part, a serial number from 01 to 99 is added.

#2

<ejb.server.log.directory> indicates a directory specified in the ejb.server.log.directory parameter in the <configuration> tag of the logical J2EE server (j2ee-server) in the Easy Setup definition file. The default value is Cosminexus-installation-directory\CC\server\public\ejb\server-name\logs.

For details about the ejb.server.log.directory parameter in the Easy Setup definition file, see 4.11.3 Parameters used for setting up the option definitions for the J2EE server and 2.2.2 usrconf.cfg (Option definition file for J2EE servers) in the uCosminexus Application Server Definition Reference Guide.

#3

Check the file contents when the file is output. If the maximum size is exceeded while checking, rename the cjlogger.log file with the backup file name (cjlogger_save.log).

#4

Decision about acquiring the resource adapter log depends on the contents specified in server management commands. Moreover, you can use the simple setup definition file to change the size and number of files for a resource adapter log. For details about the settings for acquiring the resource adapter logs, see 3.3.11 Settings for Acquiring the Resource Adapter Logs.

#5

Stack trace for the exception that occurred in a servlet and JSP is also output.

#6

It is a log in which only the start process information is acquired. As it is output mainly while starting and terminating J2EE server, this log is almost not output online. When the file size reaches the upper limit, it is saved in cjstdout_save.log or cjstderr_save.log under working-directory\ejb\server-name\logs (in Windows) or under working-directory/ejb/server-name/logs (in UNIX). If cjstdout_save.log or cjstderr_save.log already exists, it is overwritten.

#7

The size and number of files cannot be changed.

#8

The output destination of the log file differs depending on the Windows event log settings.

#9

To output messages related to J2EE server start, stop, and abnormal termination, to syslog, it is necessary to set the priority for the facility daemon to info or debug in the syslog settings. For details about the syslog settings, see the manual provided with the OS.

Reference note: When the session failover function is used, the log for session failover is output as the log of the J2EE server using the session failover function.

(b) Server management command log

Table 4‒4: Output destination of the server management command log (Default)
Category	Contents	Log output destination and log file name^#1	Default size × number of files	Channel name
Message log	Operation log^{#2, #3}	In Windows `Cosminexus-installation-directory\CC\admin\logs\cjmessage[n].log` In UNIX `/opt/Cosminexus/CC/admin/logs/cjmessage[n].log`	1024KB × 3	MessageLogFile
Message log	Log operation log^#2	In Windows `Cosminexus-installation-directory\CC\admin\logs\cjlogger.log` In UNIX `/opt/Cosminexus/CC/admin/logs/ cjlogger.log`	1024KB × 2	--
Exception log	Exception information when an error occurs^{#2, #3}	In Windows `Cosminexus-installation-directory\CC\admin\logs\cjexception[n].log` In UNIX `/opt/Cosminexus/CC/admin/logs/cjexception[n].log`	1024KB × 6	ExceptionLogFile
Maintenance log	Maintenance information^#2	In Windows `Cosminexus-installation-directory\CC\admin\logs\CC\maintenance\cjmaintenance[n].log` In UNIX `/opt/Cosminexus/CC/admin/logs/CC/maintenance/cjmaintenance[n].log`	1024KB × 3	MaintenanceLogFile
	Console message^#2	In Windows `Cosminexus-installation-directory\CC\admin\logs\CC\maintenance\cjconsole[n].log` In UNIX `/opt/Cosminexus/CC/admin/logs/CC/maintenance/cjconsole[n].log`	32KB × 3	ConsoleLogFile
	Maintenance information of the server management command^#2	In Windows `Cosminexus-installation-directory\CC\admin\logs\CC\maintenance\cjserveradmin[n].log` In UNIX `/opt/Cosminexus/CC/admin/logs/CC/maintenance/cjserveradmin[n].log`	32KB × 3	ServerAdminLogFile

Legend:: --: Not applicable
Note:: Channel name is the name to identify the output destination of the log.
#1: In the [n] part of the log file name, add the file number (from 1 to the maximum number of files for each log).
#2: The command name is displayed in the output message (application identification name) of the Hitachi Trace Common Library format. For details on the log in the Trace Common Library format, see 5.2 Application Server Log.
#3: For the compatibility mode, the output destination of the operation log and the exception information when an error occurs will differ from the standard mode. For the compatibility mode, the output destination, the default size, and the number of files are as follows:

Table 4‒5: Output destination of server management commands log (Compatibility mode)
Contents	Log output destination and log file name^#	Default size × number of files
Operation log	In Windows `Cosminexus-installation-directory\CC\admin\logs\<command-name>message[n].log` In UNIX `/opt/Cosminexus/CC/admin/logs/command-name/message[n].log`	128KB × 2
Exception information when an error occurs	In Windows `Cosminexus-installation-directory\CC\admin\logs\<command-name>exception[n].log` In UNIX `/opt/Cosminexus/CC/admin/logs/command-name/exception[n].log`	256KB × 2

#: In the [n] part of the log file name, add the file number (from 1 to the maximum number of files for each log).

In the messages output to the message log of the server management commands, there are the cases when the message ID field is blank and message ID (such as KDJEnnnnn-Y) is included in the message text field. This is an additional information of the messages output before or after the messages are output at the server side.

(c) Resource adapter version-up command (cjrarupdate) log

Table 4‒6: Output destination of the resource adapter version-up command (cjrarupdate) log
Category	Contents	Log output destination and log file name^#	Default size × number of files
Message log	Operation log	In Windows `Cosminexus-installation-directory\CC\logs\cjrarupdatemessage[n].log`^#1 In UNIX `/opt/Cosminexus/CC/logs/cjrarupdatemessage[n].log`^#1	1MB × 2
Exception log	Exception information when an error occurs	In Windows `Cosminexus-installation-directory\CC\logs\cjrarupdateexception[n].log`^#1 In UNIX `/opt/Cosminexus/CC/logs/cjrarupdateexception[n].log`^#1	1MB × 2
Maintenance log	Maintenance information	In Windows `Cosminexus-installation-directory\CC\logs\cjrarupdatemaintenance[n].log`^#2 In UNIX `/opt/Cosminexus/CC/logs/cjrarupdatemaintenance[n].log`^#2	16 MB × 4

#1: In the[n]part of the log file name, add the file number (1 or 2).
#2: In the[n]part of the log file name, add the file number (from 1 to 4).

(d) Migration command (cjenvupdate) log

Table 4‒7: Output destination of the migration command (cjenvupdate) log
Category	Contents	Log output destination and log file name^#	Default size × number of files
Message log	Operation log of the cjenvupdate command	In Windows `Cosminexus-installation-directory\CC\logs\cjenvupdatemessage[n].log` In UNIX `/opt/Cosminexus/CC/logs/cjenvupdatemessage[n].log`	4MB × 4
Exception log	Exception information of the cjenvupdate command	In Windows `Cosminexus-installation-directory\CC\logs\cjenvupdateexception[n].log` In UNIX `/opt/Cosminexus/CC/logs/cjenvupdateexception[n].log`	4MB × 4
Maintenance log	Maintenance information of the cjenvupdate command	In Windows `Cosminexus-installation-directory\CC\logs\cjenvupdatemaintenance[n].log` In UNIX `/opt/Cosminexus/CC/logs/cjenvupdatemaintenance[n].log`	4MB × 4

#: In [n], the file number (from 1 to 4) is attached.

(e) Resource depletion monitoring log

Table 4‒8: Output destination of resource depletion monitoring log
Monitored Resources	Log acquisition location and log file name^#1	Default size × number of files	Channel name
Memory	In Windows `<ejb.server.log.directory>`^#2`\watch\cjmemorywatch[n].log` In UNIX `ejb.server.log.directory`^#2`/watch/cjmemorywatch[n].log`	1MB × 2	MemoryWatchLogFile
File descriptors	In UNIX^#3 `ejb.server.log.directory`^#2`/watch/cjfiledescriptorwatch[n].log`	1MB × 2	FileDescriptorWatchLogFile
Threads	In Windows `<ejb.server.log.directory>`^#2`\watch\cjthreadwatch[n].log` In UNIX `ejb.server.log.directory`^#2`/watch/cjthreadwatch[n].log`	1MB × 2	ThreadWatchLogFile
Thread dump	In Windows `<ejb.server.log.directory>#2\watch\cjthreaddumpwatch[n].log` In UNIX `ejb.server.log.directory`^#2`/watch/cjthreaddumpwatch[n].log`	1MB × 2	ThreaddumpWatchLogFile
HTTP requests pending queue	In Windows `<ejb.server.log.directory>`^#2`\watch\cjrequestqueuewatch[n].log` In UNIX `ejb.server.log.directory`^#2`/watch/cjrequestqueuewatch[n].log`	1MB × 2	RequestQueueWatchLogFile
HTTP session numbers	In Windows `<ejb.server.log.directory>`^#2`\watch\cjhttpsessionwatch[n].log` In UNIX `ejb.server.log.directory`^#2`/watch/cjhttpsessionwatch[n].log`	1MB × 2	HttpSessionWatchLogFile
Connection pool	In Windows `<ejb.server.log.directory>`^#2`\watch\cjconnectionpoolwatch[n].log` In UNIX `ejb.server.log.directory`^#2`/watch/cjconnectionpoolwatch[n].log`	1MB × 2	ConnectionPoolWatchLogFile

Note:

Channel name is the name to identify the output destination of the log. Use it as a key value when changing log attributes (size, number of files).

#1

In [n], the file number (number of files from 1 (maximum 16)) is attached.

#2

<ejb.server.log.directory> indicates the directory specified in the ejb.server.log.directory parameter in the <configuration> tag of the logical J2EE server (j2ee-server) of the Easy Setup definition file. The default value is Cosminexus-installation-directory\CC\server\public\ejb\server-name\logs.

#3

The file descriptor cannot be monitored in Windows and AIX.

For details about the information output to the resource depletion monitoring log file and for the output format of the log file, see 4.3 Resource depletion monitoring functionality and output of resource depletion monitoring information in the uCosminexus Application Server Operation, Monitoring, and Linkage Guide.

(f) User definition file to set output destination of the log

When the output destination of the J2EE server and server management command log output destination is changed, reference the user definition file in which the log output destination is set, described in the following table and confirm the output destination. Note that if the output destination of a log is changed, that log is not collected when the snapshot log is collected in a batch. Change the collection destination of the snapshot log as and when required.

Table 4‒9: User definition file in which the output destination of log is set
Category	User definition file
J2EE server	The `ejb.server.log.directory` parameter is specified in the <`configuration`> tag of the logical J2EE server (j2ee-server) of the Easy Setup definition file. The default is `Cosminexus-installation-directory\CC\server\public\ejb\server-name\logs` (in Windows), or `/opt/Cosminexus/CC/server/public/ejb/server-name/logs` (in UNIX).
Server management commands	`ejbserver.log.directory` key of the server management command usrconf.bat (in Windows) or usrconf (in UNIX) The default key is `Cosminexus-installation-directory`\CC\admin\logs (in Windows) or /opt/Cosminexus/CC/admin/logs (in UNIX). You cannot change the output destination of the server management command log when operating from the Management Server remote management functionality.

For details about the settings of the data acquisition for troubleshooting, such as how to change the output destination of the logs, see the chapter 3. Preparing for Troubleshooting.

To Page Top

(2) Acquiring the log of Administration agent, Management agent, and Management Server

This points describes the output destination of the Administration Agent, Management Agent, and the Management Server log.

In the Administration agent, Management agent, and Management Server logs, besides acquiring separately, you can also acquire these logs by compiling as a Integrated log. Following are the types of integrated logs:

Integrated message log

The message logs of the Manager are integrated and output.
Integrated trace log

The trace logs of the Manager are integrated and output.
Command maintenance log^#

The management commands, the commands used with Smart Composer functionality, and the trace log of the snapshotlog command are integrated and output.

# For details about the commands used with the Smart Composer functionality, see 8. Commands Used with the Smart Composer Functionality in the uCosminexus Application Server Command Reference Guide.

The following table describes the output destination of integrated logs.

Table 4‒10: Output destination of the integrated log (In Windows)
File name	Contents	Output destination directory	Default size × number of files
mngmessage[`n`].^#1log	Integrated message log	`Log-output-directory-of-Manager`\message^#2	256KB × 4
mngtrace[`n`]^#1.log	Integrated trace log	`Log-output-directory-of-Manager`\trace^#2	1MB × 4
mngcmd[`n`]^#1.log	Command maintenance log	`Log-output-directory-of-Manager`\maintenance^#2	16MB × 4

#1: In the part of the log file name [n], the file number (number of files from 1 (maximum 64)) is added.
#2: Log-output-directory-of-Manager indicates the directory specified in manager.cfg (Manager log settings file). The default value is Cosminexus-installation-directory\manager\log. For details about manager.cfg, see 8.2.9 manager.cfg (Manager settings file) in the uCosminexus Application Server Definition Reference Guide.

Table 4‒11: Output destination of the integrated log (in UNIX)
File name	Contents	Output destination directory	Default size × number of files
mngmessage[`n`]^#1.log	Integrated message log	`Log-output-directory-of-Manager`/message^#2	256KB × 4
mngtrace[`n`]^#1.log	Integrated trace log	`Log-output-directory-of-Manager`/trace^#2	1MB × 4
mngcmd[`n`]^#1.log	Command maintenance log	`Log-output-directory-of-Manage`r/maintenance^#2	16MB × 4

#1: In the part of the log file name [n], the file number (number of files from 1 (maximum 64)) is added.
#2: Log-output-directory-of-Manager indicates the directory specified in manager.cfg (Manager log settings file). The default value is /opt/Cosminexus/manager/log. For details about manager.cfg, see 8.2.9 manager.cfg (Manager settings file) in the uCosminexus Application Server Definition Reference Guide.

Note that the log output in the integrated log is output separately by default.

Additionally, the logs output in the integrated log might not output separately. For details about the settings to output integrated logs, see 3.3.10 Settings for Acquiring the Cosminexus Manager Log.

The following table describes the Administration agent, Management agent, and Management Server log output destination as well as the possibility of output to integrated message log and integrated trace log when acquiring separately.

Table 4‒12: Output destination when acquiring the Administration agent, Management agent, and Management Server log separately (in Windows)
Category	File name	Contents	Output destination directory	Default size × number of files	Integrated message log/ integrated trace log
Administration agent	`adminagent.err.[1-16].log`^#1	Standard error output of Administration agent	`Log-output-directory-of-the-Manager`	64KB × 4	N
	`adminagent.out.[1-16].log`^#1	Standard output of Administration agent		64KB × 4	N
	`adminagent.err`	Standard command line error output of Administration agent		--	N
	`adminagent[1-16].log`	Administration agent log		64KB × 4	Y
	`adminagentctl.exe.[1-2].log`	Administration agent start, stop command log		64KB × 2	N
	`adminagent[n]`^#2.`log`	Administration agent maintenance log	`Log-output-directory-of-Manager\maintenance`	16MB × 4	N
	`mngrmi[n]`^#2`.log`	Maintenance log in RMI processing executed by Administration Agent	`Log-output-directory-of-Manager\maintenance`	16MB × 8	N
	`processConsole[n]`^#2`.log`	Console log	`Log-output-directory-of-the-Manager`	64KB × 4	N
	`adminagentsv.exe.[1-16]log`^#1	Administration agent service log		64KB × 2	N
	`adminagentsv.exe.out`^#1	Administration agent service standard output		--	N
	`adminagentsv.exe.err`^#1	Administration agent service standard error output		--	N
	`adminagent.javalog[01-04].log`	JavaVM log file of Administration Agent		256KB × 4	N
Management agent	`mngagent-domain-name`-`agent-name`.[`n`]^#2`.log`^#3	Management agent log and trace System JP1 event and user JP1 event log^#4 for J2EE server Management event published log^#5		64KB × 4	N
Management Server	`mngsvr.exe.[1-2` `].log`	Management Server service log		64KB × 2	N
	`mngsvr.exe.err`^#1	Management Server service standard error output		--	N
	`mngsvr.exe.out`^#1	Management Server service standard output		--	N
	`mngsvrctl.exe.[1-2].log`	Management Server service start, stop command log		64KB × 2	N
	`mngsvr[n]`^#2`.log`	Management Server log Management server^#6 system JP1 event log^#4		64KB × 4	Y
	`mngsvr[n]`^#2`.log`	Management Server maintenance log	`Log-output-directory-of-Manager\maintenance`	16MB × 2	N
	`cjmessage[n].log`	Operation log	`Manager-log-output-directory`	1 MB ×2	N
	`cjexception[n].log`	Exception information for error	`Manager-log-output-directory\maintenance`	1 MB ×2	N
	`cjmaintenance[n].log`	Maintenance information		16 MB ×4	N
	`cjconsole[n].log`	Console message		1 MB ×2	N
	`cjejbcontainer[n].log`	EJB container maintenance information		1 MB ×2	N
	`web_servlet[n].log`	Web servlet log		4 MB ×4	N
	`user_out[n].log`	User output log		1 MB ×2	N
	`user_err[n].log`	User error log		1 MB ×2	N
	`cjlogger.log`	Log operation log		1 MB ×2	N
	`javalog[nn].log`	JavaVM maintenance information and GC log		4 MB ×4	N
	`ehjavalog[nn].log`	Event log of the Explicit Memory Management functionality		4 MB ×4	N
	`cjwebcontainer[n].log`	Web container maintenance information		1 MB ×2	N
	`cjstdout.log`	Standard output information for the start process	`Manager-log-output-directory\maintenance/CC/maintenance`	--	N
	`cjstderr.log`	Standard error information for the start process		--	N
	`cj_shutdown[n].log`	End process information		4 KB ×4	N
	`cjrmi[n].log`	RMI communication log of the J2EE server for the RMI processing executed by the Management Server	`Manager-log-output-directory\maintenance\CC\rmi`	1 MB ×4	N
	`cjhttp_thr.time-information.inprocess_http.mm`	Thread trace information	`Manager-log-output-directory\maintenance\http\maintenance\thr`	About 3.2 MB ×16	N
	`cjhttp_comm.time-information.inprocess_http.mm`	Communication trace information	`Manager-log-output-directory\maintenance\http\maintenance\comm`	About 16.6 MB ×16	N
	`cjmemorywatch[n].log`	Resource depletion monitoring log (Memory)	`Manager-log-output-directory\maintenance\watch`	1 MB ×2	N
	`cjthreadwatch[n].log`	Resource depletion monitoring log (Thread)		1 MB ×2	N
	`cjthreaddumpwatch[n].log`	Resource depletion monitoring log (Thread dump)		1 MB ×2	N
	`cjrequestqueuewatch[n].log`	Resource depletion monitoring log (HTTP request pending queue)		1 MB ×2	N
	`cjhttpsessionwatch[n].log`	Resource depletion monitoring log (Number of HTTP sessions)		1 MB ×2	N

Legend:

Y: Output to an integrated log

N: No output to an integrated log

[1-n]: Shows that a serial number in the range from 1 to n is used for the number of log files.

--: Not applicable

Note:

<Manager-log-output-directory> shows the directory specified in manager.cfg (Manager log setup file). The default is Cosminexus-installation-directory\manager\log (in Windows) or /opt/Cosminexus/manager/log (in UNIX). For details on manager.cfg, see 8.2.9 manager.cfg (Manager settings file) in the uCosminexus Application Server Definition Reference Guide.

#1

The log is output in a format different than Hitachi Trace Common Library format. For details on the log in the Trace Common Library format, see 5.2 Application Server Log.

#2

In the part of file name [n], the serial number from 1 to total number of specified log files is added.

#3

You can change the output destination of Management agent log trace. If the output destination of Management agent log and trace is changed, see the mngagent.log.filename key value of the mngagent.properties file (Management agent property file).

#4

This log is output if a system built with the application server by integrating with JP1 is to be operated.

#5

This log is output when a Management event is used.

#6

This log is for the Management Server of the Application Server.

Table 4‒13: Output destination when acquiring the Administration agent, Management agent, and Management Server log separately (in UNIX)
Category	File name	Contents	Output destination directory	Default size × number of files	Integrated message log/ integrated trace log
Administration agent	`adminagent.err.[1-16].log`^#1	Standard error output of Administration agent	`Log-output-directory-of-the-Manager`	64KB × 4	N
	`adminagent.out.[1-16].log`^#1	Standard output of Administration agent		64KB × 4	N
	`adminagent.err`	Standard command line error output of Administration agent		--	N
	`adminagent[1-16].log`	Administration agent log		64KB × 4	Y
	`adminagentctl.[1-16].log`	Administration agent start, stop command log		64KB × 2	N
	`adminagent[n]`^#2`.log`	Administration agent maintenance log	`Log-output-directory-of-Manager/maintenance`	16MB × 4	N
	`mngrmi[n]`^#2`.log`	Maintenance log in RMI processing executed by Administration Agent	`Log-output-directory-of-Manager/maintenance`	16MB × 8	N
	`processConsole[n]`^#2`.log`	Console log	`Log-output-directory-of-the-Manager`	64KB × 4	N
	`adminagent.javalog[01-04].log`	JavaVM log file of Administration Agent		256KB × 4	N
Management agent	`mngagent-domain-name`-`agent-name`. `[n]`^#2`.log`^#3	Management agent log and trace System JP1 event and user JP1 event log^#4 for J2EE server Management event published log^#5		64KB × 4	N
Management Server	`mngsvrctlstart.[1-2].log`	Management Server start command		64KB × 2	N
	`mngsvrctlstop.[1-2].log`	Management Server stop command		64KB × 2	N
	`mngsvrctlsetup.[1-2].log`	Management Server set up command		64KB × 2	N
	`mngsvr[n].log`	Management Server log Management server^#6 system JP1 event log^#4		64KB × 4	Y
	`mngenvsetup.[1-2].log`	Execution log of the `mngenvsetup` command	`Log-output-directory-of-Manager/maintenance`	512KB × 2	N
	`mngsvr[n]`^#2`.log`	Management Server maintenance log	`Log-output-directory-of-Manager/maintenance`	16MB × 2	N
	`cjmessage[n].log`	Operation log	`Manager-log-output-directory`	1 MB ×2	N
	`cjexception[n].log`	Exception information for error	`Manager-log-output-directory/maintenance`	1 MB ×2	N
	`cjmaintenance[n].log`	Maintenance information		16 MB ×4	N
	`cjconsole[n].log`	Console message		1 MB ×2	N
	`cjejbcontainer[n].log`	EJB container maintenance information		1 MB ×2	N
	`web_servlet[n].log`	Web servlet log		4 MB ×4	N
	`user_out[n].log`	User output log		1 MB ×2	N
	`user_err[n].log`	User error log		1 MB ×2	N
	`cjlogger.log`	Log operation log		1 MB ×2	N
	`javalog[nn].log`	JavaVM maintenance information and GC log		4 MB ×4	N
	`ehjavalog[nn].log`	Event log of the Explicit Memory Management functionality		4 MB ×4	N
	`cjwebcontainer[n].log`	Web container maintenance information		1 MB ×2	N
	`cjstdout.log`	Standard output information for the start process	`Manager-log-output-directory/maintenance/CC/maintenance`	--	N
	`cjstderr.log`	Standard error information for the start process		--	N
	`cj_shutdown[n].log`	End process information		4 KB ×4	N
	`cjrmi[n].log`	RMI communication log of the J2EE server for the RMI processing executed by the Management Server	`Manager-log-output-directory/maintenance/CC/rmi`	1 MB ×4	N
	`cjhttp_thr.time-information.inprocess_http.mm`	Thread trace information	`Manager-log-output-directory/maintenance/http/maintenance/thr`	About 3.2 MB ×16	N
	`cjhttp_comm.time-information.inprocess_http.mm`	Communication trace information	`Manager-log-output-directory/maintenance/http/maintenance/comm`	About 16.6 MB ×16	N
	`cjmemorywatch[n].log`	Resource depletion monitoring log (Memory)	`Manager-log-output-directory/maintenance/watch`	1 MB ×2	N
	`cjfiledescriptorwatch[n].log`	Resource depletion monitoring log (File descriptor)		1 MB ×2	N
	`cjthreadwatch[n].log`	Resource depletion monitoring log (Thread)		1 MB ×2	N
	`cjthreaddumpwatch[n].log`	Resource depletion monitoring log (Thread dump)		1 MB ×2	N
	`cjrequestqueuewatch[n].log`	Resource depletion monitoring log (HTTP request pending queue)		1 MB ×2	N
	`cjhttpsessionwatch[n].log`	Resource depletion monitoring log (Number of HTTP sessions)		1 MB ×2	N

Legend:

Y: Output to an integrated log

N: No output to an integrated log

[1-n]: Shows that a serial number in the range from 1 to n is used for the number of log files.

--: Not applicable

#1

The log is output in a format different than Hitachi Trace Common Library format. For details on the log in the Trace Common Library format, see 5.2 Application Server Log.

#2

In the part of file name [n], the serial number from 1 to total number of specified log files is added.

#3

You can change the output destination of Management agent log trace. If the output destination of Management agent log and trace is changed, see the mngagent.log.filename key value of the mngagent.properties file (Management agent property file).

#4

This log is output if a system built with the application server by integrating with JP1 is to be operated.

#5

This log is output when a Management event is used.

#6

This log is for the Management Server of the Application Server.

Important note

In the console log, the standard output and the standard error output of the server process started by the Administration agent is output. The precautions related to console log are as follows.

In Windows, the console log is not output for the following processes:

Logical performance tracer

Logical Web server

Logical CTM domain manager

Logical CTM

Logical user server started indirectly

For the startup types of the logical user server, see 8.2.19 Logical user server definition file in the uCosminexus Application Server Definition Reference Guide.
When multiple lines of information to be output to the console log are output at the same time, console log displays the information by consolidating into a single line.
When the number of characters of the information to be output in console information exceeds 2039 characters, the information after the 2039th character is split and output to the following line.

To Page Top

(3) Acquiring the logs of the internal setup tool of the virtual server manager and Server Communication Agent

This subsection describes the output destination for logs of the internal setup tool of the virtual server manager and Server Communication Agent.

The following table describes the output destination for logs of the internal setup tool of the virtual server manager and Server Communication Agent, and the presence or absence of output to the integrated message log or integrated trace log.

Table 4‒14: Output destination for logs of the internal setup tool of the virtual server manager and Server Communication Agent
Category	File name	Contents	Output destination directory	Default size × number of files	Integrated message log/ Integrated trace log
Internal setup tool of the virtual server manager	`rasetup[n]`^#2`.log`	Logs for the internal setup tool of the virtual server manager	In Windows `Cosminexus-installation-directory\manager\setup\log` In UNIX `/opt/Cosminexus/manager/setup/log`	262144 bytes × 4	N
Internal setup tool of the virtual server manager	`rasetup[n`^#2`.log`	Maintenance logs for the internal setup tool of the virtual server manager	In Windows `Cosminexus-installation-directory\manager\setup\log\maintenance` In UNIX `/opt/Cosminexus/manager/setup/log/maintenance`	16777216 bytes × 4	N
Server Communication Agent	`sinaviagent[n]`^#2`.log`	Server Communication Agent logs	`Log-output-directory-of-Server-Communication-Agent`^#1	524288 bytes × 4	N
	`sinaviagentsv[n]`^#2`.log`	Service logs of the Server Communication Agent		65536 bytes × 4	N
	`snactl[n]`^#2`.log`	Start and stop command logs of the Server Communication Agent		65536 bytes × 4	N
	`sinaviagent.err`	Standard error output of the Server Communication Agent		65536 bytes × 1	N
	`sinaviagent.out`	Standard output of the Server Communication Agent		65536 bytes × 1	N
	`processConsole[n]`^#2`.log`	Console logs		65536 bytes × 4	N
	`sinaviagent[n]`^#2`.log`	Maintenance logs of the Server Communication Agent	In Windows `Cosminexus-installation-directory\sinagent\log\maintenance` In UNIX `/opt/Cosminexus/sinagent/log/maintenance`	1048576 bytes × 4	N
	`sinaviagentsv[n]`^#2`.log`	Maintenance logs for the Server Communication Agent services		65536 bytes × 4	N
	`snactl[n]`^#2`.log`	Maintenance logs for the start and stop commands of the Server Communication Agent		65536 bytes × 4	N
	`sinaviagent.javalog[n].`^#2`log`	JavaVM log file of the Server Communication Agent		256 KB × 4	N

Legend:

N: No output to an integrated log.

[n]: Shows that a serial number in the range from 1 to n is used for the number of log files.

#1

Log-output-directory-of-Server-Communication-Agent indicates the directory specified in sinaviagent.cfg (option definition file for Server Communication Agent). The default values are Cosminexus-installation-directory\sinagent\log (in Windows), or /opt/Cosminexus/sinagent/log (in UNIX).

#2

In the [n] part of the file name, a serial number is added sequentially from 1 up to the specified number of log files.

To Page Top

(4) Acquiring the integrated user management log

The integrated user management trace file is output according to the settings in the com.cosminexus.admin.auth.trace.prefix option of the ua.conf file (integrated user management configuration file). For details about the ua.conf file, see 14.2.2 ua.conf (integrated user management configuration file) in the uCosminexus Application Server Security Management Guide.

To Page Top

(5) Collecting Cosminexus JMS Provider logs

This subsection describes the collection of Cosminexus JMS Provider logs. With Cosminexus JMS Provider, you can collect CJMSP Broker logs, management command (cjmsicmd) logs, and CJMSP resource adapter logs. The following table describes the default log output destinations.

Table 4‒15: Output destination of Cosminexus JMS Provider logs (Default)
Log type	Category	Default output destination	Default size ×Number of files
CJMSP Broker log	Message log	In Windows `<CJMSP_HOME>`^#1 `\var\instances\instanceName\log\cjmsbroker_msg[n].log` In UNIX `<CJMSP_HOME>`^# ¹`/var/instances/instanceName/log/cjmsbroker_msg[n].log`	1 MB ×2
CJMSP Broker log	Error log	In Windows `<CJMSP_HOME>`^#1 `\var\instances\instanceName\log\cjmsbroker_err[n].log` In UNIX `<CJMSP_HOME>`^#1 `/var/instances/instanceName/log/cjmsbroker_err[n].log`	1 MB ×2
Management command (`cjmsicmd`) log^#2	Message log	In Windows `<CJMSP_HOME>`^#1 `\var\admin\log\cjmsadmin_msg[n].log` In UNIX `<CJMSP_HOME>`^#1 `/var/admin/log/cjmsadmin_msg[n].log`	1 MB ×2
Management command (`cjmsicmd`) log^#2	Error log	In Windows `<CJMSP_HOME>`^#1 `\var\admin\log\cjmsadmin_err[n].log` In UNIX `<CJMSP_HOME>`^#1 `/var/admin/log/cjmsadmin_err[n].log`	1 MB ×2
CJMSP resource adapter log	Message log	In Windows `J2EE-server-log-output-directory-(ejb.server.log.directory)`^#3 `\cjms\Cosminexus_JMS_Provider_RA\cjmsra_msg[n].log` In UNIX `J2EE-server-log-output-directory-(ejb.server.log.directory)`^#3 `/cjms/Cosminexus_JMS_Provider_RA/cjmsra_msg[n].log`	1 MB ×2
CJMSP resource adapter log	Error log	In Windows `J2EE-server-log-output-directory-(ejb.server.log.directory)`^#3 `\cjms\Cosminexus_JMS_Provider_RA\cjmsra_err[n].log` In UNIX `J2EE-server-log-output-directory-(ejb.server.log.directory)`^#3 `/cjms/Cosminexus_JMS_Provider_RA/cjmsra_err[n].log`	1 MB ×2

Note

In [n], add the file number (number of files from 1 (maximum 16)).

#1

<CJMSP_HOME> indicates the following directory:

In Windows

Cosminexus-installation-directory\CC\cjmsp

In UNIX

/opt/Cosminexus/CC/cjmsp

#2

If the log output has reached the specified maximum file size, the log output destination switches to the next file. If the file count reaches the specified number of files, the output destination switches to the first file by the wraparound method and the original information is overwritten. Note that the file is initialized only during the creation and not during the wraparound. If the file size is extended, the file is initialized only for the extended part. Initialization means writing null characters (0x20) in the area from EOF (End Of File) to the specified file size. The existing data is not affected.

#3

J2EE-server-log-output-directory (ejb.server.log.directory) is the directory specified in the J2EE server option definition. By default, the following directory is specified:

In Windows

Directory-specified-in-ejb.public.directory\ejb\J2EE-server-name\logs

In UNIX

Directory-specified-in-ejb.public.directory/ejb/J2EE-server-name/logs

To Page Top

(6) Required information to be acquired other than a log

This section describes the required information to be acquired other than a log.

When using the in-process transaction service

When using the in-process transaction service, it is necessary to acquire the status file of the in-process transaction service. Note that you also acquire the spare status file when the status file is duplicated.

The status file is stored in the path specified in the ejbserver.distributedtx.ots.status.directory1 parameter and the ejbserver.distributedtx.ots.status.directory2 parameter (during duplication) in the <configuration> tag of the logical J2EE server (j2ee-server) in the Easy setup definition file.

To Page Top