JGAS log file

The JGAS provides for a daily log file to be created for the application you run. If you need to troubleshoot an application, enable the DAILYFILE element to capture messages for requests, proxies, system errors, and VM sessions.

A log file is created in the directory specified by the default resource log.file.path.

The log file is saved to a directory named with the current date in the format, YYYYMMDD, for example, 20170106. As you can redefine resources for each application or service deployed in the same war file, the logging configuration can vary from one application to another. Therefore, a separate DVM log file is created for each application you run. If the log file is enabled, it is identified by the application name, for example,appname.log.

The log file may contain the following information and messages:

A list of the field identifiers that define the detail in the logged output appears at the top; defaults are set in the log.file.columns resource. See FORMAT (under LOG for JGAS).
```
#Fields: date time relative-time location thread-id contexts event-type event-params
```
The configuration file settings for the application are shown at the top.
As the application runs, messages are written for HTTP requests and responses, the starting of proxies, system errors, etc. This output depends on the categories of logs specified in the CATEGORIES element.
Messages for different VM sessions are shown. These are prefaced in the contexts column by the output VM=session_number. Session numbering starts at zero and is incremented by one for each new VM session started. Sessions are also identified by their session id (SID).
```
2017/01/20 10:20:37.292 413.739 [UAProcess.java:96] 21 
        VM=0;SID=77eda293a4604483b10647442eedf929 "VM State" Move state VM Initialized -> VM connected.
...
2017/01/20 10:20:59.225 435.672 [UAProcess.java:96] 14 
        VM=1;SID=e5e11c2222fc43fa8121a8cbaad5a8cf "VM State" Move state VM Initialized -> VM connected
```