Hosted by:

wrapper.startup.timeout Property

wrapper.startup.timeout Property

Configuration Property Overview

- Configuration Property Overview
- Advanced Properties
- Property List by Name

wrapper.startup.timeout

Number of seconds to allow between the time that the Wrapper launches the JVM process and the time that the JVM side of the Wrapper responds that the application has started. 0 means never time out. Defaults to 30 seconds.

If you are experiencing timeout problems as your application is starting up. The most common cause is a misconfiguration. Please verify that the `WrapperManager` is indeed being started. You should see the following output in the console when you launch the Wrapper.

    wrapper  | --> Wrapper Started as Console
    wrapper  | Launching a JVM...
    jvm 1    | Wrapper (Version 3.x.x)

If you do not see the Wrapper version displayed, then the `WrapperManager` is not being launched. Please make sure that you have read over the Integration section. If the configuration looks correct, then try enabling DEBUG level log output to try and narrow in on the problem.

If the Wrapper version is being displayed, but the Wrapper is still timing out on startup, then it is most likely being caused by one of two things. The first is that the start method call is not returning. This should not be an issue if you are using the `SimpleWrapperApp` or `SimpleStartStopApp` classes to launch your application. If you are implementing the `WrapperListener` however, please verify that the `start` method is indeed returning upon completion. You should be able to see this with `DEBUG` output enabled.

The other possibility is that the startup method is simply taking a while to complete. In this case, it may be necessary to extend the default startup timeout. Try setting to to 300 (5 minutes) and see if that makes the problem go away.

It is best to choose a value which is long enough to let the application start reliably, but short enough that the Wrapper will react as quickly as possible in the event of an actual JVM hang.

If the start procedure sometimes takes a long time. One alternative to setting a long timeout is to periodically call the `WrapperManager.signalStarting(n)` method. This method gives the application the ability to request more time to startup, while at the same time assuring the Wrapper that the JVM is alive and well.

Example:

    wrapper.startup.timeout=30

WARNING |  | While the ability is there. Be aware that setting this property to 0 or some large value will mean that the Wrapper's ability to detect a JVM hang during the startup phase will be disabled.

by Leif Mortenson

Copyright ©1999-2004 by Tanuki Software. All Rights Reserved. | last modified: