Matty wrote: > > I am not 100% sure what the PID was, but I am certain there were no > Java processes running (at least according to ps). After I rebooted > the server, everything worked flawlessly. Unless anyone has any ideas, > I will open up a ticket with Sun support. This appears to be some sort > of bug. > The hotspot probes you referenced aren't tied to the 'java' executable. They're created when the 'libjvm.so' library is loaded (they are traditional USDT probes in that library). The 'java' executable isn't the only thing that loads libjvm.so. So not having 'ps' list a 'java' process, while dtrace still shows some 'hotspot*' probes doesn't necessarily indicate a problem. Your reboot may have fixed things because it terminated some other unrelated process that may have loaded libjvm.so (perhaps a browser?)
Just make sure to take a close look at the pid of the java process you're starting (and stopping), and make sure that the hotspot<pid> provider of the leftover probes matches that pid. What were you doing that caused this situation to occur? -- - Keith _______________________________________________ dtrace-discuss mailing list [email protected]
