com.wily.introscope.agent.probe.net.ManagedDatagramSocket monitor contention

Solution Unverified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform
  • CA Wily Introscope

Issue

  • AJP threads blocked waiting for a com.wily.introscope.agent.probe.net.ManagedDatagramSocket monitor owned by another ajp thread.
  • Blocking threads look like this:
"ajp-10.171.161.37-8009-1" daemon prio=10 tid=0x0000000048e34800 nid=0x18b2 waiting for monitor entry [0x00002b8b87ea5000]
   java.lang.Thread.State: BLOCKED (on object monitor)
    at java.net.DatagramSocket.setSoTimeout(DatagramSocket.java:795)
    - waiting to lock <0x0000000761ad8608> (a com.wily.introscope.agent.probe.net.ManagedDatagramSocket)
    at com.rsa.authagent.authapi.authmsg.AUTHa0.a
    at com.rsa.authagent.authapi.authmsg.AUTHa2.b
    at com.rsa.authagent.authapi.authmsg.AUTHa2.a
...

Resolution

It seems that Wily is causing contention. Monitoring comes at a cost and can cause performance issues due to excessive monitoring. Get input from CA support how to configure Wily to avoid the contention.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments