Re: [Wrapper-user] Wrapper fails to start after JVM timeout - Needs server reboot to fix

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

Justin,
We have run several tests and made some modifications to make the
Wrapper a bit more responsive in the event that the backend socket is
ever closed externally.  These changes will be in the next release.

This is will not be all that helpful for you however as your
application is failing to start back up and after the restart.  Most
likely the reason is can't be restarted is related to the reason why
the backend socket was closed in the first place.

The way the Wrapper is failing to send any data back to the JVM AFTER
the Wrapper has been restarted once is quite odd.  Is it possible that
McAfee or a firewall is somehow deciding to lock down the Wrapper or
Java processes?

Everything else appears to be working as expected.

Please take a look at McAfee on your end, and we will try to think of
other possible causes.

Cheers,
Leif

On Tue, Jun 1, 2010 at 3:02 PM, Justin Maguire <jma...@gm...> wrote:
> Hello Leif,
>
> The successful start up was after a phyical server reboot, everything else
> is before. We have disabled the virus scanner McAfee but I will double check
> that the IT team disabled it or jsut disabled some parts of it :)
>
> I will also escalate here to development as to why that error was throwing
> in the Application to help further troubleshoot this. I am all for the
> upgrading to the latest and greatest I will see if we can get this done.
>
> The machine is a 64bit windows server with 32gb of memory, but I will double
> check the resources next time the error occurs just in case.
>
> Thanks for the insight and explainations this has help me better understand
> the problem.
>
>
> Thanks!
> Justin

-- 
Leif Mortenson
Tanuki Software, Ltd.
6-16-7-1001 Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel/Fax: +81-3-3878-3211
http://www.tanukisoftware.com
lei...@ta...