Java app agent warnings

[Shane.Samuelson]

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.

[Ryan.Paredez]

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.

[karthik.Athisamy]

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.

cc @Shane.Samuelson 

[Nawaz Ali.Mohammad]

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.

[Gaurav.Jakharia]

Hi @Nawaz Ali.Mohammad 

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.

[Michael.Green]

Can we please get an update to this WARN issued....exceeded maximum size of 550 entries, and how to resolve?
Thank you!

[Sunil.Agarwal]

@Michael.Green ,  The internal collection's default limit is 550 items, however it can be raised using the node property "SqlCacheHolder-connectionVsZosSSID-limit / SqlCacheHolder-connectionVsURL-limit" and the warning messages will no longer appear.

Add below Node Property: 

property name: SqlCacheHolder-connectionVsZosSSID-limit
description: SqlCacheHolder-connectionVsZosSSID-limit
type: Integer
Value: (default is 550) increase it to 800 or 900

property name: SqlCacheHolder-connectionVsURL-limit
description: SqlCacheHolder-connectionVsURL-limit
type: Integer
Value: (default is 550) increase it to 800 or 900

Doc link to add/edit node property: https://docs.appdynamics.com/appd/23.x/latest/en/application-monitoring/administer-app-server-agents... 

Please reset all problematic tier nodes from the controller user interface after setting the node properties. Please see the document link:  https://docs.appdynamics.com/appd/23.x/latest/en/application-monitoring/administer-app-server-agent...

The application's operation shouldn't be affected by these messages, but you shouldn't see them in the logs either after adding these properties and resetting the agent. If the problem persists, please start a support ticket and attach the debug agent logs that were generated by the problematic node during the problematic time span.