3.3.18 Settings for acquiring the WebSocket container log
This subsection describes the items that you can set up for acquiring the WebSocket container log.
The following table describes the settings of the items that you can change for acquiring the WebSocket container log and the corresponding parameters of the Easy Setup definition file.
|
Log or trace |
Items |
Corresponding parameters of the Easy Setup definition file |
|---|---|---|
|
Access log |
Whether the access log is output |
ejbserver.logger.access_log.websocket.enabled in the <configuration> tag on a logical J2EE server (j2ee-server) (By default, the access log is not output.) |
|
Format when the access log is output |
ejbserver.logger.access_log.websocket.format in the <configuration> tag on a logical J2EE server (j2ee-server)# |
|
|
File size of the access log |
ejbserver.logger.channels.define.WebSocketAccessLogFile.filesize in the <configuration> tag on a logical J2EE server (j2ee-server) |
|
|
Number of files of access log |
ejbserver.logger.channels.define.WebSocketAccessLogFile.filenum in the <configuration> tag on a logical J2EE server (j2ee-server) |
|
|
Trace based performance analysis |
-- |
Specify acquisition condition, when you want to execute the cprfed command for performing a daily system operation same as for other trace based performance analysis. For details about acquiring the trace based performance analysis files, see 7. Performance Analysis by Using Trace Based Performance Analysis. |
- Legend:
-
--: Not applicable
- #
-
In the access log, you can customize the log output format by defining the format with the above-mentioned keys. For customization of the access log of the NIO HTTP server, see 6.11.2 Customizing the access log of the NIO HTTP server in the uCosminexus Application Server Web Container Functionality Guide.