When debugging an issue with PAS for OpenEdge, there are several areas to consider:

  1. Tomcat layer—handles the incoming messages
  2. Session Manager layer—manages incoming messages to the multi-session agent
  3. Multi-session agent layer—handles ABL requests

Methodology for troubleshooting

  1. Because the majority of activity occurs within the agent the common place to begin investigating a problem is within the abl-app-name .agent. date .log file.
  2. Scan the file for the time of the error. Time is based on the system time of the PAS for OpenEdge Tomcat process.
  3. If no errors are listed there: go one level higher to the abl-app-name . date .log .
  4. Scan the file for the time of the error.
  5. If no errors are listed within these files at the expected time, search higher still to see if an error is recorded in either of these log files:
    • catalina. date .log
    • localhost. date .log
    • localhost-access. date .log
  6. If the error cannot be found in these log files, change the verbosity of your log output by setting the logging levels in logging-pasoe.properties and logging-tomcat.properties . This is described in Configure logging in PAS for OpenEdge.
  7. You can specify additional Log Entry Types in openedge.properties for your agent. For example:
    • DB.Connects
    • DynObjects.DB (you can log all DynObjects information by using DynObjects.* )
    • DynObjects.XML
    • DynObjects.Other
    • FileID
    • QryInfo
    • ProEvents.UI.Char
    • ProEvents.UI.Command
    • ProEvents.Other
    • SAX

    For more information about the log entry types, see Log Entry Types (-logentrytypes), Log entry types, and Log Entry Types Detail.

  8. If memory consumption for the multi-session agent is continually increasing, there may be memory leaks in the application code. See the following articles for more information:
    Note: If an item shows up as a potential leak, that does not mean that it is actually the problem. These articles simply report on objects that are sticking in memory.