CEM: Limit exceeded adding new components to Discovered Transactions
Article ID: 41780
Updated On:
Products
Issue/Introduction
Issue/Problem/Symptoms:
Seeing an issue with CA CEM when trying to use the transaction discovery, I get the following message: "Limit exceeded adding new components to Discovered Transactions."
Environment:
Linux. APM 10.x.
Cause:
By default, up to 50 non-identifying components can be discovered per transaction. After 50 have been discovered, the oldest ones are deleted to allow new ones to be added. A CA CEM event called "Limit" exceeded adding new components is logged each time a new non-identifying component replaces an old one.
Resolution/Workaround:
To change the maximum number of non-identifying components, edit the Autogen.Max.NonIdentifying.Components property in tess-customer.properties.
*tess-customer.properties file should be created as following:
1. Locate the file:
<EM_Home>/config/tess-default.properties
2. Create a copy of the tess-default.properties file in the same directory, and name it tess-customer.properties.
3. Modify the created tess-customer.properties file, adding only the properties needed to modify for your CA CEM environment.
a. Edit this new properties file.
For example, using the vi editor:
vi tess-customer.properties
Important! The tess-customer.properties file should contain only those properties with values that differ from the CA CEM system defaults.
If you leave all the properties in your tess-customer.properties file, then system upgrades might not take advantage of future system performance or tuning updates to the properties.
b. Save the tess-customer.properties file.
4. Copy the tess-customer.properties file to all the Enterprise Managers in the cluster.
5. Restart each Enterprise Manager in the cluster.
Additional Information:
Automatically Discovering Components
*Modifying the tess-default.properties Property Default File
Environment
Component:
Feedback
