Re: [Wrapper-user] Timed out waiting for a signal from the JVM.

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

Victor,
    I do not see the Java side startup banner which shows that the 
WrapperManager class is
being correctly initialized.   In every case I have seen to date, this 
was caused by the user
setting the main class directly to their application's main class.   
When this happens, the
app will start normally, but the Java side of the Wrapper does not get 
initialized correctly
and you get a timeout.
    I added some code to version 3.1.0 which should make this mistake 
more obvious to
the user.   What version of the Wrapper are you running.

    That said, I am confused at this point looking at your configuration 
file.  It looks like
it should be working correctly.   I notice that you named it 
service.conf.  Is it possible
that another wrapper.conf file also exists?

    In any rate, could you please add the wrapper.debug=TRUE property to 
your
configuration file and repost with the resulting log output.   I am 
curious as to exactly
what is going on.

    One minor detail in your configuration.  It would work fine on 
Windows, but fail on
Unix if you ever tried to port your application:
This:
wrapper.java.additional.1=uk.co.mooed.calllogger.Logger 
call-logger.properties

Should be:
wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
wrapper.java.additional.2=call-logger.properties

Cheers,
Leif

Victor Kirk wrote:

>I'm having problems running my app as a service.  The application
>opens up a few sockets an logs data to file(s), nothing complicated
>to go wrong some I'm assuming it is a config proplem. If anyone
>can suggest anything I'd be grateful.
>
>
>The output below implies my application was started correctly
>but the wrapper thought it was frozen.  My application works
>fine when executed without the wrapper.
>
>$wrapper -c service.conf
>wrapper  | --> Wrapper Started as Console
>wrapper  | Launching a JVM...
>jvm 1    | localhost: Logging in localhost:23 (attempt 1)
>jvm 1    | localhost: Logged in
>jvm 1    | localhost: Connecting to localhost:4001 (attempt 1)
>jvm 1    | localhost: Connected
>jvm 1    | localhost: Logging started
>wrapper  | Startup failed: Timed out waiting for a signal from the JVM.
>x5
>
>
>Heres my service.conf
>
>wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
>wrapper.java.classpath.1=wrapper.jar
>wrapper.java.classpath.2=call-logger.jar
>wrapper.java.command=java.exe
>wrapper.java.library.path.1=.
>wrapper.java.additional.1=uk.co.mooed.calllogger.Logger
>call-logger.properties
>wrapper.ntservice.displayname=FROG Call Logger
>wrapper.ntservice.name=FROGCallLogger
>wrapper.ntservice.description=Logs calls
>wrapper.ntservice.starttype=AUTO_START
>wrapper.ntservice.interactive=false
>
>
>And here is my main
>
>    public static void main(String[] args) {
>        logger=new Logger();
>        logger.start();
>    }
>        
>Thanks for reading this,
>
>Vic
>  
>