2.6.1 Precautions Related to the System Log of an EJB Client Application
The precautions when referencing a system log output by an EJB client application in a shared sub-directory mode and operating the shared sub-directory mode EJB client applications are described below:
-
The valid data in the log file is from the start of the file up to the EOF.
In the system log of an EJB client application, the log data is overwritten from the beginning sequentially when the log file is wrapped around, without deleting the log data prior to wrap around. For this reason, when referencing a log file, ignore the data after the EOF. The data after the EOF is the invalid log file data prior to wrap around.
The end of the valid log file data is the data shown below:
EOF CRLF CRLF CRLF CRLF----------< End of Data >----------CRLF CRLF
EOF are characters (0x1A) denoting the end of trace data. CRLF denotes line feed (0x0D, 0x0A).
The example of output is described below. Further, the character showing the end of trace is described as [EOF].
-
In Windows
**** "OS name (including details such as OS version)" TZ="time zone name" xxxx/xx/xx xx:xx:xx.xxx yyyy/mm/dd hh:mm:ss.sss pid tid message-id message(LANG=ja) 0000 xxxx/xx/xx xx:xx:xx.xxx HEJB BE3F6FE9 015EE671 KDJEXXXXX-W xxxxxxxxx 0001 xxxx/xx/xx xx:xx:xx.xxx HEJB BE3F6FE9 015EE671 KDJEYYYYY-I yyyyyyyyy 0002 xxxx/xx/xx xx:xx:xx.xxx HEJB BE3F6FE9 015EE671 KDJEZZZZZ-I zzzzzzzzz [EOF] ----------< End of Data >---------- <<Invalid data before wraparound>>... ... ... -
In UNIX
**** "OS name (Including details such as OS version)" TZ=Asia/Tokyo xxxx/xx/xx xx:xx:xx.xxx yyyy/mm/dd hh:mm:ss.sss pid tid message-id message(LANG=ja) 0000 xxxx/xx/xx xx:xx:xx.xxx HEJB BE3F6FE9 015EE671 KDJEXXXXX-W xxxxxxxxx 0001 xxxx/xx/xx xx:xx:xx.xxx HEJB BE3F6FE9 015EE671 KDJEYYYYY-I yyyyyyyyy 0002 xxxx/xx/xx xx:xx:xx.xxx HEJB BE3F6FE9 015EE671 KDJEZZZZZ-I zzzzzzzzz [EOF] ----------< End of Data >---------- << Invalid data before wraparound>>... ... ...
-
-
At the time of starting an EJB client application process, a number of trace files specified in the ejbserver.logger.channels.define.channel-name.filenum key of system properties are created. At this time, trace files are initialized as space (0x20).
-
The capacity of the user log file is fixed as specified in the ejbserver.logger.channels.define.channel-name.filesize key of system properties. The trace files of the specified size are created at the time of process startup. For this reason, capacity does not increase or decrease as per the log output.
-
When you want to change the log file capacity or the number of files, you need to stop all the processes that output log in the relevant log files, and delete the log management files under the mmap directory and the log files or move them to a different directory.
-
In cases other than when you want to change the log file capacity or the number of files, do not change or delete the log files and the log management files. If you change or delete them, thereafter, the log may not be output correctly.
-
Do not delete the sub directories using the cjcldellog command where the EJB client application running in the shared sub-directory mode output log. If you delete such sub-directories, thereafter, the log may not be output correctly.
-
When starting an EJB client application in the shared sub-directory mode in the environment where the EJB client application is already running in the exclusive sub directory mode, specify a value different than that of the EJB client application running in an exclusive sub-directory mode in the ejbserver.client.ejb.log key of system properties. If the same value is specified, you cannot correctly manage the number of sub directories of the EJB client application operating in the exclusive sub-directory mode. Note that the exclusive sub-directory mode is used for compatibility with earlier versions.