Progress Application Server for OpenEdge uses three distinct and independent logging subsystems to record events.
1. Generic Tomcat Logs (catalina*, localhost*, manager*, host-manager*)
- Tomcat logs are configured in <CATALINA_BASE>/conf/logging.properties.
- By default this logging subsystem uses the Operating System default buffering. Delays in writing to these logs are usually not noticeable.
- Immediate writes can be forced by adding a bufferSize property with a value less than zero to whichever file handler needs to be forced. For example in the logging.properties file:
2localhost.org.apache.juli.FileHandler.level = INFO
2localhost.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
2localhost.org.apache.juli.FileHandler.prefix = localhost.
2localhost.org.apache.juli.FileHandler.bufferSize = -1
2. PASOE Web App Log (<PAS instance name>.<date>.log)
- Web App Logs are configured in <CATALINA_BASE>/webapps/<Web app name>/WEB-INF/logging.xml.
- By default these logs are not buffered. There is no need to add "<immediateFlush>true</immediateFlush>" to force writes because this is the default
- Buffering may be added for increased performance by adding an immediateFlush property in the encoder node of logging.xml. For example:
<encoder>
<!-- add the timestamp as milliseconds to facilitate logfile post processing -->
<!-- -->
<!-- <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern> -->
<pattern>%d{HH:mm:ss.SSS}/%r [%thread] %-5level %logger{36} - %msg%n</pattern>
<immediateFlush>false</immediateFlush> <!-- -->
</encoder>
3. PASOE Agent Log (<PAS instance name>.agent.log)
- PASOE Agent logs are configured in <CATALINA_BASE>/conf/openedge.properties.
- By default these logs are buffered, but the buffering is not configurable.
- Delay in writing entries to the Agent log may be noticed when events are infrequent. If this is inconvenient in a testing situation, stopping the PAS server will flush all entries to disk so that the log can be examined.
