----- Original Message -----
From: "Remy Maucherat" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Friday, September 12, 2003 1:38 AM
Subject: Re: cvs commit:

> Bill Barker wrote:
> >>On 12 Sep 2003, <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>> +++ PoolTcpEndpoint.java 12 Sep 2003 03:51:36 -0000 1.16
> >>> @@ -389,12 +389,12 @@
> >>>              if (accepted != null) {
> >>>                  try {
> >>>                      accepted.close();
> >>> -                    accepted = null;
> >>>                  } catch(Exception ex) {
> >>>                      msg = sm.getString("endpoint.err.nonfatal",
> >>>                                         accepted, ex);
> >>>                      log.warn(msg, ex);
> >>>                  }
> >>> +                accepted = null;
> >>>              }
> >>>
> >>>              if( ! running ) return null;
> >>
> >>wouldn't it be better to put the "accepted = null" into a finally
> >>block so you clean up even in the (unlikely but possible) case where
> >>close throws an Error (or Throwable) instead of an Exception?
> >
> > Wouldn't do anything.  The 'accepted' variable is local to the
> > so it goes away if I throw clear of the method.  In this case you just
get a
> > DoS condition where no threads are listening on the ServerSocket.  I
> > thought about changing the catch to 'Throwable', but is it really
> > for Socket.close to throw anything other than an Exception?
> I don't know. From traces I saw, there are conditions where there could
> be no thread listening on the socket (at that point, the connector was
> dead, of course), while everything else in the TP was looking ok
> (including no deadlock). There didn't seem to be anything in the logs
> related to an error during accept.

If you max out the threads, then the thread that is waiting in ThreadPool is
the one that will do the next accept.  It's supposed to be a temporary
condition (since a thread should get returned to to Pool soon).  Porting the
connectionTimeout throttling back to 4.1 should make it more responsive in
this case (since Tomcat will stop doing keep-alives).  Of course, what it's
really telling you is that your maxProcessors is set too low :).

> I'd catch throwable just to be safe, personally :)

I'll catch throwable then.

> Remy
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

This message is intended only for the use of the person(s) listed above as the 
intended recipient(s), and may contain information that is PRIVILEGED and 
CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or 
distribute this message or any attachment. If you received this communication in 
error, please notify us immediately by e-mail and then delete all copies of this 
message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the 
Internet is not secure. Do not send confidential or sensitive information, such as 
social security numbers, account numbers, personal identification numbers and 
passwords, to us via ordinary (unencrypted) e-mail.

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to