Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #30258 > unrolled thread

VM-inspection on AIX (not oracle's java there)

Back to article view | Back to comp.lang.java.programmer

Contents

  VM-inspection on AIX (not oracle's java there) Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-10-30 18:39 +0000
    Re: VM-inspection on AIX (not oracle's java there) Lothar Kimmeringer <news200709@kimmeringer.de> - 2014-10-30 22:58 +0100
      Re: VM-inspection on AIX (not oracle's java there) Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-10-30 23:55 +0000

#30258 — VM-inspection on AIX (not oracle's java there)

Being used to Oracle's jvisualvm,jstack and other tools, I feel quite
blindfolded on that AIX machine, where these tools just don't exist in
the $JAVA_HOME/bin directory. (Since there does exist a "jre" subdir
of $JAVA_HOME, I'm positive that it really is a jdk and not just a jre)

Does anyone know *SPECIFICALLY for IBM's Java on AIX* how I could (e.g.)
get the stack-traces of all currently running threads of a running JVM
given by the VM's pid?

[toc] | [next] | [standalone]

#30259

Andreas Leitgeb wrote:

> Does anyone know *SPECIFICALLY for IBM's Java on AIX* how I could (e.g.)
> get the stack-traces of all currently running threads of a running JVM
> given by the VM's pid?

kill -3 pid
maybe? At least that's how you did it before the tools you
mentioned were available e.g. on Linux.


Cheers, Lothar
-- 
Lothar Kimmeringer                E-Mail: spamfang@kimmeringer.de
               PGP-encrypted mails preferred (Key-ID: 0x8BC3CD81)

Always remember: The answer is forty-two, there can only be wrong
                 questions!

[toc] | [prev] | [next] | [standalone]

#30260

Lothar Kimmeringer <news200709@kimmeringer.de> wrote:
> Andreas Leitgeb wrote:
>> Does anyone know *SPECIFICALLY for IBM's Java on AIX* how I could (e.g.)
>> get the stack-traces of all currently running threads of a running JVM
>> given by the VM's pid?
> kill -3 pid
> maybe? At least that's how you did it before the tools you
> mentioned were available e.g. on Linux.

Thanks, that helped!  At first I feared that it might just kill the
process and leave a core file, but the process actually survived it,
and instead of the expected normal core file, it produced a text file
with all the information I wanted (and much much more) in it.

Thanks, that'll definitely help me next time my app misbehaves :-)

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.java.programmer

csiph-web