tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Lin <wool...@gmail.com>
Subject Re: tomcat crash ... "unexpected exception"
Date Wed, 23 Jun 2004 12:36:06 GMT
by default, the max threads is set to 150 in server.xml.  Is your
webserver really getting that many active requests at one time?  I've
worked on some large sites and most of the time, the peak concurrent
requests is usually less than 10. this is on some big Sun boxes.

just because there are 150 threads, not all of them are active. If
you're using tomcat5, you can use the status servlet to see how many
threads are active compared to the total threads.

peter


On Wed, 23 Jun 2004 14:24:35 +0200, bastien.devos@bpo.be
<bastien.devos@bpo.be> wrote:
> 
> Again about my general problem, below is an output of the 'top' command on the webserver.
> We can see that the Tomcat java process (the first one) has 135 threads in it. How is
this
> defined ? I guess this number is dynamic, but how can I say that it is its maximum or
not
> ? If it is, it may be some kind of bottleneck ...
> 
> Is it related to the settings of min/max processors in server.xml ?
> 
> ----------------------
> last pid: 14592;  load averages:  0.27,  0.25,  0.26
>                                                14:14:21
> 173 processes: 165 sleeping, 7 zombie, 1 on cpu
> CPU states: 91.5% idle,  3.9% user,  4.2% kernel,  0.4% iowait,  0.0% swap
> Memory: 8192M real, 1404M free, 6472M swap in use, 7856M swap free
> 
>    PID USERNAME THR PRI NICE  SIZE   RES STATE    TIME    CPU COMMAND
>  11751 userx    135   0   10 6288M 4718M sleep    9:55  0.60% java
>    680 root       4 150  -20 3568K 2424K sleep  489:23  0.13%
>  14526 root       1 150  -20 2056K 1472K sleep    0:00  0.06%
>  14527 root       1 150  -20 2056K 1472K sleep    0:00  0.06%
>   5078 root      12   1    0 7312K 6272K sleep   72:41  0.05%
>   8529 root       1  59    0 2776K 1848K cpu/0    0:08  0.05% top
>  14513 userx      8   1    0 7280K 5864K sleep    0:00  0.05% httpd
>  14591 userx      6   0    0 6848K 5112K sleep    0:00  0.03% httpd
>  14524 root       1 150  -20 2056K 1472K sleep    0:00  0.03%
>  14592 userx      4   0    0 6720K 5016K sleep    0:00  0.02% httpd
>  14533 root       1 150  -20 2176K 1408K sleep    0:00  0.02%
>  14534 root       1 150  -20 2176K 1408K sleep    0:00  0.02%
> ----------------------
> 
> Thanks,
> 
> Bastien.
> 
> Ralph Einfeldt wrote:
> > That error can something between 'ignore it' and 'severe error'.
> >
> > Tomcat failed while writing the response to mod_jk.
> > That can be caused by this reasons:
> > - the apache child that created the request died
> > - the user closed the browser before the response was sent
> > - there may be further reasons
> >
> >
> >>-----Original Message-----
> >>From: bastien.devos@bpo.be [mailto:bastien.devos@bpo.be]
> >>Sent: Wednesday, June 23, 2004 11:39 AM
> >>To: Tomcat Users List
> >>Subject: Re: tomcat crash ... "unexpected exception"
> >>
> >
> >
> >>Jun 23, 2004 11:17:12 AM org.apache.jk.server.JkCoyoteHandler action
> >>SEVERE: Error in action code
> >>java.net.SocketException: Broken pipe
> >
> >
> > ---------------------------------------------------------------------
> > 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


Mime
View raw message