Logging Considerations

Edit online

Refer to the following consideration when viewing log files:

  • To check the CM or engine log file on Microsoft™ Windows™, use the Notepad application. WordPad will not open the log file because the file is locked by the application. If you want to use WordPad, copy the file before opening it.
  • A connection time-out with a remote node causes a listen time-out exception in an Secure Proxy log.
  • CM uses the log4j tool to log messages. The configuration file that controls the CM log is called log4j.properties. By default, the logging level is set to INFO and includes warning, error, and informational messages. You can change the log level to DEBUG but this is not recommended because DEBUG generates a large amount of logs and may affect system performance.
  • To configure the CM log to write debug messages, open the log4j.properties file located in install_dir /conf where install_dir is the location of the CM installation.
  • To write debug messages for the Jetty web server, add the following statements: 
    # GUI log4j 
log4j.logger.sspdashboard=DEBUG,R,stdout 
log4j.logger.sspjsf=DEBUG,R,stdout 
log4j.logger.com.sterlingcommerce.sspgui.web=DEBUG,R,stdout
log4j.logger.com.sterlingcommerce.csp.gui.web=DEBUG,R,stdout
log4j.logger.com.sterlingcommerce.hadrian.client.gui=DEBUG,R,stdout
  • To write debug messages for CM, add the following statements: 
    #CM log4j 
log4j.logger.com.sterlingcommerce.component.configurator=DEBUG,R,stdout
log4j.logger.com.sterlingcommerce.hadrian.system=DEBUG,R,stdout
log4j.logger.com.sterlingcommerce.component.accepter.csap.impl.AccepterImpl=INFO,R,stdout
log4j.logger.com.sterlingcommerce.component.dispatcher.XmlConversionFilter=INFO,R,stdout