Review Request: 7196045 Possible JVM deadlock in ThreadTimesClosure

[serguei.spitsyn at oracle.com]

Hi Kevin,

Looks good.

Thanks,
Serguei

On 9/4/12 3:35 PM, Kevin Walls wrote:
> Hi,
>
> I'd like to get this reviewed, it's a deadlock that can happen due to 
> Java objects being allocated while holding Threads_lock.
>
> We need to collect just the characters of the thread names while 
> holding the lock, and create the String objects when it's released.  
> You do need to hit the (non-public) HotspotInternal MBean very rapidly 
> to trigger this reliably, but there's a small chance the deadlock 
> could happen when it's called by the tool that is meant to call it.
>
> http://cr.openjdk.java.net/~kevinw/7196045/webrev.01/
>
> Thanks!
> Kevin
>