Currently there is no way to get a stack dump on a windows machine when it is installed as a service. It can be done by sending the correct signal on UNIX, but there is no way to do that on Windows. If you have any ideas for how it should be signalled, let me know. But currently you can only do this when run as a console. Sorry.
We started dividing up the downloads starting with 2.2.3 Try scrolling down on the download page. There are downloads for the src and a larger download if you want to be able rebuild the docs. Not really needed.
Thanks for the kudos.
Leif
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The ThreadDump is sooo important for finding
problems in the code that I still start my
server in cmd.exe.
However I came across a tool xdProf which can
get these ThreadDumps (through jvmpi). It is
also on sourceforge (and jni).
See : http://xdprof.sourceforge.net/
For the sourcecode : I just didn't look hard
enough. I will take a look
Thanks,
Kees.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is something that I think would be best to keep as a seperate project. There is nothing in the Wrapper which prevents you from using xdprof with it. The Wrapper's support for Thread Dumping only goes as far as handling the signals correctly and passing them on to the JVM.
xdprof is quite a bit different than the Thread Dumping that you can do with the Wrapper (Or a standalone JVM)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
How do I get a Java Thread Dump when the
wrapper is run as a Service ?
I saw it was implemented in 2.2.6 but cannot
find how to get one. I know I can CTRL-\ in
windows in a console but what if it runs as
as service ?
The sourcecode of 2.2.6 is not available in
the Files page. Is it possible to put it there ?
I must say I have tried a lot of
'java-service-runners' but none of them is
as easy as Wrapper. Thank you !
Kees.
Currently there is no way to get a stack dump on a windows machine when it is installed as a service. It can be done by sending the correct signal on UNIX, but there is no way to do that on Windows. If you have any ideas for how it should be signalled, let me know. But currently you can only do this when run as a console. Sorry.
We started dividing up the downloads starting with 2.2.3 Try scrolling down on the download page. There are downloads for the src and a larger download if you want to be able rebuild the docs. Not really needed.
Thanks for the kudos.
Leif
The ThreadDump is sooo important for finding
problems in the code that I still start my
server in cmd.exe.
However I came across a tool xdProf which can
get these ThreadDumps (through jvmpi). It is
also on sourceforge (and jni).
See : http://xdprof.sourceforge.net/
For the sourcecode : I just didn't look hard
enough. I will take a look
Thanks,
Kees.
I have used that before. It is a great tool.
This is something that I think would be best to keep as a seperate project. There is nothing in the Wrapper which prevents you from using xdprof with it. The Wrapper's support for Thread Dumping only goes as far as handling the signals correctly and passing them on to the JVM.
xdprof is quite a bit different than the Thread Dumping that you can do with the Wrapper (Or a standalone JVM)