On Jan 4, 2008 8:49 AM, Keith McGuigan <[EMAIL PROTECTED]> wrote: > 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?)
I am 100% certain that the 'java' executable is the only thing that makes use of libjvm.so on this specific server. Since my script didn't work prior to me rebooting the box, and it started working after I rebooted the box, it would appear to me that some type of bug reared its head. > 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? We have bumped into a couple bugs in the JVM CMS collector that cause our Java processes to fail hard. This is the only thing I can think of that might lead to this behavior. Thanks for the feedback, - Ryan -- UNIX Administrator http://prefetch.net _______________________________________________ dtrace-discuss mailing list [email protected]
