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

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

Lary,
    Could you please post your wrapper.conf file as well as a few more 
lines before what
you sent.?  I am interested in everything after the "jvm 4" log out put 
stops, particularly
the java command used to start the JVM.

    Looking at the debug output below, it appears like you are maybe 
using integration
method #3, rather than #1.  I am not seeing any of the log output from the
WrapperSimpleApp class that I would normally expect to see.  I can clear 
that up
when I see the above info.

    If it is the case that you have implemented your own WrapperListener 
implementation
then the problem is that your WrapperListener.start method is not 
returning as expected.

Cheers,
Leif

Larry Ashworth wrote:

> I'm attempting to use Java Service Wrapper to start ZAppSvr, but start 
> up fails, both under linux
> and Win32 with the same errors.
>
> I set debug on and the following is the last failed attempt.
>
>
> INFO   | jvm 5    | 2005/02/25 10:46:31 |
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Wrapper (Version 3.1.2) 
> http://wrapper.tanukisoftware.org
> INFO   | jvm 5    | 2005/02/25 10:46:31 |
> INFO   | jvm 5    | 2005/02/25 10:46:31 | 
> WrapperManager.start(ZAppSvr@4f2c80, args["-noui"]) called by thread: 
> main
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Open socket to wrapper...
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Opened Socket
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Send a packet KEY : 
> XffqfX60atsyi_F3
> INFO   | jvm 5    | 2005/02/25 10:46:31 | 
> handleSocket(Socket[addr=127.0.0.1/127.0.0.1,port=32001,localport=3005])
> DEBUG  | wrapperp | 2005/02/25 10:46:31 | accepted a socket from 
> 127.0.0.1 on port 3005
> DEBUG  | wrapperp | 2005/02/25 10:46:31 | read a packet KEY : 
> XffqfX60atsyi_F3
> DEBUG  | wrapper  | 2005/02/25 10:46:31 | Got key from JVM: 
> XffqfX60atsyi_F3
> DEBUG  | wrapperp | 2005/02/25 10:46:31 | send a packet LOW_LOG_LEVEL : 1
> DEBUG  | wrapperp | 2005/02/25 10:46:31 | send a packet PING_TIMEOUT : 30
> DEBUG  | wrapper  | 2005/02/25 10:46:31 | Start Application.
> DEBUG  | wrapperp | 2005/02/25 10:46:31 | send a packet START : start
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Received a packet 
> LOW_LOG_LEVEL : 1
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Wrapper Manager: LowLogLevel 
> from Wrapper is 1
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Received a packet 
> PING_TIMEOUT : 30
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Wrapper Manager: PingTimeout 
> from Wrapper is 30000
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Received a packet START : start
> INFO   | jvm 5    | 2005/02/25 10:46:31 | calling listener.start()
> INFO   | jvm 5    | 2005/02/25 10:46:31 | ZeroPoint Product: ZCSentry
> INFO   | jvm 5    | 2005/02/25 10:46:31 | Licensed to: ZeroPoint, Inc.
> INFO   | jvm 5    | 2005/02/25 10:46:31 |            : Clayton Ross
> INFO   | jvm 5    | 2005/02/25 10:46:31 |            : 
> cr...@ze...
> ERROR  | wrapper  | 2005/02/25 10:47:00 | Startup failed: Timed out 
> waiting for signal from JVM.
> ERROR  | wrapper  | 2005/02/25 10:47:00 | JVM did not exit on request, 
> terminated
> DEBUG  | wrapper  | 2005/02/25 10:47:00 | JVM was only running for 30 
> seconds leading to a failed restart count of 5.
> FATAL  | wrapper  | 2005/02/25 10:47:00 | There were 5 failed launches 
> in a row, each lasting less than 300 seconds.  Giving up.
> FATAL  | wrapper  | 2005/02/25 10:47:00 |   There may be a 
> configuration problem: please check the logs.
> STATUS | wrapper  | 2005/02/25 10:47:01 | <-- Wrapper Stopped
> STATUS | wrapper  | 2005/02/25 10:51:52 | ZeroPoint Application Server 
> removed.
>
> How can I debug this problem?  I've used the wrapper successfully on 
> other smaller applications, and it works very well. I mimicked what I 
> did before, but it does not work here.
>
> I'm using integration method #1.
>
> I look forward to your input.
> Thanks,
> Larry.