When installing or running the OpenEdge Memory Profiler tool, you may encounter a few common issues related to permissions, configuration, or runtime behavior. This section lists these issues along with their recommended solutions to help ensure a smooth setup and operation experience.

The Required file is locked by another process

Platform: Windows

Description: During installation, an error appears in <oemp-install-dir>/oemp/bin/create_oemp.txt log file indicating that a file is locked by another process. This typically occurs due to insufficient permissions in the <DLC> path when registering the PAS for OpenEdge instance.

Solution: Run the installer as an Administrator or adjust file permissions for <DLC>/servers/pasoe/conf/instances.windows.

Permission denied

Platform: Linux

Description: During installation, a "Permission denied" error appears in <oemp-install-dir>/oemp/bin/create_oemp.txt log file, typically related to the instances.unix file. This occurs because the DLC/servers/pasoe directory may be owned by root and not accessible to non-root users. While the installation routine must be executed as root, it is not only supported but also recommended to run the PAS for OpenEdge instance as a non-root user in production environments.

Solutions:
  • Use sudo to run the installer.
  • Run the PAS for OpenEdge instance as a non-root user by following these steps:
    1. Verify executable permissions—Ensure that <DLC>/bin executables are owned by root and have 4755 permissions.
    2. Change ownership of the PAS for OpenEdge directories—Update ownership of both CATALINA_HOME (<DLC>/servers/pasoe) and <CATALINA_BASE> (the instance directory) to be owned by the same group as the user who will run the instance, for example: ensure that the user belongs to a group such as, progress that has appropriate access rights. Then, update the ownership of both the directories to be owned by root and the designated group:
      chown -R root:progress $DLC/servers/pasoe <instance_path>
    3. Run the PAS for OpenEdge instance as the intended user—Run tcman or pasman by using one of the following methods:
      su someuser -c "<command>"

      Or,

      runuser -l <userName> -c '<command>'
      For more information, see Run PAS for OpenEdge as a non-root user.
  • Create a dedicated user group for the DLC directory and assign the instance-creating user to that group with appropriate read and write access. This allows controlled access without requiring root privileges.

Missing JAVA_HOME directory

Platform: Windows/Linux

Description: During installation, an informational message appears about a missing or misconfigured JAVA_HOME directory.

Solution: Edit the DLC/properties/java.properties file and replace all backslashes (\) with forward slashes (/).
Note: This is a warning only and does not impact the installation of the OpenEdge Memory Profiler tool.

Recordings do not appear on the home page

Platform: Windows/Linux

Description: Files placed in the import directory may not automatically appear on the Recordings home page. This issue can occur due to the following common reasons:
  • The files do not have a .oemp extension or are not text files.
  • The files are not located within a watched directory.
  • The reportdb database has not started successfully, or the application is unable to establish a connection to it.

Solutions:

  1. Ensure that all files use the .oemp extension and are confirmed to be text files. Then, open the batch.config configuration file located at <CATALINA_BASE>/openedge. This file defines the multiple locations or directories that the application monitors for new files. For more information, see Modify batch configuration file. Place the files in one of the specified watched directories. Use the Refresh button in the UI to manually trigger an update that requests fresh data from the API.
  2. To determine if the issue is related to the database, review the application’s log files. Start with the Activate-<DATE>.log files located in <CATALINA_BASE>/temp. These logs indicate whether a connection to reportdb was successfully established. Common errors may include:
    • Insufficient user licenses allowed by the database.
    • Incorrect or inaccessible database path.
    If these logs do not provide sufficient insight, check the reportdb.lg database log file at <CATALINA_BASE>/db to confirm whether the database started successfully. For more information, refer to the troubleshooting topic "Identify issues through logging."

Uninstall does not remove all files

Platform: Windows/Linux

Description: Residual files remain after uninstalling the OpenEdge Memory Profiler tool. When trying to create a new PAS for OpenEdge instance, you may encounter a similar error message, indicating that the previous PAS for OpenEdge instance was not properly removed by the oemp delete command's request to the TCMAN utility:
The instance alias name is already in use – oemp
Solution: In the <DLC>/servers/pasoe/conf directory, locate the instances.windows or instances.unix file, depending on your OS installation. Identify the entry corresponding to the old PAS for OpenEdge instance, typically named as oemp. Remove the relevant line and save the file.
Note: Administrator or sudo privileges may be required to perform this change.

Recordings appear on the home page but were not automatically imported

Platform: Windows/Linux

Description: Files may appear on the Recordings home page, indicating they were placed in a watched directory, but may not be automatically imported. This behavior can occur due to the following common reasons:
  • The auto-import configuration is not properly set for the intended watched directory.
  • The watcher process has not yet scanned for files eligible for automatic import.
  • The watcher background process did not start as expected.
  • The AVM writing the recording file did not terminate, leaving the recording incomplete.

Solution: To confirm that the files were placed in a directory configured for automatic import, open batch.config located at <CATALINA_BASE>/openedge. Watched directories that support automatic import have the auto property set to true. For more details on modifying this configuration, see Modify batch configuration file.

The watcher process scans configured directories at regular intervals, which is every 60 seconds by default for files eligible for automatic import. To qualify, files must:
  • Reside in a watched directory configured for auto-import.
  • Have a .oemp file extension.
  • Be text files, not binary.
  • Contain the final _Exit snapshot.
Note: The OpenEdge Memory Profiler tool allows a maximum of two simultaneous imports by default, one automatic and one manual.
Review the log file located at <CATALINA_BASE>/temp/Watcher-<DATE>.log for information about the background watcher process. If this file is missing, the process may not have started. In such cases, stop and restart the PAS for OpenEdge instance.

If the log file is present, it may contain error messages or other diagnostic information indicating the cause of the issue.

For more information, refer to the troubleshooting topic "Identify issues through logging."

Identify issues through logging

Platform: Windows/Linux

Description: For issues not explicitly covered in this section, additional diagnostic information may be available within the running PAS for OpenEdge instance. Understanding the location and purpose of log files can help you troubleshoot independently or provide more context when contacting technical support.

Solution:When encountering unexpected behavior or specific error messages, refer to the appropriate log file directories. Each directory serves a distinct purpose. The following log files provide diagnostic information for various components and processes within the PAS for OpenEdge environment:
  • Standard PAS for OpenEdge logs—Located at <CATALINA_BASE>/logs, these logs capture general runtime activity for the PAS for OpenEdge instance. The most relevant files are agent logs generated by each ABL application, which provide insights into the operation of MSAgent processes.
    • rptbatch.agent.<DATE>.log—Agent logs for batch processing
    • rptview.agent.<DATE>.log—Agent logs for report processing
    If the PAS for OpenEdge instance or its agents fail to start, error messages will typically appear in these files.
  • Application-specific logs—Located at <CATALINA_BASE>/temp, these logs pertain to internal operations of the OpenEdge Memory Profiler tooling, including the API layer and batch operations. They also contain statistics and messages related to recording imports.
    • Activate-<DATE>.log—Tracks any messages or errors from the session activate procedure used for all ABL Sessions, especially dynamic connections to the reportdb database instance.
    • MemProfParse-<DATE>.log—Tracks any messages or errors from the recording import process. At a minimum, it logs the start and end of recording import processes.
    • Profiler-A<AGENT_PID>-S<ABL_SESSION_ID>.log—Captures general messages from rptbatch or rptview ABL applications. This log reflects only internal messages from the application itself.
    • Watcher-<DATE>.log—Tracks operations performed by the background watcher process, which is responsible for detecting files eligible for automatic import.
  • Logging configuration—Located at <CATALINA_BASE>/openedge, the logging.config can be used to set logging level for all the log files. The default logging level is set to INFO.
    Note: Increase the logging level only if instructed by technical support. Higher logging levels can significantly increase the volume of messages and generate additional output files, which may consume disk space. Avoid setting it higher than DEBUG, as TRACE can significantly impact application performance and generate excessive log output.
  • Database logs—Located at <CATALINA_BASE>/db/, the reportdb.lg log file is generated by the OpenEdge RDBMS and provides information about database startup and runtime issues. It is the standard log file for the reportdb database started with the PAS for OpenEdge instance.
  • Windows-specific logs—Located at <CATALINA_BASE>/bin/, these logs are created by PowerShell scripts executed by batch scripts. These scripts are responsible for starting and stopping the database and watcher processes during PAS for OpenEdge instance startup and shutdown. If you encounter issues during either of these management actions, check the following Windows-specific log files for diagnostic information:
    • instance_started.log—Logs output from the PowerShell script executed by the instance_startup.bat utility during PAS for OpenEdge instance startup.
    • instance_shutdown.log—Logs output from the PowerShell script executed by the instance_shutdown.bat utility during PAS for OpenEdge instance shutdown.