|
From: Leif M. <le...@ta...> - 2005-05-18 11:15:50
|
Ivan,
I actually tried really hard to cut down on this exact question by
putting the
Advice into the log output that you posted below. This is a configuration
problem with your choice of main class. You want to be using one of the
helper classes. Take 10 minutes and read over the integration section
as suggested in the logs.
If you have any questions after looking over the docs, I'd love to help.
Cheers,
Leif
Berg, Ivan Michael (Ivan) wrote:
> Hey all,
>
> FYI, not on the mailing list, so please reply directly to
> iva...@av... <mailto:iva...@av...>
>
> Just started using the wrapper, looks like a nice program, so thanks
> for the hard work putting it together.
>
> I am a newbie trying to integrate into a java watchdog program that:
> a. Starts up and does some initialization (very quick)
> b. Polls to get a status (success/fail)
> c. Goes to sleep via Thread.sleep for a time period. Usually > 30 seconds
> d. Wakes up and polls again, might do some action based on this
> e. Rinse, repeat
>
> I tried to integrate via Method 1, but it looks like the sleep is
> messing up with the health checking with the JSW.
>
> I set the following:
> # Number of seconds to allow between the wrapper pinging the JVM and
> the response
> wrapper.ping.timeout=60
>
> But it didn't seem to have much affect
>
> Got something like:
> 2005-05-17 09:55:26,040 [main] DEBUG WatchDog - Sleeping for 30 seconds
> Waiting to start...
> Waiting to start...
> Waiting to start...
> Waiting to start...
> Waiting to start...
> Startup failed: Timed out waiting for a signal from the JVM.
>
> ------------------------------------------------------------------------
> Advice:
> The Wrapper consists of a native component as well as a set of classes
> which run within the JVM that it launches. The Java component of the
> Wrapper must be initialized promptly after the JVM is launched or the
> Wrapper will timeout, as just happened. Most likely the main class
> specified in the Wrapper configuration file is not correctly initializing
> the Wrapper classes:
> AICWatchDog
> While it is possible to do so manually, the Wrapper ships with helper
> classes to make this initialization processes automatic.
> Please review the integration section of the Wrapper's documentation
> for the various methods which can be employed to launch an application
> within the Wrapper:
> http://wrapper.tanukisoftware.org/doc/english/integrate.html
> ------------------------------------------------------------------------
>
> JVM did not exit on request, terminated
> Waiting to start...
> Launching a JVM...
>
> So, I was looking for some advice, is there something I can play with
> in the config parameters to handle this better?
> Will moving to integration Method 3 help?
> Any other ideas?
>
> Thanks, Ivan
>
>
|