- 
        1. Re: problem getting thread dump while JBoss AS is starting upwdfink Feb 3, 2012 6:30 AM (in response to tamal24)how do you start run.sh? For me it works if I use the original run.sh@Linux and start 'bin/run.sh >myfile'. Do you see the thread dump still in the console? 
- 
        2. Re: problem getting thread dump while JBoss AS is starting uprhusar Feb 3, 2012 6:34 AM (in response to tamal24)Would jstack tool help? 
- 
        3. Re: problem getting thread dump while JBoss AS is starting uptamal24 Feb 3, 2012 6:43 AM (in response to wdfink)Hi, Thanks for the reply. Actually I do not run run.sh. I just do ./jboss.sh start from $JBOSS_HOME/bin/ I thought it inturn runs run.sh Is it not? because when I run ./jboss.sh start from $JBOSS_HOME/bin/ the server starts. And while it is starting I am giving kill -3 <pid> when it got stucks in between. I need the stack trace to proceed further. 
- 
        4. Re: problem getting thread dump while JBoss AS is starting uptamal24 Feb 3, 2012 6:45 AM (in response to rhusar)Yes, I also tried jstack but getting the below error : [root]# jstack 26076 >> /opt/jbosstrace.log 26076: Unable to open door: target process not responding or HotSpot VM not loaded The -F option can be used when the target process is not responding [root]# jstack -l 26076 >> /opt/jbosstrace.log 26076: Unable to open door: target process not responding or HotSpot VM not loaded The -F option can be used when the target process is not responding [root]# jstack -F 26076 >> /opt/jbosstrace.log Attaching to process ID 26076, please wait... Error attaching to process: Did not find libthread in target process/core! 
 
     
    