Does this mean that the proposed patch to call setSoTimeout() should not be
applied?
> -----Original Message-----
> From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 20, 2001 10:12 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Bug 1006, what's next ?
>
>
> Hi,
>
> I may help here since I figth against this kind of TCP
> bugs each days on my pay job.
>
> The problem with TCP/IP is that when there is no activity a
> read() system call (that java used) will block the calling
> thread.
>
> You could use :
>
> - select() like before read() to see if there is something to
> get. Also on Unix there is many ioctl() for that task (FIONREAD).
> But equivalent call are only present in JDK 1.3
>
> - you could set the socket to non blocking and add a timeout to
> read (ie 1 second), but you'll have after that to create a kind
> of Super read() method with the intelligence to know that a HTTP
> request must'nt take more than 5/10 seconds.
>
> - You may use something like an Apache server in front of you tomcat
> which as built-in support against that kind of potential DOS attack.
>
> I could try to fix that one ...
>
> >-----Original Message-----
> >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> >Sent: Tuesday, March 20, 2001 4:03 PM
> >To: [EMAIL PROTECTED]
> >Subject: Re: Bug 1006, what's next ?
> >
> >
> >Hi,
> >
> >I had a (long) weekend without computers. But I still found
> >one and read
> >the mail once - and your report is very serious and important ( and not
> >easy to fix ). You have (at least ) my full attention. The read
> >timeout will be checked in soon - but the general problem (
> >with a servlet
> >hanging a thread ) is very hard to resolve (or I don't know any good
> >solution ).
> >
> >We could stop setting an upper limit on the thread count ( we
> >still have
> >the OS upper limit ), and we could also use the (dangerous,
> >deprecated) suspend/terminate on the thread that is taking too
> >much time.
> >
> >Have you tried any fix ? The timeout will not resolve the
> >"bursts" ( and
> >high-loaded servers ) - unless it is very short.
> >
> >BTW, this is not a tomcat-specific problem ( I would guess Apache does
> >have the same issue - and we need to find how they deal with that ).
> >
> >Costin
> >
> >
> >On Tue, 20 Mar 2001, Tal Dayan wrote:
> >
> >>
> >> Two days ago I filed a bug report regarding a sever hanging
> >problem in
> >> PollTcpEndpoint of Tomcat 3.x. The bug is
> >> at http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1006
> >and also include a
> >> suggestion for a patch.
> >>
> >> Since then I did not notice any change in the status or
> >resolution of the
> >> bug report nor any
> >> indication that it got anywhere.
> >>
> >> 1. Is this is the right place to file the bug ?
> >>
> >> 2. Is the bug filed correctly ?
> >>
> >> 3. Should I do anything else to make sure the bug gets the
> >attention of the
> >> relevant maintainers ?
> >>
> >> Thanks,
> >>
> >> Tal
> >>
> >>
> >
