Troubleshoot problems with an instance

Methodology for troubleshooting

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.

1. Open the abl-app-name.agent.date.log file.
2. Review the file for the time of the error. The time is based on the system time of the PAS for OpenEdge Tomcat process.
3. If no errors are listed, then go up one level to the abl-app-name.date.log file. For more information about ABL application logging, see Configure ABL application logging.
4. Review the file for the time of the error.
5. If no errors are listed within these files at the expected time, then go up another level to see if an error is recorded in one 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. See Configure logging in PAS for OpenEdge.
7. You can specify additional Log Entry Types in openedge.properties for your agent:
   • 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. For more information, see Find memory leaks using ABL object tracking.
9. If a severe error occurs on a multi-session agent, then a multi-session agent initiates a graceful shutdown of itself to avoid further failures. For more information, see Multi-Session agent initiated graceful shutdown.