Messages in the EM logs
[ERROR] [pool-19-thread-2] [Manager.AppMap.RESTFederate] Error when invoking internal controller.
...
Caused by: org.springframework.dao.DataAccessResourceFailureException: PreparedStatementCallback; SQL [SELECT v.vertex_name, v.vertex_id FROM appmap_filter f JOIN appmap_vertices v ON f.vertex_id = v.vertex_id and f.start_time = v.start_time]; ERROR: canceling statement due to user request; nested exception is org.postgresql.util.PSQLException: ERROR: canceling statement due to user request
...
Caused by: org.postgresql.util.PSQLException: ERROR: canceling statement due to user request
...
EM version 10.7 with HF60
Release 10.7.0.271 (Build 996001)
RHEL 7.8 VMware VM.
As explained by Dev , this error is caused by either a timeout in UI or by canceling in UI (user simply closed the browser).
The exception is quite common. ERROR: canceling statement due to user request; nested exception is org.postgresql.util.PSQLException: ERROR: canceling statement due to user request
The error message can be ignored. if want to remove or stop reporting these on the log,
Engineering suggests changing the following log4j config within the IntroscopeEnterpriseManager.properties file:
log4j.logger.Manager.AppMap=INFO,console,logfile
log4j.logger.Manager.AppMap.PublicApi=INFO,console,logfile
to
log4j.logger.Manager.AppMap=INFO,console
og4j.logger.Manager.AppMap.PublicApi=INFO,console
This will keep the errors from showing in the IntroscopeEnterpriseManager.log files that the log4j library itself writes to; but the errors will still be written to the console
(standout) which normally gets appended to em.log on Linux and EMService.log on Windows.
Note: it is NOT recommended, as it will stop reporting errors in the AppMap module.