Re: [Wrapper-user] JVM Timeout

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

99.99999% of the time users post about this problem it is a result of not
having read the integration section of the manual. Please confirm that you
have done so. The Wrapper requires that a WrapperManager class be
loaded and initialized on the JVM side. There are 3 basic ways of doing
that, all of which are covered in detail in the integration section.

I am not trying to be sarcastic here. But this is the most common question
asked by new users. I would love to be able to avoid answering this same
question a few hundred more times and I am sure that other new users
would love to avoid having to ask it.

You have obviously spent some time looking around if you found the
timeouts. So my question to you is what could I have done in the
documentation or sample config file to have directed you more quickly
to the integration section of the manual?

By the way, reset all of the changes to the timeouts that you have made so
far. Most likely you do not want those changes in there.

Cheers,
Leif

C B wrote:

>
> I've got the wrapper succesfully starting my application but it times
> out everytime and attempts to re-start. I tried changing the timeout &
> interval and that didn't seem to make a difference. My CPU is well
> below 100% and the JVM is definitely still running.
>
> Any thoughts on what my issue may be? How exactly is the JVM pinging
> accomplished?
>
> Thank you.