Acquiring the Cosminexus Component Container Logs

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

Also, in Cosminexus Component Container, the migration command logs are output besides these logs. When the in-process HTTP server or resource depletion monitoring function is used, the in-process HTTP server log or the resource depletion monitoring log is output respectively.

In the J2EE server and redirector log, there are four types of logs, message log, user log, exception 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.
In in-process HTTP server log, there are three types of logs; access log, thread trace log, and communication trace log.
In the Cosminexus JPA provider log, there are four types of logs; message log, exception log, operation log, and maintenance log. The message log and the exception log are same as for the J2EE servers.
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.

Note that message log is also output in the following cases for Cosminexus JPA Provider:

When failed in class loading and in the query analysis
When ignored the annotation specified by the user with the orm.xml tag.
When an invalid value is specified for the property of the Cosminexus JPA specific functionality specified in persistence.xml
When failed to participate in JTA transaction
When failed to update the database

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 in the case of operating systems other than Solaris.

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.; For the Cosminexus JPA Provider, if you specify cosminexus.jpa.exception.logging.sql in the property of the logical J2EE server of the Easy Setup definition file, the exception message can also include SQL statement (includes an SQL issued internally because of a delay in processing). For details about the properties, see 2.4 usrconf.properties (User property file for J2EE server) in the uCosminexus Application Server Definition Reference Guide.

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.

In-process HTTP server log: The maintenance information and the processing result of a request are output for using the in-process HTTP server. Maintenance personnel use the maintenance information to analyze the errors that occur in Cosminexus Component Container. The processing result of the request is used for analyzing the performance information and the session tracking information of the in-process HTTP server as an access log.

Cosminexus JPA Provider log

In the Cosminexus JPA Provider, the operation information (includes an SQL issued internally because of a delay in the processing) is output. In operation logs, there are two categories; SQL and TRANSACTION. You can specify the output level of the log as per each category. There is the information indicating Off, Information, and Detail for the output level of the operation log. An operation log is output when Information or Detail is specified. The following table describes the output contents of the operation log as per each category.

Table 4-3 Output contents of the operation log as per each category

Category	Output contents in information level	Output contents in detail level
SQL^#1	All issued SQL are output. Issued SQL is output regardless of the user or the Cosminexus JPA Provider. Return value of PreparedStatement#executeUpdate() is output^{#2, #3}	Output content in Information level is output. Setup value for the ? parameter (place holder) is output.
TRANSACTION	Message is output showing that the Synchronization is registered to the transaction manager when using JTA transaction. Message is output when the EntityManager participates in the JTA transaction. Message is output showing that afterCompletion() of Synchronization is called from the transaction manager when using JTA transaction. Message is output when JTA transaction is concluded.	Output content of the Information level. Event message is output showing that begin(), commit(), and rollback() of EntityTrasanction are executed. Message is not output when an exception occurs.

#1: Consider the setup of the log output level as an SQL and a parameter issued to the database are output to log.

#2: When you execute the UPDATE statement, it becomes the updated number of lines. For details, see java.sql.PreparedStatement of Javadoc; When you execute the SELECT statement, there is no output if PreparedStatement#executeUpdate() is not used. However, when Query interface is generated with the SELECT statement of native query, the SELECT statement is also output when you execute Query#executeUpdate().

#3: There is no output if exception occurs when you execute PreparedStatement#executeUpdate().

When the status of the transaction described in the above-mentioned table or the information on persistent unit name cannot be acquired, the operation log is output in the lower case as unknown. For details about the operation log output in the Cosminexus JPA Provider, see Appendix C.1 Cosminexus JPA Provider operation log.

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 and redirector log

Table 4-4 Output destination of the J2EE server and the redirector 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	--
	Redirector message log	Directory^#4 In Windows Cosminexus-installation-directory\CC\web\redirector\logs In UNIX /opt/Cosminexus/CC/web/redirector/logs	4MB 5	--
Message log	Redirector message log	File name^#4 In Windows isapi_redirect[n].log (Microsoft IIS) hws_redirect[n].log (Cosminexus HTTP Server) In UNIX hws_redirect[n].log (Cosminexus HTTP Server)	4MB 5	--
Message log	Operation log of resource adapter that is deployed and used as a J2EE resource adapter^#5	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	--
Message log	Operation log of resource adapter used in a J2EE application^#5	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	2 MB 4	--
Message log	Operation log of resource adapter used in a J2EE application^#5	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	1MB 2	--
Message log	Operation log of resource adapter used in a J2EE application^#5	In UNIX (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	1MB 2	--
User log	Web servlet log^#6	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
User log	JavaVM maintenance information and garbage collection log	In Windows ejb.server.log.directory^#2\javalog[nn].log In UNIX ejb.server.log.directory^#2/javalog[nn].log	4MB 4	--
User log	Event log of Explicit Heap 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
Maintenance log	Start process standard output information^#7	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^#7	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^#8	--
	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
Maintenance log	Redirector maintenance trace log	Directory^#4 In Windows Cosminexus-installation-directory\CC\web\redirector\logs In UNIX /opt/Cosminexus/CC/web/redirector/logs/	16MB 4	--
	Redirector maintenance trace log	File name^#4 In Windows iis_rd_trace[n].log (Microsoft IIS) hws_rd_trace[n].log (Cosminexus HTTP Server) In UNIX hws_rd_trace[n].log (Cosminexus HTTP Server)	16MB 4	--
	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^#9	--	--
syslog	Log showing J2EE server start, stop or abnormal termination	Depends on UNIX syslog settings.^#10	--	--
Debug log	Log for checking development	In Windows <ejb.server.log.directory>^#²\cjdevelopment[n].log In UNIX <ejb.server.log.directory>^#²/cjdevelopment[n].log	1 MB 4	DevelopmentLogFile

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 Microsoft IIS in the redirector, or 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.14.2 Parameters for setting option definition for J2EE server and 2.3 usrconf.cfg (option definition file for J2EE server) 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: The directory and file names can be set in isapi_redirect.conf (redirector action definition file for Microsoft IIS) or mod_jk.conf (redirector action definition file for Cosminexus HTTP Server). For details about the settings for acquiring the redirector logs, see 3.3.10 Settings for Acquiring the Redirector Log. For details about each file, see the uCosminexus Application Server Definition Reference Guide.; Among the messages output to the redirector message log, messages from KDJE21000-Z to KDJE21999-Z (Z shows the variable, E (error message), W (warning message), I (notification message)) are the messages for maintenance.

#5: 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.13 Settings for Acquiring the Resource Adapter Logs.

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

#7: 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.

#8: The size and number of files cannot be changed.

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

#10: 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.

Note

When using Cosminexus HTTP Server (UNIX) as a Web server, a specified number of redirector log files are created with a file size specified in mod_jk.conf, when the Web server is started. At this time, trace files are initialized as space (0x20). When working with the default file size and number of files, it is necessary to have 84 MB of disk space in the directory specified in the log output destination.
When using Microsoft IIS as a Web server, the number of redirector log files and the files with the file size specified in isapi_redirect.conf are all created when the Web server is accessed for the first time. At this time, trace files are initialized as space (0x20). When working with the default file size and number of files, it is necessary to have 84 MB of disk space in the directory specified in the log output destination.
In UNIX, execute the following command before acquiring the redirector trace log for maintenance.
/opt/hitachi/HNTRLib2/bin/hntr2sync JkTraceLogFileDir-specification-value/JkTraceLogFilePrefix-specification-value
Note that JkTraceLogFileDir and JkTraceLogFilePrefix are the keys specified in mod_jk.conf (Cosminexus HTTP Server redirector action definition file).

Reference note

When using the session failover function, the log for session failover is output to the following output destination:

Session failover function log
This log is output as a J2EE server log that uses the session failover function.
SFO server log
When the memory session failover functionality is used, the log of a J2EE server operating as the SFO server is output in the same directory as that of the J2EE server. Moreover, the log of applications running on the SFO server is also output to the J2EE server log where the SFO server applications are running.

(b) Server management command log

Table 4-5 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
Maintenance log	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 log	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-6 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-7 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) In-process HTTP server log

Table 4-8 Output destination of an in-process HTTP server log (Default)

Category	Contents	Log output destination and log file name	Default size number of files
Access log	Processing result of in-process HTTP server	In Windows <ejb.server.log.directory>^#1\http\cjhttp_access.inprocess_http[n].log^#2 In UNIX <ejb.server.log.directory>^#1/http/cjhttp_access.inprocess_http[n].log^#2	4MB 16
Thread trace	Information on thread trace	In Windows <ejb.server.log.directory>^#1\http\maintenance\thr\cjhttp_thr.time-information.inprocess_http.mm^#3 In UNIX <ejb.server.log.directory>^#1/http/maintenance/thr/cjhttp_thr.time-information.inprocess_http.mm^#3	about 3.2MB^#4 16
Communication trace	Information on communication trace	In Windows <ejb.server.log.directory>^#1\http\maintenance\comm\cjhttp_comm.time-information.inprocess_http.mm^#3 In UNIX <ejb.server.log.directory>^#1/http/maintenance/comm/cjhttp_comm.time-information.inprocess_http.mm^#3	About 16.6MB^#4 16

#1: <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) of 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 of the Easy Setup definition file, see 4.14.2 Parameters for setting option definition for J2EE server and 2.3 usrconf.cfg (option definition file for J2EE server) in the uCosminexus Application Server Definition Reference Guide.

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

#3: In <time information>, the date and time when the file was output is displayed in YYYYMMDDHHmmSSnnn format. For example, if the date and time when the file was output is 2005-01-20 at10:50:30.158, the file name will become as cjhttp_thr.20050120105030158.inprocess_http.mm or cjhttp_comm.20050120105030158.inprocess_http.mm.

#4: At every start-up, create a new trace file. If the number of files exceeds the maximum value (default value is 16), the file with the oldest date and time is reused.; File size is decided as follows:; File size of the thread trace = (((A+B) 32786)+ 32914) byte; File size of the communication trace = (((A+B) 172050)+128) byte; A= Value of webserver.connector.inprocess_http.max_connections; B = If the value of webserver.connector.inprocess_http.send_timeout is 0, then 0 and if it is not 0, then 1

Note

Execute the following commands before acquiring the thread trace and communication trace for in-process HTTP server:

In Windows: Cosminexus-installation-directory\CC\admin\bin\cjtracesync [-thr|-comm] server-name

In UNIX: /opt/Cosminexus/CC/admin/bin/cjtracesync [-thr|-comm] server-name

For details about the cjtracesync command, see cjtracesync (trace file synchronization for in-process HTTP server) in the uCosminexus Application Server Command Reference Guide.

(e) Cosminexus JPA Provider log

Table 4-9 Output destination of the Cosminexus JPA Provider log (Default)

Category	Contents	Log output destination and log file name^#	Default size number of files	Channel name
Operation log	SQL	In Windows Cosminexus-installation-directory\CC\server\public\ejb\server-name\logs\cjpa\cjpaoperation[n].log In UNIX /opt/Cosminexus/CC/server/public/ejb/server-name/logs/cjpa/cjpaoperation[n].log	1024KB 2	JPAOperationLogFile
Operation log	Transaction		1024KB 2	JPAOperationLogFile
Maintenance log	Maintenance information	In Windows Cosminexus-installation-directory\CC\server\public\ejb\server-name\logs\cjpa\maintenance\cjpamaintenance[n].log In UNIX /opt/Cosminexus/CC/server/public/ejb/server-name/logs/cjpa/maintenance/cjpamaintenance[n].log	1024KB 2	JPAMaintenanceLogFile
Maintenance log	Maintenance information	In Windows Cosminexus-installation-directory\CC\server\public\ejb\server-name\logs\cjpa\maintenance\cjpadefinition[n].log In UNIX /opt/Cosminexus/CC/server/public/ejb/server-name/logs/cjpa/maintenance/cjpadefinition[n].log	1024KB 2	--

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).

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

(f) Migration command (cjenvupdate) log

Table 4-10 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.

(g) Resource depletion monitoring log

Table 4-11 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.; For details about the ejb.server.log.directory parameter in the Easy Setup definition file, see 4.14.2 Parameters for setting option definition for J2EE server and 2.3 usrconf.cfg (option definition file for J2EE server) in the uCosminexus Application Server Definition Reference Guide.

#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.

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

When the output destination of the J2EE server, redirector, 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-12 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).
Redirector	In the case of Cosminexus HTTP Server Message log The JkLogFileDir parameter specified in the <configuration> tag of the logical Web server (web-server) of the Easy Setup definition file. The default is logs. Maintenance trace log The JkTraceLogFileDir parameter specified in the <configuration> tag of the logical Web server (web-server) of the Easy Setup definition file The default is logs.
Redirector	Microsoft IIS Message log log_file_dir key of Cosminexus-installation-directory\CC\web\redirector\isapi_redirect.conf The default key is Cosminexus-installation-directory\CC\web\redirector\logs. Maintenance trace log trace_log_file_dir key of Cosminexus-installation-directory\CC\web\redirector\isapi_redirect.conf The default key is Cosminexus-installation-directory\CC\web\redirector\logs.
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.

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 in the Smart Composer functionality in the uCosminexus Application Server Command Reference Guide.

The following table describes the output destination of integrated logs.

Table 4-13 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 10.10 manager.cfg (Manager settings file) in the uCosminexus Application Server Definition Reference Guide.

Table 4-14 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-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 /opt/Cosminexus/manager/log. For details about manager.cfg, see 10.10 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.12 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-15 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]^#².log	Maintenance log in RMI processing executed by Administration Agent	Log-output-directory-of-Manager\maintenance	16MB 8	N
Administration agent	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	Log-output-directory-of-the-Manager	64KB 4	N
Management Server	mngsvr.exe.[1-2 ].log	Management Server service log	Log-output-directory-of-the-Manager	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 garbage collection 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 for the J2EE servers	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	--	N
	cjhttp_comm.time-information.inprocess_http.mm	Communication trace information	Manager-log-output-directory\maintenance\maintenance\http\maintenance\comm	About 3.2 MB 16	N
	cjmemorywatch[n].log	Resource depletion monitoring log (Memory)	Manager-log-output-directory\maintenance\watch	16.6 MB 16	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 10.10 manager.cfg (Manager setup 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-16 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
Administration agent	processConsole[n]^#2.log	Console log	Log-output-directory-of-the-Manager	64KB 4	N
Administration agent	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	Log-output-directory-of-the-Manager	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 garbage collection 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 for the J2EE servers	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	--	N
	cjhttp_comm.time-information.inprocess_http.mm	Communication trace information	Manager-log-output-directory/maintenance/http/maintenance/comm	About 3.2 MB 16	N
	cjmemorywatch[n].log	Resource depletion monitoring log (Memory)	Manager-log-output-directory/maintenance/watch	16.6 MB 16	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.

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 10.21 Logical user server definition files 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.

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
Server Communication Agent	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].^#2log	JavaVM log file of the Server Communication Agent		256 KB 4	N

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

4.3.1 Acquiring the Cosminexus Component Container Logs

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

(a) J2EE server and redirector log

(b) Server management command log

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

(d) In-process HTTP server log

(e) Cosminexus JPA Provider log

(f) Migration command (cjenvupdate) log

(g) Resource depletion monitoring log

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

(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