The development check log is output to a file generated on the console or at the following path:

Log-output-directory-for-J2EE-servers-(ejb.server.log.directory)\cjdevelopment[n].log

n indicates the number of log files. The settings for the number of files n are described in 24.4(4)Settings for number, size, and level of log files.

The development check log messages are output in the following format:

The following information is output in the "message text":

• Log level
• Name of the class that outputs the message
• Name of the method that outputs the message
• Message details

Furthermore, the message text is output in two separate rows as follows:

Note

If stack trace is output, the trace is output from the 2^nd row onwards (if no message is specified), or from the 3^rd row onwards.

For details on the contents output apart from the message text, see 5.2.1 Format of output and items output to Hitachi Trace Common Library log in the manual uCosminexus Application Server Maintenance and Migration Guide.

The development check log can be output in the following nine levels. From item no. 2 to 8, higher the item no., more detailed is the information that is output.

Table 24-1 Log levels provided for the development check log

#

• The contents of the message to be output, described in the Remarks column, are standard.
• If you specify the OFF level, the log file is not generated (if the log file already exists, there is no execution).
• We recommend that you set a level higher than INFO so that more detailed information is output during development.

You specify the settings for the number, size, and level of development check log files in the <configuration> tag of the logical J2EE server (j2ee-Server) in the Easy Setup definition file.

The following table lists and describes the keys that can be used to set up the number, size, and level of log files.

Table 24-2 Details of keys that can be used to set up the number, size, and level of development check log files

Legend:

--: Not applicable

Note "Default value" is the value that is assumed when no key is specified.

Hint

Specifying the log level

To troubleshoot the application being developed, we recommend that you first set the INFO level. If the information output at the INFO level is inadequate for investigation, specify the CONFIG or FINE levels that output more detailed log. If you require further details, specify the FINER level.

You, thus, specify levels that output details in a graded manner, as and when required, and obtain detailed information.

The following is an example of using the Easy Setup definition file to set up the number, size, and level of development check log files:

:
 <logical-server-name>j2ee-server</logical-server-name>
 <configuration>
  <param>
  <param-name>
   ejbserver.logger.channels.define.DevelopmentLogFile.filenum
  </param-name>
  <param-value>4</param-value>
  </param>
  <param>
  <param-name>
   ejbserver.logger.channels.define.DevelopmentLogFile.filesize
  </param-name>
  <param-value>1048576</param-value>
  </param>
  <param>
  <param-name>
   ejbserver.logger.DevelopmentLogFile.level
  </param-name>
  <param-value>OFF</param-value>
  </param>
 </configuration>
:

For details on the parameters and the Easy Setup definition file, see 2.4 usrconf.properties (User property file for J2EE servers) and 4.6 Easy Setup definition file in the manual uCosminexus Application Server Definition Reference Guide.