Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
07-28-2020 08:57 AM
What property controls the limit causing this warning,
[AD Thread Pool-Global97] 28 Jul 2020 09:52:39,334 WARN BoundsEnforcer - BoundsEnforcer for collection com.singularity.ee.agent.util.bounded.collections.BoundedConcurrentHashMap with service name TransactionMonitoringService and property name BusinessTransactionRegistry-registeredBTInfos-limit has exceeded maximum size of 55 entries.
[AD Thread Pool-Global97] 28 Jul 2020 09:52:39,334 WARN BoundsEnforcer - BoundsEnforcer for collection com.singularity.ee.agent.util.bounded.collections.BoundedConcurrentHashMap with service name TransactionMonitoringService and property name BusinessTransactionRegistry-registeredTransactions-limit has exceeded maximum size of 55 entries.
07-28-2020 10:49 AM
Hi @Shane.Samuelson,
Thanks for asking your question on the community. I see you also submitted a support ticket about this question.
If you get any valuable information from Support can you please share those results back on this post. This helps drive knowledge sharing across the community.
Thanks,
Ryan, AppDynamics Community Manager
12-18-2020 09:46 AM - last edited on 12-18-2020 10:44 AM by Ryan.Paredez
I too see a similar error message in the app logs, it would be great if someone posts the solution, even though there are support tickets opened.
[http-nio-8080-exec-11] 18 Dec 2020 00:19:37,772 WARN BoundsEnforcer - BoundsEnforcer for collection com.singularity.ee.agent.util.bounded.collections.BoundedConcurrentReferenceHashMap with service name TransactionMonitoringService and property name SqlCacheHolder-connectionVsZosSSID-limit has exceeded maximum size of 550 entries.
[http-nio-8080-exec-12] 18 Dec 2020 00:21:51,853 WARN BoundsEnforcer - BoundsEnforcer for collection com.singularity.ee.agent.util.bounded.collections.BoundedConcurrentReferenceHashMap with service name TransactionMonitoringService and property name SqlCacheHolder-connectionVsURL-limit has exceeded maximum size of 550 entries.
[http-nio-8080-exec-12] 18 Dec 2020 00:21:51,853 WARN BoundsEnforcer - BoundsEnforcer for collection com.singularity.ee.agent.util.bounded.collections.BoundedConcurrentReferenceHashMap with service name TransactionMonitoringService and property name SqlCacheHolder-connectionVsZosSSID-limit has exceeded maximum size of 550 entries.
01-09-2021 11:18 PM
In the logs shared by Shane and Karthik, both are just warnings which can be ignored.
In Shane's shared logs the BT count per node has exceeded the limit, and in Karthik shared logs it has got more sql calls than excepted and logged a message stating that it has reached limit.
09-13-2021 04:14 AM - last edited on 09-13-2021 10:02 AM by Ryan.Paredez
WARN BoundsEnforcer - BoundsEnforcer for collection com.singularity.ee.agent.util.bounded.collections.BoundedConcurrentReferenceHashMap with service name TransactionMonitoringService and property name SqlCacheHolder-connectionVsZosSSID-limit has exceeded maximum size of 550 entries.
The warning message cannot be ignored as the agent stopped reporting and caused a false Alert to the Support team for an application being monitored.
There was an escalation and we need to ensure that the Agent reports seamlessly without loss of monitoring data.
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form