kjkoster
08-12-2009, 12:34
Dear All,
Occasionally Java-monitor releases a new version of its probe. We strive to keep supporting all live versions of our probes, to keep the amount work you have on maintaining Java-monitor to a minimum.
Today we have seen a few instances of an old problem return. This is an edge case where in some situations you'd get more than one JVM thinking they are the same JVM on Java-monitor. This causes the data set for your account to grow rapidly and consequently it will make the graphs appear to be slow.
This is caused by a bug in an old version of our probes and should be fixed once you deploy the latest version. To be precise, the fixed probe was released on 7 October 2009 (http://java-monitor.com/forum/showthread.php?p=1583#post1583).
Please update your probe by clicking on the Download your probe (http://java-monitor.com/lemongrass/java-monitor-probe.zip) link in your host overview page.
Kees Jan
Occasionally Java-monitor releases a new version of its probe. We strive to keep supporting all live versions of our probes, to keep the amount work you have on maintaining Java-monitor to a minimum.
Today we have seen a few instances of an old problem return. This is an edge case where in some situations you'd get more than one JVM thinking they are the same JVM on Java-monitor. This causes the data set for your account to grow rapidly and consequently it will make the graphs appear to be slow.
This is caused by a bug in an old version of our probes and should be fixed once you deploy the latest version. To be precise, the fixed probe was released on 7 October 2009 (http://java-monitor.com/forum/showthread.php?p=1583#post1583).
Please update your probe by clicking on the Download your probe (http://java-monitor.com/lemongrass/java-monitor-probe.zip) link in your host overview page.
Kees Jan