3.3.11 Settings for Acquiring the Resource Adapter Logs
This subsection describes the settings to acquire the resource adapter logs. The following two settings are required to acquire resource adapter logs.
-
Settings for application of the log output
Set up the availability of output of the log for each resource adaptor by the server management commands. Acquire Hitachi Connector Property file by the cjgetrarprop command and specify true for LogEnabled in the <property> tag. After editing the file, use the cjsetresprop command to apply the edited contents. Note that for defining the property before deploying the resource adapter, use the cjgetrarprop and cjsetrarprop command.
For details about Hitachi Connector Property file, see 4.1 HITACHI Connector Property file in the uCosminexus Application Server Application and Resource Definition Reference Guide. For details about the above commands, see the uCosminexus Application Server Command Reference Guide. For details about the operations of the server management commands, see 3. Basic Operations of Server Management Commands in the uCosminexus Application Server Application Setup Guide.
-
Setting the size, number, and the level of logs
Set up the size and number of resource adapter logs in the following parameter in the <configuration> tag of logical J2EE server (j2ee-server) in the Easy Setup definition file.
-
ejbserver.connector.logwriter.filesize
Set up the maximum size for each resource adapter log file. (unit: byte).
-
ejbserver.connector.logwriter.filenum
Specify the number of resource adapter log files.
Moreover, the log output level of the J2EE server (log level) is considered as the log level of the resource adapter. For details about settings of the log level of the J2EE server, see 3.3.6(3) Changing the log level.
- Important note
-
-
For the CJMSP resource adapters, methods to set up log size, number of files, and log levels differ from the other resource adapters. For details, see the subsection 3.3.13 Settings for collecting Cosminexus JMS Provider logs.
-
If the sum of the length of the log output destination directory of the resource adapter and the length of the resource adapter display name exceeds the path length restrictions for the OS, the initialization of the resource adapter log fails, the KDJE90002-E message is output, and then the server stops. This occurs in the cases such as when the log file is locked by another process.
Use one of the following steps to ensure that the resource adapter log does not exceed the maximum path length. For details, see the uCosminexus Application Server System Setup and Operation Guide.
- Change the length of the resource adapter display name
- Change the log output destination directory or work directory
Also, do not lock the log file with another process.
-
If the initialization of the resource adapter log fails, the KDJE90002-E message is output and then the J2EE server stops. This occurs when the sum of the path length of the log output destination directory of the resource adapter and the length of the resource adapter display name exceeds the path length restrictions for the OS, or in the cases such as when the log file is locked by another process.
Change the length of the resource adapter display name, or change the log output destination directory or work directory to ensure that the resource adapter log does not exceed the maximum path length. Also, do not lock the log file with another process.
-
-