× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Looking at the Java Diagnostics Guide for JVM 5, it looks like you can find
the process id of the job by looking in the joblog for the JVAB56D message
which has the process id in parentheses at the tail end of the message.
Then, go into STRQSH and type

kill -QUIT process-id

HTH,
Gary

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-
bounces@xxxxxxxxxxxx] On Behalf Of James Perkins
Sent: Monday, August 10, 2009 2:14 PM
To: Java Programming on and around the iSeries / AS400
Subject: Re: Dump stack trace of running JVM?

Thorbjoern,
Have you found a good one for the 32-Bit JVM?

I thought I remembered you posting some time back something about using
JConsole. Did you ever get it to work?

--
James R. Perkins
http://twitter.com/the_jamezp


On Mon, Aug 10, 2009 at 13:26, Thorbjoern Ravn Andersen
<ravn@xxxxxxxxxx>wrote:For the Classic JVM. The mechanism is
different for the new one.


--
Thorbjørn Ravn Andersen "...plus... Tubular Bells!"


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.