Profiler root methods explanation

  • From: Herkules <herkule9s@...>
  • To: "users@..." <users@...>
  • Subject: Profiler root methods explanation
  • Date: Wed, 18 Dec 2013 07:40:11 -0800 (PST)
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=NP9XxaOM8IsM2Vh+23fjQgqq3PdRe6lTF3EfSiBW1up+ye4E1VCAYMNDl1GKccTC3P+POeAcS1dtG95CJMjyBonccDr8+h6mbXdCLW3n3TrWQChNysr33NFh9acER16nMNjZ+u0dSCsUUB2QWVVDZi2p+OOHPBmgwofJuh0lVA0=;

Hi

I am familiar with what root methods are, at least I hope :-) However they 
doesn't work as expected. Assume the following classes, each with one static 
public methods:

cz.someone.profiler.root.Root - contains main method and calls Inter class

cz.someone.profiler.inter.Inter - calls Target class method in a cycle

cz.someone.profiler.target.Target - single static method that sleeps some time


My profiler settings:

start profiling from classes: cz.someone.profiler.inter.Inter
profile new runnables: not ticked
profile only classes: cz.someone.profiler.target.Target

When I stop (on breakpoint) my application in main method and hit CPU 
profiling, VisualVM says that no methods were instrumented and when the 
program continues with call to Inter method, no profiling results are shown. 
I assume that profiler is able to grab and instrument new loaded classes, but 
this doesn't work.

BTW, this is VisualVM from JDK 1.7 Update 46

Thank you for your support, Jan

Profiler root methods explanation

Herkules 12/18/2013

Re: Profiler root methods explanation

Tomas Hurka 12/20/2013

Re: Profiler root methods explanation

Herkules 12/27/2013
Terms of Use; Privacy Policy; Copyright ©2013-2015 (revision 20150226.965aeb8)
 
 
Close
loading
Please Confirm
Close