Alternative for generating Javacores in Windows
 Technote (troubleshooting)
 
Problem(Abstract)
When debugging JVM™ issues in IBM® WebSphere® Embedded Servers, it is often difficult to generate a Javacore. This is because of the limited tools available. This technote documents how a Javacore can be generated from a DOS window command line.
 
Cause
Problems in an embedded Application Server that require the generation of a Javacore as part of problem resolution.
 
Resolving the problem
Generating a Javacore from a Windows® command prompt:
  1. Open a Windows command prompt.
  2. Go to the install_root\AppServer\bin folder.
  3. Issue a command as follows for the appropriate server (in this example, server1):
    1. startServer server1 -script
    2. The output of this command will be a start_server1.bat file
  4. Stop server1, then clean out the logs, logs/server1, and logs/ffdc folders.
  5. At the Windows command line, type:
    1. start_server1
    2. This starts server1, but you retain control in the command prompt window.
  6. To generate a Javacore, press <Ctrl> + <Break> keys simultaneously. The following commands are generated:

    JVMDG217: Dump Handler is Processing a Signal - Please Wait.
    JVMDG303: JVM Requesting Java core file
    JVMDG304: Java core file written to C:\WebSphere5\AppServer\bin\javacore......txt
    JVMDG215: Dump Handler has Processed Dump Signal 21.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java SDK
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1163860
IBM Group: Software Group
Modified date: Feb 10, 2005