Re: [Wrapper-user] Startup failed: Timed out waiting for signal from JVM

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

Peter,
The WrapperListener.start method implementation is designed to return null
if the application has been started, or return an Integer exit code if 
it failed and
should be shutdown.
 From your log, it does not look like the start method is ever 
returning.  That
is most likely your problem.
See the WrapperListener javadocs.

You most likely do not really need to be using integration method 3.  
With the
new WrapperManager.addWrapperEventListener method and your own
WrapperEventListener implementations, you  can do everything that was
previously only possible with method 3.

Cheers,
Leif

peter ellis wrote:
> i dont seem to be able to run my server (which is using java .net
> sockets) it will run ...get to a point then the wrapper will fail:
> reporting the following:
>
> wrapper  | Startup failed: Timed out waiting for signal from JVM.
> wrapper  | JVM did not exit on request, terminated
> wrapper  | JVM exited on its own while waiting to kill the application.
> wrapper  | Signal trapped.  Details:
> wrapper  |   signal number=17 (SIGCHLD), source="unknown"
>
> and fire up a new JVM
>
> until finally giving up.
>
> I have no idea what im doing wrong here or what im missing
>
> here is my checklist
>
> i am using the following to start
> public class MonitorDaemon implements WrapperListener {
>
> in my start code i have monitor.start()
>
> and within the start() method  of Monitor the code gets as far as:
>
> .....
>       serverSocket = new ServerSocket(getMonitorPort());
>       serverSocket.setSoTimeout(120000);
>
>       while (isRunning()) {
>           try {
>               log.debug("Waiting for connection from client");
>               final Socket socket = serverSocket.accept();
>
>
> So im stumped i have no idea why it wont connect if anyone can shed
> some light on this it would be most appreciated
>
>
> WRAPPER.LOG.........................................as follows
>
> jvm 3    | calling WrapperListener.start()
> jvm 3    | Waiting for WrapperListener.start runner thread to complete.
> jvm 3    | WrapperListener.start runner thread started.
> jvm 3    | Send a packet START_PENDING : 60000
> wrapperp | read a packet START_PENDING : 60000
> wrapper  | JVM signalled a start pending with waitHint of 60000 millis.
> jvm 3    | 2006-11-23 10:42:56,617 [main] FATAL
> com.peter.server.monitor.MonitorDaemon  - Hurray a fatal log ....has
> it emailed me?
> jvm 3    | 2006-11-23 10:43:18,361 [main] INFO
> com.peter.server.monitor.MonitorDaemon  - MyServer Monitor Daemon has
> been started
> jvm 3    | 2006-11-23 10:43:18,361 [main] DEBUG
> com.peter.server.monitor.MonitorDaemon  - MyServer Monitor Daemon has
> been started
> jvm 3    | 2006-11-23 10:43:18,361 [main] ERROR
> com.peter.server.monitor.MonitorDaemon  - MyServer Monitor Daemon has
> been started
> jvm 3    | 2006-11-23 10:42:57,774 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.Monitor  - Monitor port set to 8050
> jvm 3    | 2006-11-23 10:43:40,825 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.MonitorDaemon  - About to start monitor
> jvm 3    | 2006-11-23 10:43:40,825 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.Monitor  - Starting monitor daemon
> jvm 3    | 2006-11-23 10:43:40,825 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.Monitor  - Creating the ping pong thread
> jvm 3    | 2006-11-23 10:43:40,827 [WrapperListener_start_runner] INFO
>  com.peter.server.monitor.Monitor  - Creating the realtime task thread
> jvm 3    | 2006-11-23 10:43:40,829 [WrapperListener_start_runner]
> DEBUG com.peter.server.monitor.Monitor  - Waiting for connection from
> client
> wrapper  | Startup failed: Timed out waiting for signal from JVM.
> wrapper  | JVM did not exit on request, terminated
> wrapper  | JVM exited on its own while waiting to kill the application.
> wrapper  | Signal trapped.  Details:
> wrapper  |   signal number=17 (SIGCHLD), source="unknown"
> wrapper  | Received SIGCHLD, checking JVM process status.
> wrapper  | JVM exited in response to signal SIGKILL (9).
> wrapper  | JVM process exited with a code of 1, setting the wr....
>
> --
> Peter Ellis
> Java Developer
>
>