Here is one of the responses I've got on the dev list.
-----Original Message-----
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 18, 2001 1:18 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Tomcat & Frames
Servers don't know anything about frames. The only relevance it has in
this context is the fact that your browser will typically do multiple
requests (one per frame) simultaneously, up to some maximum -- typically
4. This is the same reason you see multiple images being downloaded
simultaneously (these are also done on separate requests). In most
browsers, the number of simultaneous requests is configurable somewhere.
The server is reporting "connection reset by peer" in the middle of a
request. That means one of the following things:
* The browser started a request and the user pressed STOP.
* The browser started an request in one frame and
JavaScript on another frame told it to go somewhere else (which
has the same effect as a user pressing STOP).
* You have a meta refresh reload someplace that is firing so fast that
the previous request hasn't had a chance to complete yet. The five
second periodicity makes me pretty suspicious of this.
* You have some network component in between (a router or proxy) that
is misbehaving.
* You have some completely separate connection attempts going on that
are disobeying the HTTP protocol (such as doing a telnet connection
to port 8080 and then disconnecting).
Craig
On Wed, 18 Jul 2001, Cory Powers wrote:
> That is what I would have thought to but, as I noted in the bug report, I
> can reproduce the error in IE and Netscape on multiple platforms(different
> versions of Windows and Linux). Please take a look at this, I think there
is
> a real issue here. I'm trying to investigate deeper but this is my first
> expirence with tomcat so I need figure out the code before I could really
> make any progress. Any pointers on where to look would be greatly
> appreciated.
>
> BTW I have posted this to the user list and recieved reports of other
users
> having the same issue but, the only resolution was to restart the server
and
> this did not work for me, strange...
>
> Thanks,
> Cory
> [EMAIL PROTECTED]
>
> -----Original Message-----
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 18, 2001 11:59 AM
> To: '[EMAIL PROTECTED]'
> Subject: Re: Tomcat & Frames
>
>
> First, because servlet containers (and web servers, for that matter) don't
> have a clue about frames, it's 99.9% sure to be either an application
> error, a browser bug, or else a harmless warning that the browser
> stopped downloading one frame because some JavaScript in the page told it
> to do so.
>
> Second, these sorts of issues are better discussed on the TOMCAT-USER
> mailing list.
>
> Craig McClanahan
>
> On Mon, 16 Jul 2001, Cory Powers wrote:
>
> > I am having issues using Tomcat with a frameset page that contains 4
> frames,
> > I do not have any problems with the same page when I reduce it to 3
> frames.
> > I have created a Bug in the Bugs Database(Bug #2605) and gotten no
> response.
> > Can someone please assist me in getting this solved. The Bug entry has a
> lot
> > more detail.
> >
> > Thanks,
> > Cory
> > [EMAIL PROTECTED]
> >
>
