Matthew,
In general, setting the timeouts to 0 is a very bad idea. You will most
likely get the
same behavior if you run from a console. Could you post the full debug
log output
from a single JVM invocation along with your wrapper.conf file? Comment
out the
timeouts before the run.
I should be able to tell you how to fix it with that information.
Cheers,
Leif
Matthew Vegh wrote:
> Hi,
>
> I have recently upgraded to version 3.1.2 (from 2.2.3 I think) and
> I’ve run into a confusing problem. Despite the presence of the
> following properties in the .conf file, timeouts are occurring. The
> timeouts take approximately 5 minutes and iterate 5 times; on
> Unix-flavored machines this is a medium-sized problem, on Windows,
> this blocks Windows startup, adding 30 minutes to the blank screen
> before your typical user sees his login dialog.
>
> Relevant properties:
>
> wrapper.startup.timeout=0
>
> wrapper.ping.timeout=0
>
> Log section:
>
> ERROR | wrapper | 2005/05/03 14:52:22 | Startup failed: Timed out
> waiting for signal from JVM.
>
> ERROR | wrapper | 2005/05/03 14:52:22 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper | 2005/05/03 14:52:27 | Launching a JVM...
>
> INFO | jvm 2 | 2005/05/03 14:52:30 | Wrapper (Version 3.1.2)
> http://wrapper.tanukisoftware.org <http://wrapper.tanukisoftware.org/>
>
> INFO | jvm 2 | 2005/05/03 14:52:30 |
>
> I should mention that the extra information from setting
> wrapper.debug=true hasn’t provided any clues. I’ve also tried
> switching the JVM (Sun/Jrockit) to no gain. I have double and
> triple-checked the formatting of the configuration file, as well as
> setting all of the timeout-related properties to 0 (disabled). I
> haven’t seen any similar bugs/issues posted, so I’m a bit concerned.
>
> If anyone has any suggestions/solutions, I would be forever in your debt.
>
> Thanks,
>
> Matt
>
|
