PQ71854: INFOCENTER DIRECTIONS FOR CREATING HEAP DUMP ARE OUT OF DATE | |||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||
APAR status Closed as documentation error. Error description Section on using JVM Arguments, 6.6.36.0: JVM properties, references using HPROF arguments. These appear to not be applicable anymore, since the Heap dump is configured with the following environment variables that are set before startupServer is invoked from the command line: . Here are the recommended settings: set IBM_HEAPDUMP=true set IBM_HEAPDUMP_OUTOFMEMORY=true set IBM_HEAPDUMPDIR=c:\jvmdumpdir set IBM_JAVACOREDIR=c:\jvmdumpdir set _JVM_THREAD_DUMP_BUFFER_SIZE=419430400 After setting the above environment variables run the application with verbosegc.(i.e java -verbosegc) Out of memory or a JVM crash should produce your heap dump. . Note: The path and file information in this example is for Windows. This is applicable to all IBM JDKs The JTC (Java Technology Center) has a paper on the JDK used by WebSphere 4.0 (JDK 1.3.1). Chapther 12 covers enabling a heap dump: http://eureka.hursley.ibm.com/ServiceInfo/ServiceProcess /JTC0D100.pdf . Other hints and tips: If you want a heap dump, but are not getting the out of memory condition or a crash, you can use <ctrl><break> in the window where you start WebSphere via the command line (e.g. startupServer.sh) .Local fix not applicableProblem summary **************************************************************** * USERS AFFECTED: Users of WebSphere Application Server, * * Version 4.0.6 InfoCenter. * **************************************************************** * PROBLEM DESCRIPTION: After Version 4.0.6, HProf arguments * * entered for JVM properties no longer * * apply. * * InfoCenter article: "Additional * * profiler arguments to use * * when Run HProfs is used" needs to be * * updated to reflect this. * **************************************************************** * RECOMMENDATION: * **************************************************************** Hprof Arguments Additional profiler arguments to use when Run HProfs is used. Users of Version 4.0.6 and beyond: HProf arguments are no longer applicable because the Heap dump is configured with environment variables such as those below that are set before you run startupServer from a command line. Recommended settings include: set IBM_HEAPDUMP=true set IBM_HEAPDUMP_OUTOFMEMORY=true set IBM_HEAPDUMPDIR=c:\jvmdumpdir set IBM_JAVACOREDIR=c:\jvmdumpdir set _JVM_THREAD_DUMP_BUFFER_SIZE=419430400 After setting the above environment variables, run the application with verbosegc (for example, java -verbosegc). An out of memory condition or a JVM crash should produce a heap dump. Note that the above path and file information is for Windows platforms. However, the instructions apply to all IBM JDKs. Further, if you want a heap dump, but are not getting the out of memory condition or a crash, you can use Ctrl-Break in the window where you start WebSphere Application Server from a startupServer command.Problem conclusion Close this APAR as a documentation change. The updated information will appear on the external site after 05/18/2003.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ71854
IBM Group: Software Group
Modified date: Jun 3, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.