Performance issues in ePolicy Orchestrator 5.x when debug logging is enabled

Technical Articles ID: KB86593
Last Modified: 2023-07-20 10:37:43 Etc/GMT

Environment

ePolicy Orchestrator (ePO) 5.x

Problem

There are performance issues with ePO 5.x, such as slow startup, slow console navigation, or high CPU usage.

The orion.log records errors similar to the following:

DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.getString(17) returned Access Protection rule violation detected and blocked
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.wasNull() returned false
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.getInt(18) returned 155936856
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.wasNull() returned false
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.next() returned true
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.getInt(1) returned 1092
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.wasNull() returned false
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.getString(2) returned hip.file
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.wasNull() returned false
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.getString(3) returned access protection
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.wasNull() returned false
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.getInt(4) returned 5
DEBUG [core-QueryExecutor-thread-10] jdbc.resultset - 18804. ResultSet.wasNull() returned false

In addition, you see the following:

[execute-sql]
[echo] EPOCore:upgrade Start webapp upgrade
[echo] EPOCore:upgrade webapp upgrade done
[echo] EPOCore:Upgrade Start command postInstallSQLConfig
[echo] EPOCore:Upgrade End command postInstallSQLConfig
upgrade4.6.8:
upgrade5.0.0:
upgrade5.0.1:
upgrade5.1.0:
upReports45To50:
upReports46To50:
ReportingDefinitions46:
ReportingDefinitions50:
ReportingUpgrade46to50:
ReportingInstall50OnPremise:
upReports50To51:
[echo] EPOCore: Repairing any database integrity issues
[execute-sql]
[echo] EPOCore: Finished database integrity updates
BUILD SUCCESSFUL
Total time: 1002 minutes 27 seconds

Cause

ePO 5.x has added logging capability to include detailed SQL logging to the Orion.log file. The additional logging capability must be used only for troubleshooting purposes. This logging is resource-intensive and can cause many performance issues.

The configuration for this extra logging must be included in the log-config.xml file. But, sometimes, this log configuration might be missing from the log-config.xml file. This issue can occur after an upgrade from ePO 4.6. The issues occur when the upgrade carries over the existing log-config.xml file. It's seen when you've added some additional configuration to this file. In doing so, the new loggers that are normally included with a fresh installation of ePO 5.x aren't added. The default behavior for this extra logging is to be on. So, if these additional loggers are missing from the log-config.xml file, it causes them to be turned on and results in performance issues.

Solution 1

Add the SQL loggers or log configuration to the log-config.xml file:

Create a backup of the existing log-config.xml file ( ..\<ePO_Installation_folder>\Server\Conf\Orion\log-config.xml).
Stop the ePO services:
1. Click Start, Run, type services.msc, and click OK.
2. Right-click each of the following services and click Stop:
  
  McAfee ePolicy Orchestrator 5.x Application Server
  McAfee ePolicy Orchestrator 5.x Event Parser
  McAfee ePolicy Orchestrator 5.x Server
Add the following log configuration. You can add it anywhere in the log-config.xml file, as long as you don't add it to the middle of another logger. In other words, choose a blank line, press Enter to insert a carriage return, paste it in, and then press Enter again to insert another carriage return. For an example of the placement of this additional configuration, see the log-config.xml file in the "Attachment" section.





<logger name="jdbc.audit">

<level value="off"/>

</logger>



<logger name="jdbc.resultset">

<level value="off"/>

</logger>



<logger name="jdbc.sqlonly">

<level value="off"/>

</logger>



<logger name="jdbc.sqltiming">

<level value="off"/>

</logger>



<logger name="jdbc.connection">

<level value="off"/>

</logger>
Start the ePO services:
1. Click Start, Run, type services.msc, and click OK.
2. Right-click each of the following services and click Start:
  
  McAfee ePolicy Orchestrator 5.x Application Server
  McAfee ePolicy Orchestrator 5.x Event Parser
  McAfee ePolicy Orchestrator 5.x Server
3. Close the services window.

Solution 2

Replace the log-config.xml file with the log-config.xml file in the "Attachment" section of this article. Correct the path statements, so that they sync with the ones of the ePO Server on which you're replacing the file:

Create a backup of the existing log-config.xml file (..\<ePO Installation directory>\Server\Conf\Orion\log-config.xml).
Stop the ePO services:
1. Click Start, Run, type services.msc, and click OK.
2. Right-click each of the following services and click Stop:
  
  McAfee ePolicy Orchestrator 5.x Application Server
  McAfee ePolicy Orchestrator 5.x Event Parser
  McAfee ePolicy Orchestrator 5.x Server
Replace the existing ..\<ePO Installation directory>\Server\Conf\Orion\log-config.xml on the ePO server using the log-config.xml file attached to this article.
Verify or correct the ePO paths listed in this configuration. They must match the current paths for the ePO installation on the server to which you're copying this file. The following are the path statements you must find in this file:

<appender class="org.apache.log4j.FileAppender" name="TOFILE">

<param name="File" value="C:/PROGRA~2/McAfee/EPOLIC~1/server/logs/orion.log"/>

<appender class="com.mcafee.orion.core.log.RollingFileAppender" name="ROLLING">

<param name="File" value="C:/PROGRA~2/McAfee/EPOLIC~1/server/logs/orion.log"/>
Start the ePO services:
1. Click Start, Run, type services.msc, and click OK.
2. Right-click each of the following services and click Start:
  
  McAfee ePolicy Orchestrator 5.x Application Server
  McAfee ePolicy Orchestrator 5.x Event Parser
  McAfee ePolicy Orchestrator 5.x Server

Attachment

log-config.xml
5K • < 1 minute @ broadband

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

Performance issues in ePolicy Orchestrator 5.x when debug logging is enabled

Environment

Problem

Cause

Solution 1

Solution 2

Attachment

Affected Products

Languages:

Title

Title

Knowledge Center

Performance issues in ePolicy Orchestrator 5.x when debug logging is enabled

Environment

Problem

Cause

Solution 1

Solution 2

Attachment

Affected Products

Languages:

Choose your region

Title

Title