You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Daniel Rubio <dr...@tinet.org> on 2003/03/21 09:48:53 UTC
Problems with tomcat 4.0.1 and 4.1.18
Hi to all
Recently, we updated our Tomcat server from 4.0.1 to 4.1.18.
All was perfect on the first day, but then the new server crashed and I
can't found the cause.
Doing a ps -ef i see lots of tomcat processes that are'nt finalizing,
and when this number arrives to the value we have in acceptCount
variable it stops serving pages.
Here is the error on catalina.out
Mar 20, 2003 9:34:30 PM org.apache.tomcat.util.log.CommonLogHandler log
INFO: All threads are busy, waiting. Please increase maxThreads or check
the servlet status75 75
maxThreads is set to 75 but we haven't more from 2-3 concurrent users so
I think this is not th problem.
We tried to run again the old server, but now we have a very strange
error, we can execute servlets but not jsp pages. Here is the error
received by the browser:
Apache Tomcat/4.0.1 - HTTP Status 503 - Servlet jsp is currently unavailable
this happens too to the examples directory, I think it's not caused by
the application...
I'm going crazy, somebody could help?
Thanks in advance
--
********************************************************
Daniel Rubio Rodríguez
OASI (Organisme Autònom Per la Societat de la Informació)
c/ Assalt, 12
43003 - Tarragona
Tef.: 977.244.007 - Fax: 977.224.517
e-mail: drubio@oasi.org
********************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Problems with tomcat 4.0.1 and 4.1.18
Posted by Daniel Rubio <dr...@tinet.org>.
I can't find where is the problem ... :(
I've installed tomcat 4.0.6 and now all is runnig without problems.
Today I've seen the new stable version notice and it seems like this
problem was solved, but i'll take a time before upgrading again.
Jonathan Eric Miller wrote:
> I think I may be having the same problem as well. I'm running Tomcat in
> standalone mode and I have it configured only for HTTPS. The error message
> that I'm receiving is.
>
> INFO: All threads are busy, waiting. Please increase maxThreads or check the
> servlet status75 75
>
> This is the second time I've seen this. I don't think I've seen the problem
> before upgrading to 4.1.18.
>
> Jon
>
> ----- Original Message -----
> From: "Daniel Rubio" <dr...@tinet.org>
> To: "Tomcat Users List" <to...@jakarta.apache.org>
> Sent: Friday, March 21, 2003 4:19 AM
> Subject: Re: Problems with tomcat 4.0.1 and 4.1.18
>
>
>
>>Is running standalone, we have apache in port 80 but we have a link to
>>the secure area (tomcat, that runs in 8443).
>>
>>Marion McKelvie wrote:
>>
>>>Daniel
>>>
>>>Are you running in standalone mode or with a web server?
>>>
>>>I have seen a similar problem when using 4.1.18, but I think I've traced
>>
> it
>
>>>to Apache 4.0.43 and mod_jk : Apache seems to keep producing child
>>
> processes
>
>>>each of which uses up a mod_jk thread until I get the same error in
>>>catalina.out
>>>
>>>Marion
>>>
>>>-----Original Message-----
>>>From: Daniel Rubio [mailto:drubior@tinet.org]
>>>Sent: 21 March 2003 08:49
>>>To: tomcat-user@jakarta.apache.org
>>>Subject: Problems with tomcat 4.0.1 and 4.1.18
>>>
>>>
>>>Hi to all
>>>
>>>Recently, we updated our Tomcat server from 4.0.1 to 4.1.18.
>>>All was perfect on the first day, but then the new server crashed and I
>>>can't found the cause.
>>>
>>>Doing a ps -ef i see lots of tomcat processes that are'nt finalizing,
>>>and when this number arrives to the value we have in acceptCount
>>>variable it stops serving pages.
>>>
>>>Here is the error on catalina.out
>>>
>>>Mar 20, 2003 9:34:30 PM org.apache.tomcat.util.log.CommonLogHandler log
>>>INFO: All threads are busy, waiting. Please increase maxThreads or check
>>>the servlet status75 75
>>>
>>>maxThreads is set to 75 but we haven't more from 2-3 concurrent users so
>>>I think this is not th problem.
>>>
>>>We tried to run again the old server, but now we have a very strange
>>>error, we can execute servlets but not jsp pages. Here is the error
>>>received by the browser:
>>>
>>>Apache Tomcat/4.0.1 - HTTP Status 503 - Servlet jsp is currently
>>
> unavailable
>
>>>this happens too to the examples directory, I think it's not caused by
>>>the application...
>>>
>>>I'm going crazy, somebody could help?
>>>
>>>Thanks in advance
>>>--
>>>********************************************************
>>>Daniel Rubio Rodríguez
>>>OASI (Organisme Autònom Per la Societat de la Informació)
>>>c/ Assalt, 12
>>>43003 - Tarragona
>>>Tef.: 977.244.007 - Fax: 977.224.517
>>>e-mail: drubio@oasi.org
>>>********************************************************
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>>
>>>
>>
>>
>>--
>>********************************************************
>>Daniel Rubio Rodríguez
>>OASI (Organisme Autònom Per la Societat de la Informació)
>>c/ Assalt, 12
>>43003 - Tarragona
>>Tef.: 977.244.007 - Fax: 977.224.517
>>e-mail: drubio@oasi.org
>>********************************************************
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
--
********************************************************
Daniel Rubio Rodríguez
OASI (Organisme Autònom Per la Societat de la Informació)
c/ Assalt, 12
43003 - Tarragona
Tef.: 977.244.007 - Fax: 977.224.517
e-mail: drubio@oasi.org
********************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Problems with tomcat 4.0.1 and 4.1.18
Posted by Jonathan Eric Miller <je...@uchicago.edu>.
I think I may be having the same problem as well. I'm running Tomcat in
standalone mode and I have it configured only for HTTPS. The error message
that I'm receiving is.
INFO: All threads are busy, waiting. Please increase maxThreads or check the
servlet status75 75
This is the second time I've seen this. I don't think I've seen the problem
before upgrading to 4.1.18.
Jon
----- Original Message -----
From: "Daniel Rubio" <dr...@tinet.org>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Friday, March 21, 2003 4:19 AM
Subject: Re: Problems with tomcat 4.0.1 and 4.1.18
> Is running standalone, we have apache in port 80 but we have a link to
> the secure area (tomcat, that runs in 8443).
>
> Marion McKelvie wrote:
> > Daniel
> >
> > Are you running in standalone mode or with a web server?
> >
> > I have seen a similar problem when using 4.1.18, but I think I've traced
it
> > to Apache 4.0.43 and mod_jk : Apache seems to keep producing child
processes
> > each of which uses up a mod_jk thread until I get the same error in
> > catalina.out
> >
> > Marion
> >
> > -----Original Message-----
> > From: Daniel Rubio [mailto:drubior@tinet.org]
> > Sent: 21 March 2003 08:49
> > To: tomcat-user@jakarta.apache.org
> > Subject: Problems with tomcat 4.0.1 and 4.1.18
> >
> >
> > Hi to all
> >
> > Recently, we updated our Tomcat server from 4.0.1 to 4.1.18.
> > All was perfect on the first day, but then the new server crashed and I
> > can't found the cause.
> >
> > Doing a ps -ef i see lots of tomcat processes that are'nt finalizing,
> > and when this number arrives to the value we have in acceptCount
> > variable it stops serving pages.
> >
> > Here is the error on catalina.out
> >
> > Mar 20, 2003 9:34:30 PM org.apache.tomcat.util.log.CommonLogHandler log
> > INFO: All threads are busy, waiting. Please increase maxThreads or check
> > the servlet status75 75
> >
> > maxThreads is set to 75 but we haven't more from 2-3 concurrent users so
> > I think this is not th problem.
> >
> > We tried to run again the old server, but now we have a very strange
> > error, we can execute servlets but not jsp pages. Here is the error
> > received by the browser:
> >
> > Apache Tomcat/4.0.1 - HTTP Status 503 - Servlet jsp is currently
unavailable
> >
> > this happens too to the examples directory, I think it's not caused by
> > the application...
> >
> > I'm going crazy, somebody could help?
> >
> > Thanks in advance
> > --
> > ********************************************************
> > Daniel Rubio Rodríguez
> > OASI (Organisme Autònom Per la Societat de la Informació)
> > c/ Assalt, 12
> > 43003 - Tarragona
> > Tef.: 977.244.007 - Fax: 977.224.517
> > e-mail: drubio@oasi.org
> > ********************************************************
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> >
>
>
> --
> ********************************************************
> Daniel Rubio Rodríguez
> OASI (Organisme Autònom Per la Societat de la Informació)
> c/ Assalt, 12
> 43003 - Tarragona
> Tef.: 977.244.007 - Fax: 977.224.517
> e-mail: drubio@oasi.org
> ********************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Problems with tomcat 4.0.1 and 4.1.18
Posted by Daniel Rubio <dr...@tinet.org>.
Is running standalone, we have apache in port 80 but we have a link to
the secure area (tomcat, that runs in 8443).
Marion McKelvie wrote:
> Daniel
>
> Are you running in standalone mode or with a web server?
>
> I have seen a similar problem when using 4.1.18, but I think I've traced it
> to Apache 4.0.43 and mod_jk : Apache seems to keep producing child processes
> each of which uses up a mod_jk thread until I get the same error in
> catalina.out
>
> Marion
>
> -----Original Message-----
> From: Daniel Rubio [mailto:drubior@tinet.org]
> Sent: 21 March 2003 08:49
> To: tomcat-user@jakarta.apache.org
> Subject: Problems with tomcat 4.0.1 and 4.1.18
>
>
> Hi to all
>
> Recently, we updated our Tomcat server from 4.0.1 to 4.1.18.
> All was perfect on the first day, but then the new server crashed and I
> can't found the cause.
>
> Doing a ps -ef i see lots of tomcat processes that are'nt finalizing,
> and when this number arrives to the value we have in acceptCount
> variable it stops serving pages.
>
> Here is the error on catalina.out
>
> Mar 20, 2003 9:34:30 PM org.apache.tomcat.util.log.CommonLogHandler log
> INFO: All threads are busy, waiting. Please increase maxThreads or check
> the servlet status75 75
>
> maxThreads is set to 75 but we haven't more from 2-3 concurrent users so
> I think this is not th problem.
>
> We tried to run again the old server, but now we have a very strange
> error, we can execute servlets but not jsp pages. Here is the error
> received by the browser:
>
> Apache Tomcat/4.0.1 - HTTP Status 503 - Servlet jsp is currently unavailable
>
> this happens too to the examples directory, I think it's not caused by
> the application...
>
> I'm going crazy, somebody could help?
>
> Thanks in advance
> --
> ********************************************************
> Daniel Rubio Rodríguez
> OASI (Organisme Autònom Per la Societat de la Informació)
> c/ Assalt, 12
> 43003 - Tarragona
> Tef.: 977.244.007 - Fax: 977.224.517
> e-mail: drubio@oasi.org
> ********************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
--
********************************************************
Daniel Rubio Rodríguez
OASI (Organisme Autònom Per la Societat de la Informació)
c/ Assalt, 12
43003 - Tarragona
Tef.: 977.244.007 - Fax: 977.224.517
e-mail: drubio@oasi.org
********************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RE: Problems with tomcat 4.0.1 and 4.1.18
Posted by Marion McKelvie <ma...@streamlet.co.uk>.
Daniel
Please let me know how you get on. I'm also using RH8 and started with
Apache 2.0.40 but upgraded to 2.0.43 so I could use mod_jk 2.0.43. It may
be associated with Apache 2.0.4x.
Marion
-----Original Message-----
From: Daniel Regenass [mailto:Daniel.Regenass@blue-logic.com]
Sent: 21 March 2003 10:31
To: Tomcat Users List
Subject: RE: Problems with tomcat 4.0.1 and 4.1.18
Hi,
I recently moved one of our servers to RH 8.0. In the same
step I also tried to move the affected application to Tomcat
4.1.18, working together with Apache 2.0.40 by using mod_jk 1.2.2.
Everything went fine except that after about a day, Tomcat seems to
have problems. The effects were:
- OutOfMemory Exceptions
- No more responds from Tomcat
- Error 500's
The effects changed as I was trying different versions of Apache
JDK and JK versions etc., but it seems to me that these results are
caused by always the same problem: The connections between Apache
and Tomcat seem to be created once, not used again and not destroyed anymore
resulting in a huge amount of hanging threads, filling up memory
etc. It usually took about a day until the problem occurred, but
of course, this depends on the number of requests, amount of memory
and the application itself.
Currently, I'm trying JDK 1.3.1_07. Will see if it fixes the problem.
Someone mentioned that before in this mailinglist.
Typical log outputs of JkCoyoteHandler:
.
.
[INFO] ChannelSocket - -Server has been restarted or reset this connection
[INFO] ChannelSocket - -connection timeout reached
.
.
and corresponding to that by mod_jk:
.
.
[Fri Mar 21 01:13:47 2003] [jk_ajp_common.c (1050)]: Error reading reply
from tomcat. Tomcat is down or network problems.
[Fri Mar 21 01:13:47 2003] [jk_ajp_common.c (1187)]: ERROR: Receiving from
tomcat failed, recoverable operation. err=0
[Fri Mar 21 01:13:50 2003] [jk_ajp_common.c (681)]: ERROR: can't receive
the response message from tomcat, network problems or tomcat is down.
.
.
Regards,
Daniel
> -----Original Message-----
> From: Marion McKelvie [mailto:marion@streamlet.co.uk]
> Sent: Freitag, 21. März 2003 10:58
> To: Tomcat Users List
> Subject: RE: Problems with tomcat 4.0.1 and 4.1.18
>
>
> Daniel
>
> Are you running in standalone mode or with a web server?
>
> I have seen a similar problem when using 4.1.18, but I think I've
> traced it
> to Apache 4.0.43 and mod_jk : Apache seems to keep producing
> child processes
> each of which uses up a mod_jk thread until I get the same error in
> catalina.out
>
> Marion
>
> -----Original Message-----
> From: Daniel Rubio [mailto:drubior@tinet.org]
> Sent: 21 March 2003 08:49
> To: tomcat-user@jakarta.apache.org
> Subject: Problems with tomcat 4.0.1 and 4.1.18
>
>
> Hi to all
>
> Recently, we updated our Tomcat server from 4.0.1 to 4.1.18.
> All was perfect on the first day, but then the new server crashed and I
> can't found the cause.
>
> Doing a ps -ef i see lots of tomcat processes that are'nt finalizing,
> and when this number arrives to the value we have in acceptCount
> variable it stops serving pages.
>
> Here is the error on catalina.out
>
> Mar 20, 2003 9:34:30 PM org.apache.tomcat.util.log.CommonLogHandler log
> INFO: All threads are busy, waiting. Please increase maxThreads or check
> the servlet status75 75
>
> maxThreads is set to 75 but we haven't more from 2-3 concurrent users so
> I think this is not th problem.
>
> We tried to run again the old server, but now we have a very strange
> error, we can execute servlets but not jsp pages. Here is the error
> received by the browser:
>
> Apache Tomcat/4.0.1 - HTTP Status 503 - Servlet jsp is currently
> unavailable
>
> this happens too to the examples directory, I think it's not caused by
> the application...
>
> I'm going crazy, somebody could help?
>
> Thanks in advance
> --
> ********************************************************
> Daniel Rubio Rodríguez
> OASI (Organisme Autònom Per la Societat de la Informació)
> c/ Assalt, 12
> 43003 - Tarragona
> Tef.: 977.244.007 - Fax: 977.224.517
> e-mail: drubio@oasi.org
> ********************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RE: Problems with tomcat 4.0.1 and 4.1.18
Posted by Daniel Regenass <Da...@blue-logic.com>.
Hi,
I recently moved one of our servers to RH 8.0. In the same
step I also tried to move the affected application to Tomcat
4.1.18, working together with Apache 2.0.40 by using mod_jk 1.2.2.
Everything went fine except that after about a day, Tomcat seems to
have problems. The effects were:
- OutOfMemory Exceptions
- No more responds from Tomcat
- Error 500's
The effects changed as I was trying different versions of Apache
JDK and JK versions etc., but it seems to me that these results are
caused by always the same problem: The connections between Apache
and Tomcat seem to be created once, not used again and not destroyed anymore
resulting in a huge amount of hanging threads, filling up memory
etc. It usually took about a day until the problem occurred, but
of course, this depends on the number of requests, amount of memory
and the application itself.
Currently, I'm trying JDK 1.3.1_07. Will see if it fixes the problem.
Someone mentioned that before in this mailinglist.
Typical log outputs of JkCoyoteHandler:
.
.
[INFO] ChannelSocket - -Server has been restarted or reset this connection
[INFO] ChannelSocket - -connection timeout reached
.
.
and corresponding to that by mod_jk:
.
.
[Fri Mar 21 01:13:47 2003] [jk_ajp_common.c (1050)]: Error reading reply
from tomcat. Tomcat is down or network problems.
[Fri Mar 21 01:13:47 2003] [jk_ajp_common.c (1187)]: ERROR: Receiving from
tomcat failed, recoverable operation. err=0
[Fri Mar 21 01:13:50 2003] [jk_ajp_common.c (681)]: ERROR: can't receive
the response message from tomcat, network problems or tomcat is down.
.
.
Regards,
Daniel
> -----Original Message-----
> From: Marion McKelvie [mailto:marion@streamlet.co.uk]
> Sent: Freitag, 21. März 2003 10:58
> To: Tomcat Users List
> Subject: RE: Problems with tomcat 4.0.1 and 4.1.18
>
>
> Daniel
>
> Are you running in standalone mode or with a web server?
>
> I have seen a similar problem when using 4.1.18, but I think I've
> traced it
> to Apache 4.0.43 and mod_jk : Apache seems to keep producing
> child processes
> each of which uses up a mod_jk thread until I get the same error in
> catalina.out
>
> Marion
>
> -----Original Message-----
> From: Daniel Rubio [mailto:drubior@tinet.org]
> Sent: 21 March 2003 08:49
> To: tomcat-user@jakarta.apache.org
> Subject: Problems with tomcat 4.0.1 and 4.1.18
>
>
> Hi to all
>
> Recently, we updated our Tomcat server from 4.0.1 to 4.1.18.
> All was perfect on the first day, but then the new server crashed and I
> can't found the cause.
>
> Doing a ps -ef i see lots of tomcat processes that are'nt finalizing,
> and when this number arrives to the value we have in acceptCount
> variable it stops serving pages.
>
> Here is the error on catalina.out
>
> Mar 20, 2003 9:34:30 PM org.apache.tomcat.util.log.CommonLogHandler log
> INFO: All threads are busy, waiting. Please increase maxThreads or check
> the servlet status75 75
>
> maxThreads is set to 75 but we haven't more from 2-3 concurrent users so
> I think this is not th problem.
>
> We tried to run again the old server, but now we have a very strange
> error, we can execute servlets but not jsp pages. Here is the error
> received by the browser:
>
> Apache Tomcat/4.0.1 - HTTP Status 503 - Servlet jsp is currently
> unavailable
>
> this happens too to the examples directory, I think it's not caused by
> the application...
>
> I'm going crazy, somebody could help?
>
> Thanks in advance
> --
> ********************************************************
> Daniel Rubio Rodríguez
> OASI (Organisme Autònom Per la Societat de la Informació)
> c/ Assalt, 12
> 43003 - Tarragona
> Tef.: 977.244.007 - Fax: 977.224.517
> e-mail: drubio@oasi.org
> ********************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RE: Problems with tomcat 4.0.1 and 4.1.18
Posted by Marion McKelvie <ma...@streamlet.co.uk>.
Daniel
Are you running in standalone mode or with a web server?
I have seen a similar problem when using 4.1.18, but I think I've traced it
to Apache 4.0.43 and mod_jk : Apache seems to keep producing child processes
each of which uses up a mod_jk thread until I get the same error in
catalina.out
Marion
-----Original Message-----
From: Daniel Rubio [mailto:drubior@tinet.org]
Sent: 21 March 2003 08:49
To: tomcat-user@jakarta.apache.org
Subject: Problems with tomcat 4.0.1 and 4.1.18
Hi to all
Recently, we updated our Tomcat server from 4.0.1 to 4.1.18.
All was perfect on the first day, but then the new server crashed and I
can't found the cause.
Doing a ps -ef i see lots of tomcat processes that are'nt finalizing,
and when this number arrives to the value we have in acceptCount
variable it stops serving pages.
Here is the error on catalina.out
Mar 20, 2003 9:34:30 PM org.apache.tomcat.util.log.CommonLogHandler log
INFO: All threads are busy, waiting. Please increase maxThreads or check
the servlet status75 75
maxThreads is set to 75 but we haven't more from 2-3 concurrent users so
I think this is not th problem.
We tried to run again the old server, but now we have a very strange
error, we can execute servlets but not jsp pages. Here is the error
received by the browser:
Apache Tomcat/4.0.1 - HTTP Status 503 - Servlet jsp is currently unavailable
this happens too to the examples directory, I think it's not caused by
the application...
I'm going crazy, somebody could help?
Thanks in advance
--
********************************************************
Daniel Rubio Rodríguez
OASI (Organisme Autònom Per la Societat de la Informació)
c/ Assalt, 12
43003 - Tarragona
Tef.: 977.244.007 - Fax: 977.224.517
e-mail: drubio@oasi.org
********************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Problems with tomcat 4.0.1 and 4.1.18
Posted by Micael <ca...@harbornet.com>.
The two are likely the same problem. Do you have something that might be
spawning threads in your application?
At 09:48 AM 3/21/03 +0100, you wrote:
>Hi to all
>
>Recently, we updated our Tomcat server from 4.0.1 to 4.1.18.
>All was perfect on the first day, but then the new server crashed and I
>can't found the cause.
>
>Doing a ps -ef i see lots of tomcat processes that are'nt finalizing, and
>when this number arrives to the value we have in acceptCount variable it
>stops serving pages.
>
>Here is the error on catalina.out
>
>Mar 20, 2003 9:34:30 PM org.apache.tomcat.util.log.CommonLogHandler log
>INFO: All threads are busy, waiting. Please increase maxThreads or check
>the servlet status75 75
>
>maxThreads is set to 75 but we haven't more from 2-3 concurrent users so I
>think this is not th problem.
>
>We tried to run again the old server, but now we have a very strange
>error, we can execute servlets but not jsp pages. Here is the error
>received by the browser:
>
>Apache Tomcat/4.0.1 - HTTP Status 503 - Servlet jsp is currently unavailable
>
>this happens too to the examples directory, I think it's not caused by the
>application...
>
>I'm going crazy, somebody could help?
>
>Thanks in advance
>--
>********************************************************
>Daniel Rubio Rodríguez
>OASI (Organisme Autònom Per la Societat de la Informació)
>c/ Assalt, 12
>43003 - Tarragona
>Tef.: 977.244.007 - Fax: 977.224.517
>e-mail: drubio@oasi.org
>********************************************************
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>
LEGAL NOTICE
This electronic mail transmission and any accompanying documents contain
information belonging to the sender which may be confidential and legally
privileged. This information is intended only for the use of the
individual or entity to whom this electronic mail transmission was sent as
indicated above. If you are not the intended recipient, any disclosure,
copying, distribution, or action taken in reliance on the contents of the
information contained in this transmission is strictly prohibited. If you
have received this transmission in error, please delete the message. Thank
you
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org