Hi Buddi, Are you using JStack ? By default, java thread dump does not record lock owners for locks. If you use jstack, use "-l" parameter as well [1]. (eg: jstack -l "pid" ). This params records lock owner information only for synchronized blocks. Which is usefull to detect possible deadlocks.
[1] - http://docs.oracle.com/javase/7/docs/technotes/tools/share/jstack.html Thanks, Hasitha. On Tue, Dec 23, 2014 at 6:02 PM, Buddhi Senarathna <[email protected]> wrote: > hi all, > > I'm working on creating a tool to take thread dumps and analyze thread > info as carbon test utility. > > to do that i have to cover these task. > > 1. access to a process remotely using process id. > 2. get thread dump of that remote process . > 3. expose necessary informations of thread dump using some methods in > realtime. > 4. give a method to write thread dump into a file. > > > Note: currently 1st and 2nd tasks are completed. > > thank you. > > > -- > > *Buddhi Chathuranga Senarathna* > > > *InternWSO2, Inc. * > *Mob: +94 755 446 685 <%2B94%20755%20446%20685>* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Hasitha Aravinda, Software Engineer, WSO2 Inc. Email: [email protected] Mobile: +94 71 8 210 200
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
