ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Error querying for correlated traces
Article ID: 132541
Updated On:
Products
CA Application Performance Management Agent (APM / Wily / Introscope)
INTROSCOPE
Issue/Introduction
DX APM 10.3 - several times a day, sees the following message in IntroscopeEnterpriseManager.log.
[WARN] [MOM Collection Buffer consumer thread.] [Manager] Error querying for correlated traces
This is only a WARN and not showing any impact. Still like to know what is going on and how to fix this.
[WARN] [MOM Collection Buffer consumer thread.] [Manager] Error querying for correlated traces
This is only a WARN and not showing any impact. Still like to know what is going on and how to fix this.
Cause
First, this is not a bug.
Warning messages happening when EM gets shut down with a kill signal or crashes has a good chance of seeing issues with the traces. And this seems to be an issue with the traces index directory
If the EM crashes after 'Error querying for correlated traces' is repeatedly displayed.
Then, it is the timing when the index of the trace file is damaged and can not be accessed, but the specific timing is not known.
It can't reload older transactions either in the "traces" tab in Investigator, or by the Historical Event Viewer.
At that time, the trace file is corrupted or just before destruction, but the EM does not crash and the following message appears in the log file.
[WARN] [MOM Collection Buffer consumer thread.] [Manager] Error querying for correlated traces
[ERROR] [MOM Collection Buffer consumer thread.] [Manager] Error querying for correlated traces
It is considered as a sign of EM crashing.
Warning messages happening when EM gets shut down with a kill signal or crashes has a good chance of seeing issues with the traces. And this seems to be an issue with the traces index directory
If the EM crashes after 'Error querying for correlated traces' is repeatedly displayed.
Then, it is the timing when the index of the trace file is damaged and can not be accessed, but the specific timing is not known.
It can't reload older transactions either in the "traces" tab in Investigator, or by the Historical Event Viewer.
At that time, the trace file is corrupted or just before destruction, but the EM does not crash and the following message appears in the log file.
[WARN] [MOM Collection Buffer consumer thread.] [Manager] Error querying for correlated traces
[ERROR] [MOM Collection Buffer consumer thread.] [Manager] Error querying for correlated traces
It is considered as a sign of EM crashing.
Environment
CA APM 10.x
Resolution
If wanting to stop the warning message leading to a EM crash, start a traces index directory.
Please backup and remove directory "../traces/index" and restart the EM to regenerate the index directory.
Please backup and remove directory "../traces/index" and restart the EM to regenerate the index directory.
Feedback
Yes
No
Powered by
