1The following are examples of running j_stat.d.
2
3j_stat.d shows you the number of events per second that have happened since
4the last line output.  The default interval is 1 second, but you can specify
5other intervals as arguments to the script.
6
7This shows the j_stat.d script reflecting the Code/Ruby/Func_abc script.  
8
9# j_stat.d
10TIME                 EXEC/s THREAD/s METHOD/s OBJNEW/s  CLOAD/s EXCP/s   GC/s
112007 Sep 24 04:00:34      0        0        0        0        0      0      0
122007 Sep 24 04:00:35      2        6    11660     5306      318     41      0
132007 Sep 24 04:00:36      0        0      124        4        0      2      0
142007 Sep 24 04:00:37      0        0      124        4        0      2      0
152007 Sep 24 04:00:38      0        0      123       75        9      1      0
162007 Sep 24 04:00:39      0        0        0        0        0      0      0
172007 Sep 24 04:00:40      0        0        0        0        0      0      0
18^C
19
20Here we can see that at 2007 Sep 24 04:00:35 there were 2 Java programs
21executed, (this number will include those without Java provider support),
22there were 6 threads created, 11,660 methods called, 5306 new objects created,
23318 class loads, 41 exceptions raised and no garbage collects. 
24
25The numbers are per second counts for the interval specified. The default 
26interval is 1 second.
27
28If you see a count in "EXECS" but not in the other columns, then your Java 
29software is probably not running with the DTrace hotspot provider.
30
31If you see counts in "CLOAD" but not in "METHODS", then you Java software 
32probably isn't running with "+ExtendedDTraceProbes".
33
34