[Wrapper-user] Thread Dump on exit

[Thomas H. <mai...@ha...>]

Hello,

in our production env we set the property wrapper.request_thread_dump_on_failed_jvm_exit
to true. In your wrapper we run JBoss 3.2. The wrapper runs as
a service inside a windows 2000 adv cluster.
Sometime some threads of jboss hang (we think ;). So we stopped the
wrapper service and start it again. In the wrapper log file
we got the folling messages:

ERROR  | wrapper  | 2003/08/20 23:21:41 | Shutdown failed: Timed out waiting for the JVM to terminate.
STATUS | wrapper  | 2003/08/20 23:21:41 | Dumping JVM state.
ERROR  | wrapper  | 2003/08/20 23:21:41 | Unable to send BREAK event to JVM process.  Err(6 : Das Handle ist ungültig. (0x6))
ERROR  | wrapper  | 2003/08/20 23:21:42 | Java Virtual Machine did not exit on request, terminated
STATUS | wrapper  | 2003/08/20 23:21:42 | <-- Wrapper Stopped
STATUS | wrapper  | 2003/08/20 23:21:44 | --> Wrapper Started as Service
INFO   | wrapperp | 2003/08/20 23:21:45 | port 1777 already in use, using port 1778 instead.
STATUS | wrapper  | 2003/08/20 23:21:46 | Launching a JVM...
INFO   | jvm 1    | 2003/08/20 23:21:48 | Wrapper (Version 3.0.3

Did the first message "Shutdown failed: Timed out waiting for the JVM
to terminate." means that the jvm hang, or can't the wrapper.exe
ping the wrapper class inside the jvm?
The second question is why is the port 1777 in use? On our server no
other application is running. Is it because the port is still used
by the first wrapper and after a stop/start the first isn't
terminatet?

Thanks for your help

  Thomas