search

konradreiche / java-concurrency-profiler

A Java profiler with emphasis on concurrent program information.
Other
6 stars 1 forks source link

Fix Monitor Data Collection #31

Closed konradreiche closed 13 years ago

konradreiche commented 13 years ago

Currently every monitor events triggers agent messages which include a monitor lock, respectively its identification and statistics about it. When entering a synchronized block this is valid. However these data should not be send when wait(), notify() or notifyAll() is called upon a monitor lock, because this leads to too much monitor locks in the end.

Since wait(), notify() and notifyAll() calls are usable to get the class type of the monitor lock, an intermediate solution should be found in order to get meaningful data.

konradreiche commented 13 years ago

The number of monitor locks shown in the Lock tab was valid. In addition to this now the name to the monitor locks class is shown.