Performance issues in ePolicy Orchestrator 5.x when debug logging is enabled
Last Modified: 2023-07-20 10:37:43 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
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 EnvironmentePolicy 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 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: [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 CauseePO 5.x has added logging capability to include detailed SQL logging to the
The configuration for this extra logging must be included in the Solution 1 Add the SQL loggers or log configuration to the
Solution 2Replace the
AttachmentAffected ProductsLanguages:This article is available in the following languages: |
|