Implementation Guide › Diagnose Implementation Issues › Work with Support › Resource Leaks

Resource Leaks

If a system resource, such as memory, file handles, network connections, sockets, or disk space, is not being released, the following lists the information that helps Support probe for additional details. This information is not required to open a Support ticket, but is information that Support is likely to request. If you provide this information initially, it can reduce the amount of time it takes Support to resolve the issue.

1. Gather environment information.
2. Describe the problem in as much detail as possible. Include at least the following:
   • The frequency of the resource leak.
   • The size of the resource leak. Measure the resource leak over a time period with a tool that can show the resource allocation, such as prstat.
   • The tool that you used to measure the resource leak.
   • The effect the resource leak has on the system.

     Example: The system crashes or hangs.

   • The steps to reproduce the resource leak or a reproduction test based on the application traffic.
3. Attach logs:
   • (Policy Server) If you are experiencing a Policy Server issue, attach the Policy Server log and the Policy Server audit log.
   • (Web Agent) If you are experiencing a Web Agent issue, attach the Web Agent log and the web server error log.

   Note: If you are attaching log files, be sure that the set of files match and that all are from the same time as when the issue occurred.