Configure Logging

EDG uses slf4j/log4j as the logging library. The log level can set by the customer as well as the rotation and format. Some of the logging can be accessed in the user interface by administrators; errors, warnings and information.

You can filter, send the log to TopQuadrant support or download it from the user interface. Additional logging is available through the container, Tomcat. This will include access and startup logs

To configure the log size and rotation, modify the log4j2.xml file found at “tomcat”/edg/web-inf/setupdata.

If you encounter server startup problems, the following settings in Apache Tomcat’s conf/logging.properties file can give you a better picture of what’s going on:

handlers = 1catalina.org.apache.juli.FileHandler, 2localhost.org.apache.juli.FileHandler,
  3manager.org.apache.juli.FileHandler, 4host-manager.org.apache.juli.FileHandler,
  5edg.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler
5edg.org.apache.juli.FileHandler.level = FINE
5edg.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
5edg.org.apache.juli.FileHandler.prefix =edg.
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/edg].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/edg].handlers = 5edg.org.apache.juli.FileHandler

Keep in mind that the handlers setting would replace the existing one. It is shown as three lines above, but should be one line in your logging.properties file.

Tomcat Settings – other

  • A tomcat SSL connector, without an exclusion rule will require some characters be encoded where a flat http connector will not. This can cause problems with embedded links.

  • Set the following in Tomcat relaxedPathChars=”<>” relaxedQueryChars=”<>”