well, its not the whole solution, but it could eliminate buggy servlet/filter code and/or buggy client code(since it is a custom client, not a browser).
this is a way to cut the problem in half and determine which side the problem occurs on - sending/receiving the request or processing the request. if rdv shows 2 unique requests, then the problem is in the servlet OR tomcat's processing/invocation of that servlet. if rdv shows 2 similar requests, it could be a problem with the client OR tomcat's code to receive and assign to a thread for the engine. Side note: any filters in this process? filters must also be written to be thread safe. I don't recall seeing a web.xml. Charlie > -----Original Message----- > From: Mike W-M [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 17, 2002 9:28 AM > To: Tomcat Users List > Subject: Re: Simultaneous request from same IP > > > A sensible investigation, granted, but there's a flaw in your > argument! > The current hypothesis is that two different requests are > getting confused > and giving the same values. So if the RequestDumperValve > shows the same > values for both requests then how will you know whether they > originated as > identical requests or whether they're different requests that > have been > confused???? > > Mike :-) > > > ----- Original Message ----- > From: "Cox, Charlie" <[EMAIL PROTECTED]> > To: "'Tomcat Users List'" <[EMAIL PROTECTED]> > Sent: Tuesday, December 17, 2002 2:01 PM > Subject: RE: Simultaneous request from same IP > > > this goes along with the suggestion I made of using > RequestDumperValve to > dump the request to ensure that you are receiving 2 different > requests. > > Charlie > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
