Re: [Wrapper-user] mbean nativeRequestThreadDump

[Leif M. <le...@ta...>]

Richard,
    I tested this on both Linux and Windows using the -Xrs flag.   In 
both cases, the JVM
halts immediately without executing any shutdown hooks when you request 
a thread dump.
That's not good.  But there is nothing I can do about it. I'll add a 
note to the documentation
about it though.

    You were seeing something slightly different, but that may be due to 
the exact JVM you
are using.  Have you had a chance to try this out removing the -Xrs flag?

Cheers,
Leif


Richard Emberson wrote:

> I do launch the java with the flag '-Xrs'; maybe that
> prevents the signal from being seen.
>
> Richard
>
>
> Leif Mortenson wrote:
>
>> Richard,
>>    It sounds like you are doing things correctly.  I retested this 
>> today using JBoss and
>> Java 1.4.2_01 but everything appears to be working correctly.   I 
>> tried the JMX interface
>> while running in both console mode and running as an NT service.
>>    The thread dump will be dumped to both the console and wrapper.log 
>> file at the INFO
>> level.
>>    When running in console mode are you able to invoke a thread dump 
>> using
>> CTRL-BREAK on Windows or CTRL-\ on UNIX.   On unix, you should also be
>> able to invoke a thread dumb executing the wrapper script used to 
>> launch the application
>> with the dump command.
>>    I'll test this out on Linux tonight as that may be what you are 
>> running?
>>
>> Cheers,
>> Leif
>>
>>> So I've got 3.0.5 running with my jboss application. I set
>>> wrapper.debug=true, just to see whats happening.
>>> I get printout that the native library was loaded...
>>>
>>>
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 | Calling native 
>>> initialization method.
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 | Inside native 
>>> WrapperManager initialization method
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 | Java Version   : 1.4.2-b28 
>>> Java HotSpot(TM) Client VM
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 | Java VM Vendor : Sun 
>>> Microsystems Inc.
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 |
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 | Wrapper (Version 3.0.5)
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 |
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 | Open socket to wrapper...
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 | Opened Socket
>>> INFO   | jvm 1    | 2003/09/16 08:55:12 | Send a packet KEY : 
>>> XGuDK_MTRJ8iZjZ3
>>> etc......
>>>
>>> I start getting debug printout:
>>>
>>> DEBUG  | wrapperp | 2003/09/16 08:56:35 | send a packet PING : ping
>>> INFO   | jvm 1    | 2003/09/16 08:56:35 | Received a packet PING : ping
>>> INFO   | jvm 1    | 2003/09/16 08:56:35 | Send a packet PING : ok
>>> DEBUG  | wrapperp | 2003/09/16 08:56:35 | read a packet PING : ok
>>> DEBUG  | wrapper  | 2003/09/16 08:56:35 | Got ping response from JVM
>>> DEBUG  | wrapperp | 2003/09/16 08:56:41 | send a packet PING : ping
>>>
>>> but when I press 'invoke' on the methods requestThreadDump
>>> on the jmx mbean page for the wrapper nothing happens.
>>> Well, I do advance to a followup jboss web page, but there is
>>> no thread dump. Not on the web page or any of the logs. In fact,
>>> the debug information in the native (linux) method
>>> Java_org_tanukisoftware_wrapper_WrapperManager_nativeRequestThreadDump
>>> does not print.
>>>
>>> No errors, no nothing. Where is the thread dump output suppose to
>>> go?
>>>
>>> Thanks.
>>>
>>>
>>> Richard
>>