Why does jProfiler show Unsafe.park / unpark as using processor cycles?

Question

We start the service using quite a few ExecutorServices.

When profiling a service using jProfiler 7.1 (fetch, Runnable), we can see that sun.misc.Unsafe.park + unpark is currently a call that uses most of the processor time at the access point.

http://i.stack.imgur.com/wT2Cj.jpg

This is puzzling.

Park and non-paint should be blocked, therefore, do not use any processor cycles (or at least a small amount). Is this some kind of error from jprofiler (i.e. not detecting it because it is in the sun.misc package?) Or is there something wrong with our use of the ExecutorService infrastructure?

Answer 1

This is fixed in JProfiler 7.1.1. This can happen when you disconnect and connect to a profiled JVM.