How to collect data from the ePO and SQL servers for a Tomcat-related SQL connection leak

Technical Articles ID: KB92272
Last Modified: 2022-06-23 06:51:25 Etc/GMT

Environment

ePolicy Orchestrator (ePO) 5.10

Summary

This article describes how to collect data to help identify and troubleshoot extension-related connection leak issues. These issues are where the ePolicy Orchestrator (ePO) Application Server (Tomcat) service leaks connections to the SQL database. Such issues can potentially lead to port exhaustion and an inability for any new connections to be made to the SQL database. When the connection leak has escalated to this point, the ePO logon page might display a warning similar to the following:

The license for ePolicy Orchestrator is invalid

The orion.log in the ePO_installation_directory\Server\Logs folder contains a more detailed error message:

java.sql.SQLException: com.mcafee.orion.core.db.base.DatabaseConnectivityException: Failed to get a connection: Network error IOException: No buffer space available

Solution 1

IMPORTANT: The data collection steps below must be performed before ePO completely exhausts the available connection pool on the SQL Server.

Implement the following recommendations when the ePO logon page displays the error message The license for ePolicy Orchestrator is invalid:

Restart the Application Server service (restores functionality temporarily)
Wait 30 minutes to an hour. This time allows enough connections to build within the SQL database to be noticeable when you review the following data.

Execute the SQL query below against the primary ePO database. This action outputs a list of open connections grouped by frequency of occurrence.

NOTE: See "Solution 2" for steps on how to capture the data in a readable format for support.

SELECT DEST.TEXT,
COUNT(distinct SDEC.[most_recent_session_id])
FROM sys.[dm_exec_connections] SDEC
CROSS APPLY sys.[dm_exec_sql_text](SDEC.[most_recent_sql_handle]) AS DEST
GROUP BY Dest.Text
ORDER BY 2 desc

Using a text editor, open the log-config.xml file located in ePO_install_folder\server\conf\orion\.
Search for jdbc.sqlonly, and set the value to trace.

Below are some examples of log-config:

5.10 CU10 and earlier:

</logger>

5.10 CU11 and later:

Save the changes, and wait a few moments for the logging to take effect. You don't need to restart the Application Server service.
Collect the following:

Both the results of the SQL query in Step 1 above. Provide the file in RPT format (as described in "Solution 2").
The trace-level of the orion.logs.

Provide the files to Technical Support for review.

Solution 2

Export the SQL Query results to a readable format:

Log on to SQL Server Management Studio.
Right-click the ePO server and select New Query.
Paste the SQL query below into the query window.

SELECT DEST.TEXT,
COUNT(distinct SDEC.[most_recent_session_id])
FROM sys.[dm_exec_connections] SDEC
CROSS APPLY sys.[dm_exec_sql_text](SDEC.[most_recent_sql_handle]) AS DEST
GROUP BY Dest.Text
ORDER BY 2 desc
Above the toolbar, click the Query menu item.
Click Results To, Results to File, or use the shortcut Ctrl+Shift+F.
Click Execute on the toolbar, or press F5.
To save the output, select a location and leave the Save As Type field as the default, Report files (*.rpt)
To revert the output to the default, click Query, Results to, Results to Grid. Or, use the shortcut Ctrl+D.

Knowledge Center

How to collect data from the ePO and SQL servers for a Tomcat-related SQL connection leak

Environment

Summary

Solution 1

Solution 2

Related Information

Affected Products

Languages:

Title

Title

Knowledge Center

How to collect data from the ePO and SQL servers for a Tomcat-related SQL connection leak

Environment

Summary

Solution 1

Solution 2

Related Information

Affected Products

Languages:

Choose your region

Title

Title