Understanding "could not execute query" message

Document ID : KB000031674
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:  

 

- We have the following constant problem in the MOM LOG, we need help to understand and solve it.

[ERROR] [APM Model WebServices 9] [Manager] Hibernate operation: could not execute query; SQL [select agent0_.id as id0_, agent0_.name as name0_, agent0_.process_name as process3_0_, agent0_.host_name as host4_0_, agent0_.fully_qualified_host_name as fully5_0_, agent0_.creation_date as creation6_0_, agent0_.update_date as update7_0_, agent0_.user_name as user8_0_ from apm_agent agent0_ where agent0_.id not in  (select distinct vertex1_.agent_id from apm_vertex vertex1_ where vertex1_.id in (select distinct edge2_.head_vertex_id from apm_edge edge2_ where update_date<? or update_date>? and (vertex1_.agent_id is not null)) or vertex1_.id in (select distinct edge3_.tail_vertex_id from apm_edge edge3_ where update_date<? or update_date>? and (vertex1_.agent_id is not null)))]; ERROR: canceling statement due to statement timeout; nested exception is org.postgresql.util.PSQLException: ERROR: canceling statement due to statement timeout

 

Cause:

 

It looks like your Databse server rudely disconnected application connection while it was reading some sort of resultset.This error most likely occurs in applications that use a database connections pool. When the application checked out a connection that has been timed out or has been staled, and used it to connect to the database, this error occurs. Also, it can be due Prune feature enabled at Collectors side.

 

Answer: 

 

-This message can be suppressed by disabling Prune feature at Collectors side. To do so, open your "IntroscopeEnterpriseManager.properties" file under EM_Home >> CONFIG folder and set as below:


introscope.apm.pruning.enabled=false


-Collector restart is needed.

 

 

Additional Information:

 

-This message does not bring any lack of functionality to the product or to the application.
-Exist a workaround for Oracle Database, not for Postgres so far. For Oracle please see:

http://www.oracleracexpert.com/2013/02/java-sql-exception-no-more-data-to-read.html