|
From: <b.v...@va...> - 2005-12-11 20:58:20
|
Hello, I've installed the wrapper on a VPS server, behind the apache web server, to keep a tomcat 4.1 going. This goes fine, but sometimes, after maybe 2 restarts, tomcat doesn't restart properly anymore. When connecting with a browser, an "internal server error" is given. The wrapper console gives correct ping signals. a wrapper "restart" command doesn't make it work anymore. However, when I do a "wrapper stop" and then a "wrapper start", it starts working correctly again. Is there any explanation for this? Is there some way I could simulate "wrapper stop" and "wrapper start" as 2 separate steps? Regards, Bo van Weert |
|
From: Leif M. <le...@ta...> - 2005-12-12 04:00:16
|
Is anything showing up in any of the Tomcat or Wrapper logs? My first guess would be a problem rebinding to one or more ports. Some UNIX platforms lock ports for up to 2 minutes before they can be bound again. If that is the problem, you can resolve it by forcing the Wrapper to wait a couple minutes before launching a new JVM: http://wrapper.tanukisoftware.org/doc/english/prop-restart-delay.html wrapper.restart.delay=150 # 2.5 minutes Cheers, Leif b.v...@va... wrote: > > > Hello, > > I've installed the wrapper on a VPS server, behind the apache web server, > to keep a tomcat 4.1 going. > This goes fine, but sometimes, after maybe 2 restarts, tomcat doesn't > restart properly anymore. When connecting with a browser, an "internal > server error" is given. The wrapper console gives correct ping signals. a > wrapper "restart" command doesn't make it work anymore. > However, when I do a "wrapper stop" and then a "wrapper start", it starts > working correctly again. > > Is there any explanation for this? Is there some way I could simulate > "wrapper stop" and "wrapper start" as 2 separate steps? > > Regards, > > > Bo van Weert > |
|
From: <b.v...@va...> - 2005-12-12 17:12:26
|
Hello,
what I notice is that once restarted, the old JVM doesn't disappear. This
is a line of ps:
root 7506 0.0 0.0 0 0 ? Z 05:08 0:00 [java
<defunct>]
Could this cause a problem?
cheers,
Bo van Weert
Leif Mortenson
<leif@tanukisoftw
are.com> To
Sent by: wra...@li...
wrapper-user-admi cc
n...@li...
ge.net Subject
Re: [Wrapper-user] restart problem
12/12/2005 04:59
Please respond to
wrapper-user@list
s.sourceforge.net
Is anything showing up in any of the Tomcat or Wrapper logs? My first
guess would be a
problem rebinding to one or more ports. Some UNIX platforms lock ports
for up to
2 minutes before they can be bound again.
If that is the problem, you can resolve it by forcing the Wrapper to
wait a couple minutes
before launching a new JVM:
http://wrapper.tanukisoftware.org/doc/english/prop-restart-delay.html
wrapper.restart.delay=150 # 2.5 minutes
Cheers,
Leif
b.v...@va... wrote:
>
>
> Hello,
>
> I've installed the wrapper on a VPS server, behind the apache web server,
> to keep a tomcat 4.1 going.
> This goes fine, but sometimes, after maybe 2 restarts, tomcat doesn't
> restart properly anymore. When connecting with a browser, an "internal
> server error" is given. The wrapper console gives correct ping signals. a
> wrapper "restart" command doesn't make it work anymore.
> However, when I do a "wrapper stop" and then a "wrapper start", it starts
> working correctly again.
>
> Is there any explanation for this? Is there some way I could simulate
> "wrapper stop" and "wrapper start" as 2 separate steps?
>
> Regards,
>
>
> Bo van Weert
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
|
|
From: Leif M. <le...@ta...> - 2005-12-14 04:58:00
|
Bo, That is a known problem that has been fixed for the 3.2.0 release. The Wrapper process was not correctly waiting for the child Java process to terminate before continuing and launching the new JVM. It is a timing problem. In most cases it worked fine, but every once in a while the exiting JVM would end up turning into a zombie process. I don't think that was ever preventing the new JVM from being launched, it was just sticking around in the process list eating up resources. I suppose it is possible that the zombie process could still be causing one or more resources to be locked. You might want to try checking out the source from CVS and giving it a try. It is pretty easy to build on Linux. Just run build.sh. Cheers, Leif b.v...@va... wrote: > Hello, > > what I notice is that once restarted, the old JVM doesn't disappear. This > is a line of ps: > root 7506 0.0 0.0 0 0 ? Z 05:08 0:00 [java > <defunct>] > > Could this cause a problem? > > cheers, > > Bo van Weert > > > > > > > Leif Mortenson > <leif@tanukisoftw > are.com> To > Sent by: wra...@li... > wrapper-user-admi cc > n...@li... > ge.net Subject > Re: [Wrapper-user] restart problem > > 12/12/2005 04:59 > > > Please respond to > wrapper-user@list > s.sourceforge.net > > > > > > > Is anything showing up in any of the Tomcat or Wrapper logs? My first > guess would be a > problem rebinding to one or more ports. Some UNIX platforms lock ports > for up to > 2 minutes before they can be bound again. > > If that is the problem, you can resolve it by forcing the Wrapper to > wait a couple minutes > before launching a new JVM: > http://wrapper.tanukisoftware.org/doc/english/prop-restart-delay.html > wrapper.restart.delay=150 # 2.5 minutes > > Cheers, > Leif > > b.v...@va... wrote: > >> Hello, >> >> I've installed the wrapper on a VPS server, behind the apache web server, >> to keep a tomcat 4.1 going. >> This goes fine, but sometimes, after maybe 2 restarts, tomcat doesn't >> restart properly anymore. When connecting with a browser, an "internal >> server error" is given. The wrapper console gives correct ping signals. a >> wrapper "restart" command doesn't make it work anymore. >> However, when I do a "wrapper stop" and then a "wrapper start", it starts >> working correctly again. >> >> Is there any explanation for this? Is there some way I could simulate >> "wrapper stop" and "wrapper start" as 2 separate steps? >> >> Regards, >> >> >> Bo van Weert >> |
|
From: <b.v...@va...> - 2005-12-15 12:26:17
|
Hello, I set the restart time to 2,5 minutes, but there comes a time where the web says "internal server error", while the wrapper successfully receives JVM pings. "tomcat4 restart" does not solve the problem. However, when I call "tomcat4 stop" and then "tomcat4 start" (can be inmediately) I'm up again. So there seems to be a difference between tomcat restart and a separate stop and start. A solution that occurs to me is to write a linux script that checks the web, and in case of failure call stop and start. But that's not too elegant... Regards, Bo van Weert tel. 902 014 180 (00 34) 96 393 19 77 fax. 96 360 69 13 http://www.valbosoft.com Leif Mortenson <leif@tanukisoftw are.com> To Sent by: wra...@li... wrapper-user-admi cc n...@li... ge.net Subject Re: [Wrapper-user] restart problem 14/12/2005 05:57 Please respond to wrapper-user@list s.sourceforge.net Bo, That is a known problem that has been fixed for the 3.2.0 release. The Wrapper process was not correctly waiting for the child Java process to terminate before continuing and launching the new JVM. It is a timing problem. In most cases it worked fine, but every once in a while the exiting JVM would end up turning into a zombie process. I don't think that was ever preventing the new JVM from being launched, it was just sticking around in the process list eating up resources. I suppose it is possible that the zombie process could still be causing one or more resources to be locked. You might want to try checking out the source from CVS and giving it a try. It is pretty easy to build on Linux. Just run build.sh. Cheers, Leif b.v...@va... wrote: > Hello, > > what I notice is that once restarted, the old JVM doesn't disappear. This > is a line of ps: > root 7506 0.0 0.0 0 0 ? Z 05:08 0:00 [java > <defunct>] > > Could this cause a problem? > > cheers, > > Bo van Weert > > > > > > > Leif Mortenson > <leif@tanukisoftw > are.com> To > Sent by: wra...@li... > wrapper-user-admi cc > n...@li... > ge.net Subject > Re: [Wrapper-user] restart problem > > 12/12/2005 04:59 > > > Please respond to > wrapper-user@list > s.sourceforge.net > > > > > > > Is anything showing up in any of the Tomcat or Wrapper logs? My first > guess would be a > problem rebinding to one or more ports. Some UNIX platforms lock ports > for up to > 2 minutes before they can be bound again. > > If that is the problem, you can resolve it by forcing the Wrapper to > wait a couple minutes > before launching a new JVM: > http://wrapper.tanukisoftware.org/doc/english/prop-restart-delay.html > wrapper.restart.delay=150 # 2.5 minutes > > Cheers, > Leif > > b.v...@va... wrote: > >> Hello, >> >> I've installed the wrapper on a VPS server, behind the apache web server, >> to keep a tomcat 4.1 going. >> This goes fine, but sometimes, after maybe 2 restarts, tomcat doesn't >> restart properly anymore. When connecting with a browser, an "internal >> server error" is given. The wrapper console gives correct ping signals. a >> wrapper "restart" command doesn't make it work anymore. >> However, when I do a "wrapper stop" and then a "wrapper start", it starts >> working correctly again. >> >> Is there any explanation for this? Is there some way I could simulate >> "wrapper stop" and "wrapper start" as 2 separate steps? >> >> Regards, >> >> >> Bo van Weert >> ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Wrapper-user mailing list Wra...@li... https://lists.sourceforge.net/lists/listinfo/wrapper-user |