4.4.1 Acquiring the Cosminexus Component Container Logs (systems executing batch applications)
This section describes the types and output destinations of Cosminexus Component Container logs. There are two types of Cosminexus Component Container logs:
-
Batch server, server management commands, batch application logs
-
Administration agent, Management agent, Management Server logs
The output destination of each of the log is described below.
- Organization of this subsection
(1) Acquiring the batch server, server management commands, batch application logs
This point describes how to acquire the batch server, server management commands, and batch application logs.
Furthermore, in Cosminexus Component Container, the migration command logs are output in addition to these logs. When the resource depletion monitoring functionality is used, the resource depletion monitoring log is output.
-
The four types of batch server logs are 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 batch server.
-
The three types of server management command logs are message log, exception log, and maintenance log.
-
The one type of batch application log is message 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 batch 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.
- 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 batch 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 batch 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 batch server is running
-
When the batch server process is stopped externally by TerminateProcess
-
When the batch 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 batch server is output to this log. The output destination differs depending on the settings in the UNIX syslog.
Note that the event log is not output depending on how the batch 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 batch server is running
-
When the batch server process is stopped externally by the SIGKILL signal (such as kill -9)
-
When the batch 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) in 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) Batch server log
|
Category |
Contents |
Log output destination and log file name#1 |
Default size × number of files |
Channel name |
|---|---|---|---|---|
|
Message log |
Operation log |
|
1MB × 2 |
MessageLogFile |
|
Log operation log#3 |
|
1 MB × 2 |
-- |
|
|
Operation log of resource adapter that is deployed and used in batch server#4 |
|
1MB × 2 |
-- |
|
|
User log |
User output log |
|
1MB × 2 |
UserOutLogFile |
|
User error log |
|
1MB × 2 |
UserErrLogFile |
|
|
JavaVM maintenance information and GC log |
|
4MB × 4 |
-- |
|
|
Event log of the Explicit Memory Management functionality |
|
4MB × 4 |
-- |
|
|
Exception log |
Exception information when an error occurs |
|
1MB × 2 |
ExceptionLogFile |
|
Maintenance log |
Maintenance information |
|
16MB × 4 |
MaintenanceLogFile |
|
Console message |
|
1MB × 2 |
ConsoleLogFile |
|
|
EJB container maintenance information |
|
1MB × 2 |
EJBContainerLogFile |
|
|
Start process standard output information#5 |
|
-- |
-- |
|
|
Start process standard error information#5 |
|
-- |
-- |
|
|
Termination process information |
|
4KB × 2#6 |
-- |
|
|
Event log |
Log showing batch server start, stop or abnormal termination |
Application log of Windows event viewer#7 |
-- |
-- |
|
syslog |
Log showing batch server start, stop or abnormal termination |
Depends on UNIX syslog settings. #8 |
-- |
-- |
- Legend:
-
--: Not applicable
- Note:
-
Channel name is the name that identifies the log output destination.
- #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).
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, see 3.2.1 usrconf.cfg (Option definition file for batch servers) in the uCosminexus Application Server Definition Reference Guide.
- #3
-
Check the file size when the file is output. If the maximum size is exceeded when the file size is checked, change the name of the cjlogger.log file to the name of the backup file (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 settings for acquiring resource adapter logs, see 3.3.11 Settings for Acquiring the Resource Adapter Logs.
- #5
-
It is a log in which only the start process information is acquired. As it is output mainly while starting and terminating the batch 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.
- #6
-
The size and number of files cannot be changed.
- #7
-
The output destination of the log file differs depending on the Windows event log settings.
- #8
-
To output messages related to batch 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.
(b) Server management command log
|
Category |
Contents |
Log output destination and log file name#1 |
Default size × number of files |
Channel name |
|---|---|---|---|---|
|
Message log |
Operation log#2, #3 |
|
1024KB × 3 |
MessageLogFile |
|
Log operation log#2 |
|
1024KB × 2 |
-- |
|
|
Exception log |
Exception information when an error occurs#2, #3 |
|
1024KB × 6 |
ExceptionLogFile |
|
Maintenance log |
Maintenance information#2 |
|
1024KB × 3 |
MaintenanceLogFile |
|
Console message#2 |
|
32KB × 3 |
ConsoleLogFile |
|
|
Maintenance information of the server management command#2 |
|
32KB × 3 |
ServerAdminLogFile |
- Legend:
-
--: Not applicable
- Note:
-
Channel name is the name that identifies the log output destination of the log. Use it as a key value when changing log attributes (size, number of files).
- #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, default size, and the number of files are as follows:
- #
-
In the part of the log file name [n], the file number (number of files from 1 (maximum 16)) is added.
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 message is output at the server side.
(c) Batch application log
|
Category |
Contents |
Log output destination and log file name#1 |
Default size × number of files |
|---|---|---|---|
|
Message log |
Operation log of the cjexecjob command, the cjkilljob command, and the cjlistjob command |
|
1MB × 2 |
- #1
-
In the part of the log file name [n], the file number (number of files from 1 (maximum 16)) is added.
- #2
-
The <batch.log.directory> indicates a directory specified in the batch.log.directory of option definition file (usrconf.cfg file) for batch applications. The default values are as follows:
In Windows
Cosminexus-installation-directory\CC\batch\logs
In UNIX
/opt/Cosminexus/CC/admin/logs
(d) 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 |
|
1MB × 2 |
|
Exception log |
Exception information when an error occurs |
|
1MB × 2 |
|
Maintenance log |
Maintenance information |
|
1MB × 2 |
- #
-
In the part of the log file name [n], the file number (number of files from 1 (maximum 16)) is added.
(e) 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 |
|
4MB × 4 |
|
Exception log |
Exception information of the cjenvupdate command |
|
4MB × 4 |
|
Maintenance log |
Maintenance information of the cjenvupdate command |
|
4MB × 4 |
- #
-
In [n], the file number (number of files from 1 (maximum 16)) is attached.
(f) Resource depletion monitoring log
|
Monitored Resources |
Log acquisition location and log file name#1 |
Default size × number of files |
Channel name |
|---|---|---|---|
|
Memory |
|
1MB × 2 |
MemoryWatchLogFile |
|
File descriptors |
|
1MB × 2 |
FileDescriptorWatchLogFile |
|
Threads |
|
1MB × 2 |
ThreadWatchLogFile |
|
Thread dump |
|
1MB × 2 |
ThreaddumpWatchLogFile |
|
HTTP requests pending queue |
|
1MB × 2 |
RequestQueueWatchLogFile |
|
HTTP session numbers |
|
1MB × 2 |
HttpSessionWatchLogFile |
|
Connection pool |
|
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 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, see 3.2.1 usrconf.cfg (Option definition file for batch servers) 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 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.
(g) User definition file to set output destination of the log
When the batch 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.
|
Category |
Location specified for user definition file |
|---|---|
|
Batch server |
The ejb.server.log.directory parameter specified in the <configuration> tag of the logical J2EE server (j2ee-server) in 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 logs when operating from the Management Server Remote Management functionality. |
For details about settings of the data acquisition for troubleshooting, such as how to change the output destination of log, see 3. Preparing for Troubleshooting.
(2) Acquiring the log of Administration agent, Management agent, and Management Server
This point describes the output destination of Administration Agent, Management Agent, and the Management Server log.
For the Administration Agent, Management Agent, and the Management Server logs, besides acquiring separately, you can also acquire these logs by compiling as a integrated log.
For details about the output destination when acquiring the Administration Agent, Management Agent, and the Management Server log by compiling as an integrated log or separately, see 4.3.1(2) Acquiring the log of Administration agent, Management agent, and Management Server.
(3) Required information to be acquired other than a log
For details about the required information to be acquired other than a log, see 4.3.1(6) Required information to be acquired other than a log.