|
From: Leif M. <le...@ta...> - 2007-07-27 16:02:50
|
Freddy, There are a few ways to do this. 1) Make use of the WrapperManager.requestThreadDump() method. This of course requires a hook into your application. 2) Make use of the WrapperActionServer class. You have to add some code to initialize this class, but other than that it is quite simple. You can then initiate a thread dump or perform other functions via telnet. 3) Use the command file feature to invoke the thread dump: http://wrapper.tanukisoftware.org/doc/english/prop-commandfile.html Please note that there is currently a problem in current versions where the Wrapper can not invoke a thread dump unless a console window exists for the service. This has been fixed for the upcoming 3.2.0 release. To work around this in the current version you must either add a console with the wrapper.ntservice.console=true property http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-console.html Or tell the wrapper to execute thread dumps if a shutdown failure occurs: wrapper.request_thread_dump_on_failed_jvm_exit=true http://wrapper.tanukisoftware.org/doc/english/prop-request-thread-dump-on-failed-jvm-exit.html Cheers, Leif Freddy Andersen wrote: > I'm running this on windows XP for now and I'm trying to figure out > how I can get a thread-dump from the running wrapper (JBoss 4.0.2) > > I don't want to run this in a console window but as a service. When > the server has issues I would like to send a signal to the jvm and get > a thread-dump, is this not possible? > > Here is my config: (snip) |