Getting thread dump of JWS application

Hi,
I know this was discussed a few times before, but I still have no solution for my problem.
I have a JWS GUI application that deadlocks sometimes (Windows 98). So I want to get the thread dump to analyze the deadlock. In Java Web Start I changed the java command from javaw.exe to java.exe, so I get a dos box. When I press CTRL-BREAK inside the dos box, I get the thread dump but because the dos box just shows a few lines I only get the last lines of the dump. Under Windows 98 I cannot resize the dos box.
Is there a way to redirect the output of the dos box to a file? Or is there another way to get the thread dump of a JWS application?
Thanks in advance
Markus

Here is 50% of the solution. To generate a thread dump programatically, you need to call JVM_DumpAllStacks through JNI. You need to link in "jvm.lib".
JNIEXPORT void JNICALL JVM_DumpAllStacks(JNIEnv *env, jclass unused);
JNIEXPORT void JNICALL Java_Services_generateThreadDump(JNIEnv *env, jobject thisObject) {
     // Produce a thread dump to VM standard out
     JVM_DumpAllStacks( env, NULL );
}Here is the java class that calls the JVM_DumpAllStacks method through JNI.
public class Services {
      * Send a message to the VM, forcing it to create a thread dump. The resulting
      * thread dump will be sent to stdout. Note that this is the VM's stdout, not
      * necessarily System.out.
     public static native void generateThreadDump();
}When you reach the point in your code that you want to generate a thread dump, close stdout and reopen it with the thread dump destination stream. Next, call the JNI method. This will send the thread dump to stdout.
     // Replace stdout with a file output stream
     System.out.close();
     System.setOut( new PrintStream( new FileOutputStream( "stdout.log" )));
     // Generate thread dump
     Services.generateThreadDump();Why is this only 50% of the solution ? Because this works beautifully for regular applications but it does NOT work for WebStart applications. Not sure what is happening here, but so far I have not managed to get any thread dump in a file from an application that has been fired up through WebStart. Note that I CAN get a thread dump in a file if I fire up the same code from the command line.

Similar Messages

  • Program hangs, can't get thread dump

    Hello
    I have a Java program which sometimes works OK untill the very end, but sometimes just hangs in a random moment and doesn't react to Ctrl+C or Ctrl+Break. Process doesn't use CPU, so I guess it isn't something like infinite loop (I actually cannot think of places in my program where this kind of loop may occur). I tried to get thread dump to see if there are any deadlocks, but Ctrl+Break doesn't work and jstack doesn't work also (I've read that there is -F option, but it isn't available on Windows). Also I tried to connect to a process with Java Visual VM - doesn't help too (just says 'Connecting...' forever).
    What else can I do to find out what's going on in my programm and fix it?
    I tried to run it with JDK 1.6.0_07 and 1.6.0_16. I'm using Windows Vista Enterprise SP1, 64-bit.
    Thanks in advance, Yulia.
    Edited by: Yulia_Dubinina on Oct 26, 2009 11:58 PM
    Edited by: Yulia_Dubinina on Oct 27, 2009 12:13 AM

    Yulia_Dubinina wrote:
    Yesterday I tried to start my program, connect with Java Visual VM to it and see how threads visualisation will look like in a moment when program hangs. My programm died after about 50 min and all info which I was able to see was about this period of time (e.g. a timeline diagram stopped changing and the last time mark was 49:23), but Java Visual VM was still connected to a process. I tried to press Thread Dump button, it worked, but there was nothing 'criminal' on the dump it provided. So I guess maybe it's not actual thread dump, it's something that Java Visual VM was able to get before process hanged.
    I don't have much experience in resolving this kind of problems, so any advices will be great appreciated.
    Edited by: Yulia_Dubinina on Oct 27, 2009 2:14 PMTurn on verbose GC and see if you got lots and lots of full GC when the freeze happens. A full GC can take several minutes if you have a bad configuration (where e.g. memory has been paged out to disk)

  • Getting Thread Dump programitically ?

    Hi,
    Is there any way by which we can get the thread dump programatically?
    We are using Solaris OS and when we tried to get the thread dump using
    'kill -QUIT <pid of process>' the process(WebLogic) got crashed.
    So, please let me know how can we get the thread dump programatically.
    regards,
    Raghu

    There is a new static method for Thread called getAllStackTraces(). It is new for 1.5. See http://java.sun.com/j2se/1.5.0/docs/api/java/lang/Thread.html#getAllStackTraces()You can start with that.

  • How to get thread dump in case of out of memory error.

    Hi Team,
    In case of out of memory, heap dump can be generated using option '- XX:+HeapDumpOnOutOfMemoryError'. Is is possible to generate thread dump too using any option? Can it be done using option -XX:OnOutOfMemoryError="<cmd args>?
    Thanks in advance.
    Regards,
    Atul.

    Jay SenSharma wrote:
    Hi Mukul,
    Complete Steps can be Devided into 3-parts
    A). Configuring a Mail-Session
    B). Configuring WLDF Module
    C). Configuring Watch And Notification
    For detailed <A class=bodylinkwhite href="http://www.software-to-convert.com/divx-avi-conversion-software/divx-avi-to-h264-software.html"><FONT face=tahoma,verdana,sans-serif color=#000 size=1>steps</FONT></A> please refer to: <B><A class=jive-link-external href="http://jaysensharma.wordpress.com/2010/01/07/e-mail-notification-using-wldf/">http://jaysensharma.wordpress.com/2010/01/07/e-mail-notification-using-wldf/</A></B>
    <P>
    Thanks
    Jay SenSharma
    <B><A class=jive-link-external href="http://jaysensharma.wordpress.com">http://jaysensharma.wordpress.com</A> (WebLogic Wonders Are here)</B></P>
    It is just the solution for my problem, It's very useful.

  • Thread dump running Classic JVM(jdk 1.2.2)

    Hi,
    We get a thread dump while running our application. The application is in java/jsp running on apache-tomcat. The tomcat version is 3.2.1. Java version being used is:
    java version "1.2.2"
    Classic VM (build JDK-1.2.2-007, native threads, symcjit)
    Does anyone have any idea how to identify the reason for the thread dump? The application eventually hangs after the thread dump. Thanks in advance. Below is the dump:
    <pre>
    Full thread dump Classic VM (JDK-1.2.2_007, native threads):
    "Thread-34" (TID:0x5faa550, sys_thread_t:0x2f4158, state:CW, native ID:0xb9c) prio=5
    "Thread-33" (TID:0x5faa1d0, sys_thread_t:0x22092f98, state:CW, native ID:0xa54) prio=5
         at java.lang.Object.wait(Native Method)
         at org.apache.tomcat.util.ThreadPool$MonitorRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-32" (TID:0x5faa220, sys_thread_t:0x2207df88, state:R, native ID:0xb18) prio=5
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java, Compiled Code)
         at org.apache.tomcat.service.connector.TcpConnector.receiveFully(TcpConnector.java, Compiled Code)
         at org.apache.tomcat.service.connector.TcpConnector.receive(TcpConnector.java, Compiled Code)
         at org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection(Ajp13ConnectionHandler.java, Compiled Code)
         at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-31" (TID:0x5fa9e48, sys_thread_t:0x22080228, state:CW, native ID:0xb2c) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java, Compiled Code)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-30" (TID:0x5fa9e98, sys_thread_t:0x22080140, state:CW, native ID:0x908) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java, Compiled Code)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-29" (TID:0x5fa9ee8, sys_thread_t:0x2207e758, state:CW, native ID:0x74c) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java, Compiled Code)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-28" (TID:0x5fa9f38, sys_thread_t:0x22080518, state:R, native ID:0x2fc) prio=5
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:414)
         at java.net.ServerSocket.implAccept(ServerSocket.java:242)
         at java.net.ServerSocket.accept(ServerSocket.java:224)
         at org.apache.tomcat.service.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:286)
         at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-27" (TID:0x5fa9b58, sys_thread_t:0x2207ff00, state:CW, native ID:0xa7c) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-26" (TID:0x5fa9ba8, sys_thread_t:0x2207fd90, state:CW, native ID:0xa70) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-25" (TID:0x5fa9bf8, sys_thread_t:0x2207fb78, state:CW, native ID:0x4d4) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-24" (TID:0x5fa9ca0, sys_thread_t:0x2207f8f0, state:CW, native ID:0x7c8) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-23" (TID:0x5fa9c98, sys_thread_t:0x22055c18, state:CW, native ID:0xa60) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-22" (TID:0x5fa94a0, sys_thread_t:0x220556a0, state:CW, native ID:0x68c) prio=5
         at java.lang.Object.wait(Native Method)
         at org.apache.tomcat.util.ThreadPool$MonitorRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-21" (TID:0x5fa94f0, sys_thread_t:0x220555b8, state:R, native ID:0xb24) prio=5
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:414)
         at java.net.ServerSocket.implAccept(ServerSocket.java:242)
         at java.net.ServerSocket.accept(ServerSocket.java:224)
         at org.apache.tomcat.service.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:286)
         at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-20" (TID:0x5fa9540, sys_thread_t:0x22055448, state:CW, native ID:0x664) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-19" (TID:0x5fa9590, sys_thread_t:0x22055360, state:CW, native ID:0x5c0) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-18" (TID:0x5fa9338, sys_thread_t:0x220551f0, state:CW, native ID:0x874) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-17" (TID:0x5fa9388, sys_thread_t:0x22055080, state:CW, native ID:0x4f4) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-16" (TID:0x5fa9480, sys_thread_t:0x22064cf8, state:CW, native ID:0x814) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-15" (TID:0x5fa9428, sys_thread_t:0x22064b88, state:CW, native ID:0x8ec) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-14" (TID:0x5fa9478, sys_thread_t:0x22064aa0, state:CW, native ID:0x24c) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-13" (TID:0x5fa8f68, sys_thread_t:0x22064930, state:CW, native ID:0x410) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-12" (TID:0x5fa8fb8, sys_thread_t:0x22064848, state:CW, native ID:0x3f0) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-11" (TID:0x5fa86b8, sys_thread_t:0x220607f0, state:CW, native ID:0xb28) prio=5
         at java.lang.Object.wait(Native Method)
         at org.apache.tomcat.util.ThreadPool$MonitorRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-10" (TID:0x5fa85f0, sys_thread_t:0x22061618, state:R, native ID:0x6fc) prio=5
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:414)
         at java.net.ServerSocket.implAccept(ServerSocket.java:242)
         at java.net.ServerSocket.accept(ServerSocket.java:224)
         at org.apache.tomcat.service.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:286)
         at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-9" (TID:0x5fa8648, sys_thread_t:0x22061530, state:CW, native ID:0x484) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-8" (TID:0x5fa83f0, sys_thread_t:0x220613c0, state:CW, native ID:0x8f0) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-7" (TID:0x5fa8440, sys_thread_t:0x22061250, state:CW, native ID:0x94c) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-6" (TID:0x5fa8490, sys_thread_t:0x220610e0, state:CW, native ID:0x994) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-5" (TID:0x5fa84e0, sys_thread_t:0x2205a2a8, state:CW, native ID:0x530) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-4" (TID:0x5fa8120, sys_thread_t:0x2205a138, state:CW, native ID:0x730) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-3" (TID:0x5fa8170, sys_thread_t:0x2205a050, state:CW, native ID:0x688) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-2" (TID:0x5fa81c0, sys_thread_t:0x2205a560, state:CW, native ID:0x3c0) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-1" (TID:0x5fa8218, sys_thread_t:0x22053520, state:CW, native ID:0x8fc) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "StandardManager" (TID:0x5fa1158, sys_thread_t:0x220596a0, state:CW, native ID:0x724) prio=5
         at java.lang.Thread.sleep(Native Method)
         at org.apache.tomcat.session.StandardManager.threadSleep(StandardManager.java, Compiled Code)
         at org.apache.tomcat.session.StandardManager.run(StandardManager.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "StandardManager" (TID:0x5f9d178, sys_thread_t:0x22031d18, state:CW, native ID:0xaa0) prio=5
         at java.lang.Thread.sleep(Native Method)
         at org.apache.tomcat.session.StandardManager.threadSleep(StandardManager.java, Compiled Code)
         at org.apache.tomcat.session.StandardManager.run(StandardManager.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "StandardManager" (TID:0x5f872f8, sys_thread_t:0x21c8b718, state:CW, native ID:0x880) prio=5
         at java.lang.Thread.sleep(Native Method)
         at org.apache.tomcat.session.StandardManager.threadSleep(StandardManager.java, Compiled Code)
         at org.apache.tomcat.session.StandardManager.run(StandardManager.java, Compiled Code)
         at java.lang.Thread.run(Thread.java:479)
    "Thread-0" (TID:0x5f4e670, sys_thread_t:0x21b0eac0, state:CW, native ID:0x8bc) prio=5
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java, Compiled Code)
         at org.apache.tomcat.util.Queue.pull(Queue.java, Compiled Code)
         at org.apache.tomcat.logging.LogDaemon$1.run(TomcatLogger.java, Compiled Code)
         at org.apache.tomcat.logging.LogDaemon.run(TomcatLogger.java, Compiled Code)
    "SymcJIT-LazyCompilation-1" (TID:0x5f2e4f8, sys_thread_t:0x20e977d8, state:CW, native ID:0x458) prio=1
         at SymantecJITCompilationThread.DoCompileMethod(Native Method)
         at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled Code)
    "SymcJIT-LazyCompilation-0" (TID:0x5f2e540, sys_thread_t:0x20e9b6d0, state:CW, native ID:0x9bc) prio=1
         at SymantecJITCompilationThread.DoCompileMethod(Native Method)
         at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled Code)
    "SymcJIT-LazyCompilation-PA" (TID:0x5f2e508, sys_thread_t:0x20e9b560, state:CW, native ID:0x820) prio=10
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled Code)
    "Finalizer" (TID:0x5f29320, sys_thread_t:0x20dddec0, state:CW, native ID:0x4e8) prio=8
         at java.lang.Object.wait(Native Method)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, Compiled Code)
         at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, Compiled Code)
         at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)
    "Reference Handler" (TID:0x5f293b0, sys_thread_t:0x20ddc7d0, state:CW, native ID:0x55c) prio=10
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:424)
         at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)
    "Signal dispatcher" (TID:0x5f293e0, sys_thread_t:0x20dda218, state:R, native ID:0xa1c) prio=5
    Monitor Cache Dump:
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8178/6FF4140: <unowned>
         Waiting to be notified:
         "Thread-3" (0x2205a050)
    java.net.PlainSocketImpl@5FA7DC0/6FF18C8: owner "Thread-10" (0x22061618) 1 entry
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8128/6FF4248: <unowned>
         Waiting to be notified:
         "Thread-4" (0x2205a138)
    SymantecJITCompilationThread@5F2E540/6C1F6A0: <unowned>
         Waiting to be notified:
         "SymcJIT-LazyCompilation-PA" (0x20e9b560)
    org.apache.tomcat.util.ThreadPool$MonitorRunnable@5FAA1D8/6FFF340: <unowned>
         Waiting to be notified:
         "Thread-33" (0x22092f98)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA95D8/6FFADA8: <unowned>
         Waiting to be notified:
         "Thread-20" (0x22055448)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA81C8/6FF32F8: <unowned>
         Waiting to be notified:
         "Thread-2" (0x2205a560)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9598/6FFAC90: <unowned>
         Waiting to be notified:
         "Thread-19" (0x22055360)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8448/6FF4978: <unowned>
         Waiting to be notified:
         "Thread-7" (0x22061250)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9C50/6FFBAF8: <unowned>
         Waiting to be notified:
         "Thread-24" (0x2207f8f0)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9430/6FFA840: <unowned>
         Waiting to be notified:
         "Thread-15" (0x22064b88)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9C00/6FFC850: <unowned>
         Waiting to be notified:
         "Thread-25" (0x2207fb78)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA84E8/6FF4350: <unowned>
         Waiting to be notified:
         "Thread-5" (0x2205a2a8)
    org.apache.tomcat.util.ThreadPool$MonitorRunnable@5FA94A8/6FFAFB8: <unowned>
         Waiting to be notified:
         "Thread-22" (0x220556a0)
    org.apache.tomcat.util.Queue@5F4E6C0/6D4B798: <unowned>
         Waiting to be notified:
         "Thread-0" (0x21b0eac0)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8498/6FF4458: <unowned>
         Waiting to be notified:
         "Thread-6" (0x220610e0)
    java.net.PlainSocketImpl@5FA9768/6FFB970: owner "Thread-28" (0x22080518) 1 entry
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8F70/6FFA630: <unowned>
         Waiting to be notified:
         "Thread-13" (0x22064930)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9B60/6FFCA60: <unowned>
         Waiting to be notified:
         "Thread-27" (0x2207ff00)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9740/6FFB9F0: <unowned>
         Waiting to be notified:
         "Thread-23" (0x22055c18)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9340/6FFAB88: <unowned>
         Waiting to be notified:
         "Thread-18" (0x220551f0)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8F20/6FFA738: <unowned>
         Waiting to be notified:
         "Thread-14" (0x22064aa0)
    java.lang.ref.ReferenceQueue$Lock@5F29338/6BF89C0: <unowned>
         Waiting to be notified:
         "Finalizer" (0x20dddec0)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA83F8/6FF4A80: <unowned>
         Waiting to be notified:
         "Thread-8" (0x220613c0)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA93E0/6FFA948: <unowned>
         Waiting to be notified:
         "Thread-16" (0x22064cf8)
    java.net.PlainSocketImpl@5FA8FE8/6FF9860: owner "Thread-21" (0x220555b8) 1 entry
    java.lang.ref.Reference$Lock@5F293C0/6BF84B8: <unowned>
         Waiting to be notified:
         "Reference Handler" (0x20ddc7d0)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8FC0/6FF98E0: <unowned>
         Waiting to be notified:
         "Thread-12" (0x22064848)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9BB0/6FFC958: <unowned>
         Waiting to be notified:
         "Thread-26" (0x2207fd90)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9390/6FFAA80: <unowned>
         Waiting to be notified:
         "Thread-17" (0x22055080)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8650/6FF4B88: <unowned>
         Waiting to be notified:
         "Thread-9" (0x22061530)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9E50/6FFF128: <unowned>
         Waiting to be notified:
         "Thread-31" (0x22080228)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8220/6FF31A8: <unowned>
         Waiting to be notified:
         "Thread-1" (0x22053520)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9EF0/6FFEF18: <unowned>
         Waiting to be notified:
         "Thread-29" (0x2207e758)
    org.apache.tomcat.util.ThreadPool$MonitorRunnable@5FA86C0/6FF5858: <unowned>
         Waiting to be notified:
         "Thread-11" (0x220607f0)
    org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9EA0/6FFF020: <unowned>
         Waiting to be notified:
         "Thread-30" (0x22080140)
    Registered Monitor Dump:
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method Monitor: <unowned>
    SymcJIT Lazy Queue Lock: <unowned>
         Waiting to be notified:
         "SymcJIT-LazyCompilation-0" (0x20e9b6d0)
         "SymcJIT-LazyCompilation-1" (0x20e977d8)
    SymcJIT Method Monitor: <unowned>
    SymcJIT Method List Monitor: <unowned>
    SymcJIT Lock: <unowned>
    utf8 hash table: <unowned>
    JNI pinning lock: <unowned>
    JNI global reference lock: <unowned>
    BinClass lock: <unowned>
    Class linking lock: <unowned>
    System class loader lock: <unowned>
    Code rewrite lock: <unowned>
    Heap lock: <unowned>
    Monitor cache lock: owner "Signal dispatcher" (0x20dda218) 1 entry
    Thread queue lock: owner "Signal dispatcher" (0x20dda218) 1 entry
         Waiting to be notified:
         "Thread-34" (0x2f4158)
    Monitor registry: owner "Signal dispatcher" (0x20dda218) 1 entry
    </pre>
    Regards,
    Prashant

    No. we are getting the thread dumps only on the production server, and it being running on production, we cannot try it out with newer versions. However, we have so far been unable to simulate the thread dumps on our machines using the same version.

  • WL 7.0 thread dump question

    Hi,
    I am using weblogic 7.0 windows 2000. I have seen unique behaviour with this,
    if the server is not accessed for prolonged time, say overnight and in the morning
    if I want to take thread dump(by hitting Ctrl+break) it will not work. I need
    to restart server to get thread dump, any idea about this?
    Yogesh

    Ctrl+break is a JVM interrupt command, not WLS.
    Is the server accessible? I mean does it respond for PING
    BTW, what JDk you are using?
    Kumar
    Yogesh wrote:
    Hi,
    I am using weblogic 7.0 windows 2000. I have seen unique behaviour with this,
    if the server is not accessed for prolonged time, say overnight and in the morning
    if I want to take thread dump(by hitting Ctrl+break) it will not work. I need
    to restart server to get thread dump, any idea about this?
    Yogesh

  • Application freezing and recovering & Strange behaviour in Thread Dump & GC

    Hi All,
    I am facing a problem in my SWINGS application. The application is a real time data streaming application its working in TCP/IP sockets, which is reading and writing data in string format. I noticed that the data streaming getting freeze sometimes and it recovers after a few minutes. To find out why it is behaving like that i took the Thread Dump and Garbage Collection Trace of the application and found some thing strange. Find below the line taken from the Thread Dump, the third line in the log below shows that the time have jumped backwards, I don't know why that happened.
    2009-03-12 17:07:48
    Full thread dump Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing):
    2009-03-12 17:07:57
    Full thread dump Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing):
    *2009-03-12 17:04:08*
    Full thread dump Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing):
    2009-03-12 17:04:15
    Full thread dump Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing):
    2009-03-12 17:04:28
    Full thread dump Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing):
    Almost during the same time in Garbage Collector log, normally the garbage collector was running multiple times a second and during that time the frequency of garbage collection reduced. please find the details below
    3682.686: [GC 28265K->25644K(41312K), 0.0009666 secs]
    3682.731: [GC 28268K->25645K(41312K), 0.0009825 secs]
    3682.817: [GC 28269K->25647K(41312K), 0.0010381 secs]
    3682.934: [GC 28271K->25649K(41312K), 0.0009364 secs]
    3682.943: [GC 28273K->25649K(41312K), 0.0008954 secs]
    3682.985: [GC 28273K->25650K(41312K), 0.0008845 secs]
    3683.037: [GC 28274K->25651K(41312K), 0.0008747 secs]
    3683.199: [GC 28275K->25651K(41312K), 0.0010448 secs]
    *3698.250: [GC 28275K->25728K(41312K), 0.0009655 secs]*
    *3720.655: [GC 28352K->25867K(41312K), 0.0010588 secs]*
    *3743.011: [GC 28491K->26000K(41312K), 0.0015047 secs]*
    *3765.935: [GC 28624K->26130K(41312K), 0.0010180 secs]*
    *3788.487: [GC 28754K->26260K(41312K), 0.0011328 secs]*
    *3810.348: [GC 28884K->26402K(41312K), 0.0010091 secs]*
    *3832.596: [GC 29026K->26523K(41312K), 0.0010373 secs]*
    *3855.048: [GC 29147K->26652K(41312K), 0.0010029 secs]*
    *3877.230: [GC 29276K->26795K(41312K), 0.0010387 secs]*
    *3899.420: [GC 29419K->26915K(41312K), 0.0009959 secs]*
    3922.146: [GC 29539K->27042K(41312K), 0.0010088 secs]
    3922.201: [GC 29666K->27043K(41312K), 0.0010297 secs]
    3922.231: [GC 29667K->27046K(41312K), 0.0008521 secs]
    3922.260: [GC 29670K->27048K(41312K), 0.0009208 secs]
    3922.269: [GC 29672K->27048K(41312K), 0.0009831 secs]
    3922.298: [GC 29672K->27049K(41312K), 0.0008867 secs]
    3922.308: [GC 29673K->27050K(41312K), 0.0009264 secs]
    can any one please explain whats happening, I am getting no clue from these
    Thanks in Advance
    Rajin Das
    Edited by: rajindas on Mar 16, 2009 6:40 PM

    Have you used any profilers to analyze the logs? It is very difficult to read it just like that.
    I use IBM Monitoring and Diagnostic Tools for Java™. I think it does support Sun and IBM JVMs. Try out and let me know how it goes.

  • Getting a thread dump

    Is there a way from within a java program to get a thread dump of the jvm? I want to write some code that watched for a certain condition, then immediatly halts the jvm and dumps all the thread state.
    Thanks for your ideas...

    Thanks, but... those methods are useful for getting a status of the current thread, or of other threads in your thread group, but that is not I'm after.
    What I need is similar to the effect of sending a SIGQUIT signal to the JVM, causing it to stop and dump all the thread state. I want to trigger that from code running in the JVM.
    Basically I am trying to track down a bug in a complex server application, where on a dual processor box (only!), the current time zone gets reset to GMT at some point. It happens at some non-deterministic point in the application's lifetime. The app is multithreaded. I was going to just write a watchdog thread that continually monitored the timezone, then when the timezone changed the watchdog would dump all thread states. After doing this a few times I was hoping to see a pattern in where the various threads were executing. Needless to say, I have examined all the code, and nothing is setting the timezone explicitly.

  • How to get a thread dump, in case of an IDE freeze

    When you're working with the IDE and if it either freezes or becomes sluggish for no apparent reason, it's recommended to generate a thread dump, and report it to Studio feedback alias ([email protected]) with a description of what happened and attach the dump to it.
    A thread dump is an invaluable source of information to IDE developers when investigating deadlocks and some performance issues. It is a textual dump of all active threads and monitors of Java apps running in a Virtual Machine.
    The ways to generate a thread dump differ depending on the platform:
    * Windows systems
    Press Ctrl-Break in the command console you used to start the IDE.
    You won't be able to see the console in case you started the IDE using the default desktop icon created by the IDE installer. To be able to generate the thread dump, you must launch the IDE using a console window (invoke Command Prompt, go to {studio-install-dir}/bin and type runide.exe), or configure the desktop shortcut properties to launch the runide.exe program instead of the default runidew.exe.
    Note: You should increase the screen buffer size of the command prompt, so that it could retian the entire thread dump output. To do that, on the command prompt where IDE is running, open the properties dialog box by right clicking on the titlebar and selecting 'properties'. Then select the 'layout tab' and increase the 'screen buffer size' parameters to - width - 200, Height - 4000.
    * Unix systems
    Press Ctrl-\ in the terminal console you used to start the JSE.
    Alternatively, you can also generate a thread dump by sending the QUIT signal to the Java VM running the JSE
    kill -QUIT process_id
    where process_id is the process number of the respective java process.
    -------Here is a sample thread dump -------
    Full thread dump Java HotSpot(TM) Client VM (1.4.2_01-b06 mixed mode):
    "Text-Layout" daemon prio=2 tid=0x0886ebd8 nid=0x4e4 in Object.wait() [9e8f000..9e8fd94]
    at java.lang.Object.wait(Native Method)
    - waiting on <0x11730910> (a org.netbeans.editor.view.spi.ViewLayoutQueue)
    at java.lang.Object.wait(Object.java:429)
    at org.netbeans.editor.view.spi.ViewLayoutQueue.waitForTask(ViewLayoutQueue.java:128)
    - locked <0x11730910> (a org.netbeans.editor.view.spi.ViewLayoutQueue)
    at org.netbeans.editor.view.spi.ViewLayoutQueue$LayoutThread.run(ViewLayoutQueue.java:182)
    "Compilation" daemon prio=2 tid=0x0883d878 nid=0xb1c in Object.wait() [9c8f000..9c8fd94]
    at java.lang.Object.wait(Native Method)
    - waiting on <0x1143dde0> (a java.util.LinkedList)
    at java.lang.Object.wait(Object.java:429)
    at org.netbeans.core.compiler.CompilationEngineImpl$CompilerThread.nextJobAndTask(CompilationEngineImpl.java:162)
    - locked <0x1143dde0> (a java.util.LinkedList)
    at org.netbeans.core.compiler.CompilationEngineImpl$CompilerThread.run(CompilationEngineImpl.java:175)
    "TimerQueue" daemon prio=5 tid=0x03575478 nid=0xb18 in Object.wait() [988f000..988fd94]
    at java.lang.Object.wait(Native Method)
    - waiting on <0x10d4af60> (a javax.swing.TimerQueue)
    at javax.swing.TimerQueue.run(TimerQueue.java:231)
    - locked <0x10d4af60> (a javax.swing.TimerQueue)
    at java.lang.Thread.run(Thread.java:534)
    "AWT-EventQueue-1" prio=7 tid=0x0344fae0 nid=0xb14 in Object.wait() [3caf000..3cafd94]
    at java.lang.Object.wait(Native Method)
    - waiting on <0x10d4afe8> (a java.awt.EventQueue)
    at java.lang.Object.wait(Object.java:429)
    at java.awt.EventQueue.getNextEvent(EventQueue.java:339)
    - locked <0x10d4afe8> (a java.awt.EventQueue)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:162)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

    You can get a thread dump (Windows only) whitout any preparation. Simply use the Stack Trace tool from this web site:
    http://tmitevski.users.mcs2.netarray.com
    It works on Windows services too.

  • JNI - getting a thread dump

    Hi !
    I'm using JNI to create a JVM inside of my C daemon, and it's working OK except that the JVM is hanging sometimes (rarely), and I would like to get the thread dump, like when you send SIGQUIT to the java process. But it doesn't work with my program. Why?
    Thanks
    - Rustam -

    Do you have any signal handlers installed in your native code? If so, you may have to remove them - they can interfere with the JVM's use of signals, prior to Java 1.4.
    Java 1.4 introduces a "signal chaining" facility whereby you may use your own signal handlers in native code that will be chained after the JVM's own signal handlers are called. This version of JVM includes a library for determining whether a signal is intended for the JVM or for native code in the same process.

  • How to get a thread dump from Weblogic 9.1

    Hi All,
    Can someone please walk me through how to configure a WLS9.1 server to generate thread dumps. Ideally I'd like to do this via the admin console. I read about the MagicThreadDumpFile property, but can't see where/how to set it.
    Many Thanks
    Stuart

    I only know how to do this in WLS 8.1, but it will likely work in 9.1. On UNIX, you can send a kill -QUIT to the pid and it will dump threads to standard output for the server. You can also use weblogic.Admin THREAD_DUMP (http://e-docs.bea.com/wls/docs92/admin_ref/cli.html#wp1197887) or whatever is the equivalent in WLST now that weblogic.Admin is deprecated in 9.x. I'm guessing it is the threadDump() method documented at http://e-docs.bea.com/wls/docs92/config_scripting/reference.html#wp1104314.
    I know of no way to do this through the console, unfortunately.

  • How to get a Thread Dump from Windows Service?

    We're running WLS 8.1 as a Windows Service, but we can't seem to generate a Thread Dump when the server locks up (apparently).
    Can anybody recommend a wrapper that will do this?
    --Kurt                                                                                                                                                                                                                                                                                                                                                                                           

    Hi,
    Please refer to the following URL for more information http://e-docs.bea.com/wls/docs81/adminguide/winservice.html
    To cause the WebLogic Server instance to print a thread dump to standard out, do either of the following:
    Use the weblogic.Admin THREAD_DUMP command. For more information, refer to "THREAD_DUMP" in the WebLogic Server Command Reference.
    Open a command prompt and enter the following command:
    WL_HOME\bin\beasvc -dump -svcname:service-name
    where WL_HOME is the directory in which you installed WebLogic Server and
    service-name is the Windows service that is running a server instance.
    For example:
    D:\bea\weblogic81\server\bin\beasvc -dump -svcname:mydomain_myserver
    Cheers
    Raj

  • How to get complete Java thread dump?

    I suspect a deadlock on a IWS 6.0SP5 running on Solaris 8 with Sun JDK 1.4.1, how can I make a full thread dump?
    I have enabled LogStdout and LogStderr in magnus.conf.
    regards
    Lars Krog-Jensen

    Thanx for your reply,
    but there are 2 ns-httpd processes, which one do I
    send the kill to.
    If I send it to the wrong ns-httpd the server
    restarts.
    regards Lars Krog-JensenIt's the last one in the "PID chain" (the last child process) and the one using the most memory.

  • Getting Short dump When Executing MIGO:    SYNTAX_ERROR

    Please Help,
    I am getting this dump, when i hit MIGO transaction
    Runtime Errors         SYNTAX_ERROR
    Date and Time          10.12.2008 08:28:03
         Short text
              Syntax error in program "MB_MIGO_BADI==================CP ".
         What happened?
              Error in the ABAP Application Program
              The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
               terminated because it has
              come across a statement that unfortunately cannot be executed.
              The following syntax error occurred in program
               "MB_MIGO_BADI==================CP " in include
               "MB_MIGO_BADI==================CM000 " in
              line 0:
              "The specified type cannot be converted into the target variables."
              The include has been created and last changed by:
              Created by: "SAP "
              Last changed by: "SAP "
              Error in the ABAP Application Program
              The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
               terminated because it has
              come across a statement that unfortunately cannot be executed.
         What can you do?
              Please eliminate the error by performing a syntax check
              (or an extended program check) on the program "MB_MIGO_BADI==================CP
              You can also perform the syntax check from the ABAP Editor.
              If the problem persists, proceed as follows:
              Note down which actions and inputs caused the error.
              To process the problem further, contact you SAP system
              administrator.
              Using Transaction ST22 for ABAP Dump Analysis, you can look
              at and manage termination messages, and you can also
              keep them for a long time.
         Error analysis
              The following syntax error was found in the program
               MB_MIGO_BADI==================CP :
              "The specified type cannot be converted into the target variables."
         How to correct the error
              Probably the only way to eliminate the error is to correct the program.
              If you cannot solve the problem yourself and want to send an error
              notification to SAP, include the following information:
              1. The description of the current problem (short dump)
                 To save the description, choose "System->List->Save->Local File
              (Unconverted)".
              2. Corresponding system log
                 Display the system log by calling transaction SM21.
                 Restrict the time interval to 10 minutes before and five minutes
              after the short dump. Then choose "System->List->Save->Local File
              (Unconverted)".
              3. If the problem occurs in a problem of your own or a modified SAP
              program: The source code of the program
                 In the editor, choose "Utilities->More
              Utilities->Upload/Download->Download".
              4. Details about the conditions under which the error occurred or which
              actions and input led to the error.
         System environment
              SAP-Release 700
              Application server... "DMATE"
              Network address...... "140.1.1.141"
              Operating system..... "Windows NT"
              Release.............. "5.2"
              Hardware type........ "4x AMD64 Level"
              Character length.... 16 Bits
              Pointer length....... 64 Bits
              Work process number.. 1
              Shortdump setting.... "full"
              Database server... "dmate"
              Database type..... "ADABAS D"
              Database name..... "AD0"
              Database user ID.. "SAPAD0"
              Char.set.... "C"
              SAP kernel....... 700
              created (date)... "Jun 23 2008 00:09:46"
              create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
              Database version. "SQLDBC 7.6.0.018 CL 119055 "
              Patch level. 166
              Patch text.. " "
              Database............. "MaxDB 7.6, MaxDB 7.7"
              SAP database version. 700
              Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
               NT 6.0"
              Memory consumption
              Roll.... 16192
              EM...... 8379680
              Heap.... 0
              Page.... 40960
              MM Used. 1627776
              MM Free. 2559440
         User and Transaction
              Client.............. 040
              User................ "LAKSHMI"
              Language key........ "E"
              Transaction......... "MIGO "
              Transactions ID..... "EE72C6DDC96BF1F99FA4001143E563CA"
              Program............. "CL_EX_MB_MIGO_BADI============CP"
              Screen.............. "SAPLMIGO 0001"
              Screen line......... 2
         Information on where terminated
              Termination occurred in the ABAP program "CL_EX_MB_MIGO_BADI============CP" -
               in "IF_EX_MB_MIGO_BADI~INIT".
              The main program was "SAPLMIGO ".
              In the source code you have the termination point in line 1
              of the (Include) program "CL_EX_MB_MIGO_BADI============CM001".
         Source Code Extract
         Line     SourceCde
         >>>>>     method IF_EX_MB_MIGO_BADI~INIT.
             2       CLASS CL_EXIT_MASTER DEFINITION LOAD.
             3     
             4       DATA l_badi TYPE REF TO MB_MIGO_BADI.
             5     
             6     
             7     
             8     
             9     
            10       TRY.
            11     
            12         GET BADI l_badi
            13          CONTEXT me.
            14     
            15         CALL BADI l_badi->INIT
            16     
            17          CHANGING
            18            CT_INIT = CT_INIT.
            19     
            20     
         Contents of system fields
         Name     Val.
         SY-SUBRC     0
         SY-INDEX     0
         SY-TABIX     1
         SY-DBCNT     1
         SY-FDPOS     1
         SY-LSIND     0
         SY-PAGNO     0
         SY-LINNO     1
         SY-COLNO     1
         SY-PFKEY     
         SY-UCOMM     
         SY-TITLE     
         SY-MSGTY     S
         SY-MSGID     VBDOCUBATCH
         SY-MSGNO     001
         SY-MSGV1     
         SY-MSGV2     
         SY-MSGV3     
         SY-MSGV4     
         SY-MODNO     0
         SY-DATUM     20081210
         SY-UZEIT     082802
         SY-XPROG     
         SY-XFORM     
         Active Calls/Events
         No.   Ty.          Program                             Include                             Line
               Name
             4 METHOD       CL_EX_MB_MIGO_BADI============CP    CL_EX_MB_MIGO_BADI============CM001     1
               CL_EX_MB_MIGO_BADI=>IF_EX_MB_MIGO_BADI~INIT
             3 METHOD       SAPLMIGO                            LMIGOGL2                               54
               LCL_MIGO_GLOBALS=>CLASS_CONSTRUCTOR
             2 FORM         SAPLMIGO                            LMIGOIN1                               11
               INITIALIZATION
             1 MODULE (PBO) SAPLMIGO                            LMIGOPBO                               11
               PBO_INITILIZATION
         Chosen variables
         Name
             Val.
         No.          4     Ty.      METHOD
         Name      CL_EX_MB_MIGO_BADI=>IF_EX_MB_MIGO_BADI~INIT
         CT_INIT
              Table[initial]
         %_DUMMY$$
                 2222
                 0000
                 0000
                 0000
         SYST-REPID
              CL_EX_MB_MIGO_BADI============CP
                 4454554454444544443333333333334522222222
                 3CF58FD2FD97FF2149DDDDDDDDDDDD3000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         SY-SUBRC
              0
                 0000
                 0000
         No.          3     Ty.      METHOD
         Name      LCL_MIGO_GLOBALS=>CLASS_CONSTRUCTOR
         SY-REPID
              SAPLMIGO
                 5454444422222222222222222222222222222222
                 310CD97F00000000000000000000000000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         LCL_MIGO_GLOBALS=>CNTL_ERROR
                 2
                 0
                 0
                 0
         ABAP_FALSE
                 2
                 0
                 0
                 0
         SYST-REPID
              SAPLMIGO
                 5454444422222222222222222222222222222222
                 310CD97F00000000000000000000000000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         GOSEARCH_PO
                 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         TEXT-220
              Dest
                 46772222
                 45340000
                 00000000
                 00000000
         %_SPACE
                 2
                 0
                 0
                 0
         %_TAG*TS_GOITEM
              <initial>
                 <initial>
                 <initial>
         X
              X
                 5
                 8
                 0
                 0
         LCL_MIGO_GLOBALS=>IF_BADI
                 F0000000
                 70008000
         %_FL2*TV_GOFREIGHT
              <initial>
                 <initial>
                 <initial>
         %_PRINT
                  000                                                                                0###
                 2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         LCL_MIGO_GLOBALS=>T_BADI
              Table[initial]
         /SPE/CL_INB_ACTION_INFO=>C_DIALOG_MIGO
         SCREEN
                 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         OREF_TITLEBAR
                 F0000000
                 F0000000
         L_BADIS_1
              0
                 0000
                 0000
         SY-MSGID
              VBDOCUBATCH
                 54444544544222222222
                 624F3521438000000000
                 00000000000000000000
                 00000000000000000000
         OREF_TIP
                 F0000000
                 F0000000
         TV_GOSERIAL-CX
              <initial>
                 <initial>
                 <initial>
         SPACE
                 2
                 0
                 0
                 0
         SY-MSGNO
              001
                 333
                 001
                 000
                 000
         No.          2     Ty.      FORM
         Name      INITIALIZATION
         OREF_ARCH
                 F0000000
                 F0000000
         LCL_MIGO_GLOBALS=>KERNEL
                 F0000000
                 D0002000
         %_CX_TABLEVIEW_VERSION
              0
                 3
                 0
                 0
                 0
         GODEFAULT-DEF_XBOM
                 2
                 0
                 0
                 0
         LCL_MIGO_GLOBALS=>KERNEL->C_REFDOCTYPE_MATDOC
              MAT
                 445
                 D14
                 000
                 000
         No.          1     Ty.      MODULE (PBO)
         Name      PBO_INITILIZATION
         GOITEM-UMWRK
                 2222
                 0000
                 0000
                 0000
         GOITEM-UMNAME1
                 222222222222222222222222222222
                 000000000000000000000000000000
                 000000000000000000000000000000
                 000000000000000000000000000000
         Internal notes
              The termination was triggered in function "ab_genprog"
              of the SAP kernel, in line 1551 of the module
               "//bas/700_REL/src/krn/runt/abgen.c#10".
              The internal operation just processed is "CPOP".
              Internal mode was started at 20081210082802.
              Program name.........: "MB_MIGO_BADI==================CP ".
              Error message........: "The specified type cannot be converted into the target
               variables.".
         Active Calls in SAP Kernel
         Lines of C Stack in Kernel (Structure Differs on Each Platform)
         SAP (R) - R/3(TM) Callstack, Version 1.0
         Copyright (C) SAP AG. All rights reserved.
         Callstack without Exception:
         App       : disp+work.EXE (pid=5776)
         When      : 12/10/2008 8:28:3.84
         Threads   : 2
         Computer Name       : DMATE
         User Name           : SAPServiceAD0
         Number of Processors: 4
         Processor Type: EM64T Family 15 Model 4 Stepping 1
         Windows Version     : 5.2 Current Build: 3790
         State Dump for Thread Id 14f0
         FramePtr         ReturnAd         Param#1          Function Name
         0000000007eb8800 0000000077d7047f 00000000411b4070 ntdll!NtWaitForSingleObject
         0000000007eb88a0 000000000173b1d1 000000000000042c kernel32!WaitForSingleObjectEx
         0000000007eb8af0 00000000006179c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
         0000000007eb8b20 0000000000b05d9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
         0000000007eb8b70 0000000000b0afc0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7093)]
         0000000007eb9550 0000000000a51c94 0000000001d12320 disp+work!ab_rabax [abrabax.c (1231)]
         0000000007ebc220 00000000007f753a 0000000000000001 disp+work!ab_genprog [abgen.c (1555)]
         0000000007ebc2f0 00000000007f7dc8 00000000ffffffff disp+work!newload [abload1.c (336)]
         0000000007ebc350 00000000007f7e8e 0000000000000056 disp+work!ab_LoadProgOrTrfo [abload1.c (160)]
         0000000007ebc380 00000000007bc84d 000007fe725a5f70 disp+work!ab_LoadProg [abload1.c (78)]
         0000000007ebc450 00000000007be91a 00002a441022f402 disp+work!LoadGlobalClass [abobject.c (943)]
         0000000007ebc4a0 00000000007c1bdd 0000000000000000 disp+work!ab_FillCfix [abobject.c (1603)]
         0000000007ebc580 000000000083ae52 0000000000000000 disp+work!ab_jaboo [abobject.c (2248)]
         0000000007ebc700 0000000000a1ccb7 000000000000000d disp+work!ab_extri [abextri.c (554)]
         0000000007ebc750 0000000000ad50ac 000000000000000d disp+work!ab_xevent [abrunt1.c (281)]
         0000000007ebc7e0 0000000000679328 000000000000000d disp+work!ab_dstep [abdynpro.c (492)]
         0000000007ebc960 000000000067d02d 000007fe725d6f20 disp+work!dynpmcal [dymainstp.c (2396)]
         0000000007ebc9f0 000000000067ca2a 0000000000000000 disp+work!dynppbo0 [dymainstp.c (543)]
         0000000007ebcaa0 00000000006395c5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
         0000000007ebfc30 00000000004dbc4c 000000000000000c disp+work!dynpen00 [dymain.c (1646)]
         0000000007ebfeb0 000000000042f096 0000000007f62ff0 disp+work!TskhLoop [thxxhead.c (4538)]
         0000000007ebfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1136)]
         0000000007ebff10 00000000019e84b1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
         0000000007ebff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
         0000000007ebffa0 0000000000000000 00000000019e8340 kernel32!BaseProcessStart
         State Dump for Thread Id b94
         FramePtr         ReturnAd         Param#1          Function Name
         000000000c9dfe40 0000000077d5f651 0000000000000000 ntdll!NtFsControlFile
         000000000c9dfeb0 00000000018ce23f fffffffffffffffe kernel32!ConnectNamedPipe
         000000000c9dff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
         000000000c9dff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex
         000000000c9dffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
         List of ABAP programs affected
         Index     Typ     Program     Group     Date     Time     Size     Lang.
              0     Prg     SAPLMIGO          0     04.05.2008     12:54:34       1561600     E
              1     Prg     SAPMSSYD          0     25.02.2008     17:02:32         21504     E
              2     Prg     SAPFSYSCALLS          0     09.09.2004     14:18:32          7168     E
              3     Prg     CL_MMIM_USERDEFAULTS==========CP          3     06.05.2002     10:42:38         21504     E
              4     Typ     ESDUS          0     01.03.1999     13:36:04          2048     
              5     Typ     GOHEAD          0     07.02.2006     10:07:36         11264     
              6     Typ     MKPF          0     25.08.2005     22:02:19          7168     
              7     Typ     KBEFU          0     16.03.2008     17:46:49          6144     
              8     Typ     LFA1          0     16.03.2008     17:47:20         22528     
              9     Typ     MIGO_CUST_ACTION          0     30.11.1999     10:19:14          3072     
             10     Typ     MIGO_CUST_REFDOC          0     30.11.1999     10:19:14          2048     
             11     Typ     X031L          0     05.07.2005     13:10:15          6144     
             12     Prg     SAPLSDIFRUNTIME         12     19.11.2006     16:35:34         96256     E
             13     Typ     DFIES          0     28.12.2004     17:06:45         10240     
             14     Prg     SAPLSDNT         14     09.03.2008     19:02:04        219136     E
             15     Prg     SAPLSUGS         15     31.03.2006     11:23:11         47104     E
             16     Prg     SAPLV01D         16     24.03.2008     17:03:30         40960     E
             17     Typ     IWRKZ          0     04.04.1995     15:56:46          2048     
             18     Typ     TCUCH          0     07.01.2002     15:50:54          3072     
             19     Typ     TCUBN          0     07.01.2002     15:50:53          2048     
             20     Typ     TCUWS          0     13.08.1997     13:57:58          2048     
             21     Typ     TCUDRV          0     07.01.2002     15:50:54          2048     
             22     Prg     SAPLVBDOCUBATCH_BF         22     16.01.2004     14:28:56         10240     E
             23     Typ     TCUDB          0     14.01.2004     10:05:59          2048     
             24     Prg     CL_GUI_CFW====================CP         24     28.02.2005     21:03:09        168960     E
             25     Prg     CL_GUI_PROPS_CONSUMER=========CP         25     18.03.2008     13:25:33         29696     E
             26     Prg     %_CCNTL         25     18.02.2005     14:15:08         15360     E
             27     Prg     SAPLTHFB         27     18.03.2008     13:24:52        394240     E
             28     Typ     EUDB          0     06.11.2003     20:28:08          8192     
             29     Typ     TCURM          0     01.03.2005     10:56:26          5120     
             30     Prg     CL_EXITHANDLER================CP         30     18.03.2008     13:11:35         30720     E
             31     Prg     SAPLSEXV         31     18.03.2008     13:12:58        117760     E
             32     Typ     SXS_ATTR          0     07.02.2006     10:09:24          5120     
             33     Typ     BADIISIMPLED          0     19.05.2005     19:10:34          3072     
             34     Prg     CL_ENH_BADI_TOOL_UTILITIES====CP         34     17.03.2008     11:03:36         13312     E
             35     Typ     BADI_MAIN          0     08.12.2004     18:01:11          2048     
             36     Typ     BADI_IMPL          0     09.12.2004     19:05:43          3072     
             37     Typ     TADIR          0     07.02.2006     10:08:38          5120     
             38     Prg     CL_SWITCH=====================CP         38     17.03.2008     11:13:47         19456     E
             39     Typ     SFW_PACKAGE          0     07.03.2008     12:18:16          2048     
             40     Prg     CL_ABAP_SWITCH================CP         40     14.10.2006     15:40:30         33792     E
             41     Prg     SAPLPA_PACKAGE_SERVICES         41     18.03.2008     13:12:54        152576     E
             42     Typ     TDEVC          0     08.12.2004     18:02:41          6144     
             43     Prg     CL_EX_MB_MIGO_BADI============CP         43     05.12.2008     17:09:58         30720     E
             44     Prg     IF_EX_MB_MIGO_BADI============IP         30     19.05.2005     19:30:39         14336     E
             45     Typ     SYST          0     09.09.2004     14:18:12         31744     
             46     Typ     GOSEARCH_PO          0     20.07.2001     19:17:34          4096     
             47     Prg     /SPE/CL_INB_ACTION_INFO=======CP         47     24.03.2008     20:30:06         20480     E
             48     Prg     /SPE/IF_CONST=================IP         47     14.10.2006     18:49:02          7168     E
             49     Typ     GODEFAULT          0     14.01.2004     10:04:46          5120     
             50     Typ     GOITEM          0     07.02.2006     10:07:36         65536     
         Directory of Application Tables
         Name                                     Date       Time       Lngth
             Val.
         Program      SAPLMIGO
         SYST            .  .            :  :          00004612
              \0\0\0\0\x0001\0\x0370\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0
         GOITEM            .  .            :  :          00005524
                        00000000000000000000
         GOSEARCH_PO            .  .            :  :          00000492
         GODEFAULT            .  .            :  :          00000220
         Program      SAPLV01D
         TCUCH            .  .            :  :          00000122
              0401100020061029095148ANOOPJ      00000000000000
         TCUWS            .  .            :  :          00000060
              040020061227101454CONSULTANT     
         TCUBN            .  .            :  :          00000060
              040020061227101454CONSULTANT     
         TCUDRV            .  .            :  :          00000064
                    00000000000000     
         Program      CL_GUI_PROPS_CONSUMER=========CP
         EUDB            .  .            :  :          00004068
              %CAA72C6DDAD55F1179FA4001143E563CA         \0\0\0
         ABAP Control Blocks (CONT)
         Index     Name     Fl     PAR0     PAR1     PAR2     PAR3     PAR4     PAR5     PAR6     Source Code     Line
            94     BRAX     01     FFEB                                   CL_EX_MB_MIGO_BADI============CM001           15
            95     CLEA     00     0020                                   CL_EX_MB_MIGO_BADI============CM001           15
            96     EXCP     08     0000                                   CL_EX_MB_MIGO_BADI============CM001           22
            97     BRAX     00     0005                                   CL_EX_MB_MIGO_BADI============CM001           22
            98     EXCP     00     0007                                   CL_EX_MB_MIGO_BADI============CM001           22
            99     BRAX     00     0003                                   CL_EX_MB_MIGO_BADI============CM001           22
           100     EXCP     07     0000                                   CL_EX_MB_MIGO_BADI============CM001           22
           101     BRAX     00     0001                                   CL_EX_MB_MIGO_BADI============CM001           23
           102     EXCP     0B     0000                                   CL_EX_MB_MIGO_BADI============CM001           23
           103     METH     01     0000     0000     0000     0000     0000     0000     0000     CL_EX_MB_MIGO_BADI============CM001           24
           107     -
         00     0000                                   CL_EX_MB_MIGO_BADI============CM001           24
           108     ABOO     02     0000     0005     0000                         CL_EX_MB_MIGO_BADI============CM001            1
         >>>>>     CPOP     00     0000                                   CL_EX_MB_MIGO_BADI============CM001            1
           111     -
         00     0000                                   CL_EX_MB_MIGO_BADI============CM001            1
           112     METH     04     0000     0005     0002     0000     0003     0000     0000     CL_EX_MB_MIGO_BADI============CM002            1
           116     PAR2     04     0000     C000     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           118     PAR2     04     0000     C001     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           120     PAR2     14     0000     C002     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           122     PAR2     14     0000     C003     0000                         CL_EX_MB_MIGO_BADI============CM002            1
           124     PAR2     14     0000     C004     0000                         CL_EX_MB_MIGO_BADI============CM002            1

    Hai,
    Seems to be problem with the Program.
    Please check the point 'What Happened' in the dump for more details.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program
    "MB_MIGO_BADI==================CP " in include
    "MB_MIGO_BADI==================CM000 " in
    line 0:
    "The specified type cannot be converted into the target variables."
    Error in the ABAP Application Program
    The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
    terminated because it has
    come across a statement that unfortunately cannot be executed.
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "MB_MIGO_BADI==================CP
    You can also perform the syntax check from the ABAP Editor.
    Take help from a ABAP consultant and try to check the syntax of the Program.
    If you have access even you can check the syntax of the specified program from SE38.
    Goto SE38 and put the program name and select 'Source code' and press F8, IN THE SOURCE CODE PAGE, press control+F2 and check whether there is any problem with the syntax or not.
    If you find any take help from ABAP consultants.
    Hope this helps.
    Regards,
    Yoganand.V

  • 100% CPU load but no clue in thread dump, EP. Win a bottle of champagne...

    Hi,
    We are suddenly facing 100% CPU load in our EP cluster (5 x 8-way Xeon multiprocessor machines). We have a serious performance problem that is burning a lot of our time and causes a lot of stress for over 3 weeks now.
    We have taken tens of thread dumps from Application Nodes.
    - In none of the thread dumps we see the Finalizer thread
    running.
    - From the garbage collector log we see that full garbage
    collection runs occur very rarily (once an hour).
    - We use the compacting garbage collector.
    - In a lot of thread dumps we do not even see our own portal code in the stack traces of the threads!
    - In Windows Task Manager we see the jlaunch.exe processes
    consume all available CPU time.
    - Portal users see a blank portal page when the CPU load hits 100%. When the load goes down again, things return to normal.
    - There are no errors logged in any of the log files of the portal. We checked all of them. We expected a log full of errors somewhere but nothing even remotely interesting was found. Windows Event Viewer shows nothing either.
    - The amount of sockets in CLOSE_WAIT status is < 10 on every machine in the cluster.
    This forces me to conclude that something in the jlaunch.exe executable consumes the CPU time. This raises the following 3 questions:
    - What does the mystifying jlaunch.exe do besides executing java.exe ?
    - Why is the Java virtual machine launched by a custom executable like jlaunch (What is it that cannot be program med in Java) ? Can it be GZip compression ?
    - If the problem is not caused by jlaunch.exe, then it must be caused by the JVM. What activity, invisible in thread dumps, is performed by the JVM that can cause the high CPU load ?
    Our development- and support teams are desperate. All suggestions are welcome. The person that comes up with
    the solution to our problem gets a nice bottle of champagne.
    Regards,
    Chris Twigt

    Hi,
    - What does the mystifying jlaunch.exe do besides executing java.exe ?
    This is so that the startupframework can connect more easily and take control of the JVM in some situations
    - Why is the Java virtual machine launched by a custom executable like jlaunch (What is it that cannot be program med in Java) ?
    I assume when SAP release their JVM (in the next major release), that will be called directly.
    - If the problem is not caused by jlaunch.exe, then it must be caused by the JVM. What activity, invisible in thread dumps, is performed by the JVM that can cause the high CPU load ?
    Loads of thing, but there should be clues in the thread dumps.  (the reason why your code is not in those thread dumps is that your code is only active during the processing of a particular request, unless you have a service, afterwards there are no trace of it as the thread which does the processing goes back to sleep)
    I've experienced a similar situation with a an 6.40 portal, and it was then caused by the following:
    1. User A comes logs in and sees that some cache timeout has occured , therefore it issues a SQL query which does a full table scan on a table of approx. 1 GB (on of the UME tables)
    2. User B comes in just afterwards and also sees that the cache timeout has occured, and issues the same SQL query as User A
    3. User C .... and so on untill the query from User A eventually finishes
    So
    1. Check database. Any big queries running ?
    2. Check file activity, are there a lot of writing ?
    3. Check network activity, especially to the state controller which is the weakest link
    4. What about portal logs ? Any activity during the hang ?
    Also, please provide one of the thread dumps for further analysis..
    cheers
    Dagfinn

Maybe you are looking for