Foglight Weblogic admin server blocked threads (4313120)

Admin server agent has a lot of BLOCKED threads, all blocked by modelfilters trying to get a new session. Threaddumps collected at time of issue show

 "com.quest.pas.agent.plugin.periodic.jmx.WebLogic9MetricsCollector startRecording 1390315723322" daemon prio=3 tid=0x0000000106572800 nid=0x1de79 waiting for monitor entry [0xffffffff401ff000]
   java.lang.Thread.State: BLOCKED (on object monitor)
 at com.quest.pas.agent.plugin.periodic.jmx.AbstractJmxMetricsCollector$1.run(AbstractJmxMetricsCollector.java:159)
 - waiting to lock <0x0000000748890668> (a com.quest.pas.agent.plugin.periodic.jmx.WebLogic9MetricsCollector)
 at java.lang.Thread.run(Thread.java:744)
"com.quest.pas.agent.plugin.periodic.jmx.WebLogic9MetricsCollector startRecording 1390315720014" daemon prio=3 tid=0x000000010599c000 nid=0x1de68 waiting for monitor entry [0xffffffff403ff000]
   java.lang.Thread.State: BLOCKED (on object monitor)
 at com.quest.pas.agent.plugin.periodic.jmx.AbstractJmxMetricsCollector$1.run(AbstractJmxMetricsCollector.java:159)
 - waiting to lock <0x0000000748d08c50> (a com.quest.pas.agent.plugin.periodic.jmx.WebLogic9MetricsCollector)
 at java.lang.Thread.run(Thread.java:744)

If you are on Java agent 5.8.2, please apply the patch attached

Patch for this issue is now attached. It is the agent jar file...Build number to use is: "5.8.2-20130709-1307" 

To install the patch:
1. Update config file on the FMS to include the build number of the patch
a. FMS Console: Administration > Agents > Agent Properties > JavaEE > Advanced > nexus_compatible-builds.config
b. Add the patch build number "5.8.2-20130709-1307" to the existing list.
c. Save the config file.
2. On a particular monitored host, stop all instrumented weblogic servers.
3. Back up JavaEE_Agent_Home/lib/performasure-agent.jar outside the JEE agent install folder.
4. Copy the patched jar file (attached to email) to JavaEE_Agent_Home/lib/ directory. Rename the patch to performasure-agent.jar before using it.
5.. Restart all instrumented weblogic servers.
6. Repeat steps 2-5 on all monitored hosts which have this issue.

If you are on 5.9.x version,please upgrade your cartridge and agent to 5.9.3.2 or above as this issue is fixed in 5.9.3.2 and above agent versions