Re: Blocking in WeakIdentityMap
Mark Brouwer <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
Patrick Wright wrote: > Hi all > > This problem--blocking threads waiting on WeakIdentityMap--appears to > have been a side-effect of profiling; my apologies. The problem only > shows up when the profiler is enabled. The trace for the blocking > thread (that owns the monitor) is below. I was running the profiler in > "full application mode", which for most of the app was not a problem, > but looks like in this case it caused the profiler to instrument > WeakIdentityMap (possibly as a hotspot?) and that led to timing > problems. I set the profiler to ignore the class and the block has > disappeared. FYI this is a nice article about java SE 6 and DTrace http://www.devx.com/Java/Article/33943 . It will enable you to find problems (also in production) for which in general profilers are too intrusive. -- Mark -------------------------------------------------------------------------- Getting Started: http://www.jini.org/wiki/Category:Getting_Started Community Web Site: http://jini.org jini-users Archive: http://archives.java.sun.com/archives/jini-users.html Unsubscribing: email "signoff JINI-USERS" to [email protected]