tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arieh Markel <Arieh.Mar...@central.sun.com>
Subject Re: More problems with migration to 3.2
Date Sat, 26 Aug 2000 00:00:06 GMT

> Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
> X-No-Archive: yes
> list-help: <mailto:tomcat-dev-help@jakarta.apache.org>
> list-unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> list-post: <mailto:tomcat-dev@jakarta.apache.org>
> Delivered-To: mailing list tomcat-dev@jakarta.apache.org
> From: Arieh Markel <Arieh.Markel@central.sun.com>
> Subject: Re: More problems with migration to 3.2
> To: tomcat-dev@jakarta.apache.org
> Content-MD5: DeNKe/uNStkQmKYdM2vzZg==
> X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N
> 
> 
> > Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
> > X-No-Archive: yes
> > list-help: <mailto:tomcat-dev-help@jakarta.apache.org>
> > list-unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
> > list-post: <mailto:tomcat-dev@jakarta.apache.org>
> > Delivered-To: mailing list tomcat-dev@jakarta.apache.org
> > From: cmanolache@yahoo.com
> > To: tomcat-dev@jakarta.apache.org
> > Subject: Re: More problems with migration to 3.2
> > X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N
> > 
> > > Just to clarify what our application does:
> > >
> > >  . the working screen of the browser is composed of some 9 different
> > >    frames
> > 
> > That looks like a good test case.
> > I do "ab" tests quite often, and it all requests seem to be
> > served ( and return data).
> > 
> > > What I see is that when launching servlets the warning of 'document
> > > contained no data' is popped.
> > 
> > One thing you can try is to add a log()/println in the
> > HttpServletResponseAdapter, and maybe in ContextManager,
> > at the flush() after the request is processed.
> 
> I performed the following instrumentation:
> 
> 	service/http/HttpResponseAdapter: I added a flushBuffer() method
> 		on which I print the fact that I got there and invoke
> 		the superclass (Response) method.
> 		I also instrumented the doWrite() method to output the
> 		number of bytes being printed.
> 		
> 	core/ContextManager: I add print statement to indicate that
> 		request servicing had finished
> 		
> What I found is the following:
> 
> . the ContextManager finished processing the request
> . the Adapter flushBuffer method was never called.
> . the Adapter doWrite() method was not called consistently (it was called
>   to present the initial login screen, it was called to display the next
>   page, it failed to be called when the output generated was dynamically
>   generated by a servlet.

    it also failed to be called when trying to access (again) the initial
    login screen (returned 'document contains no data')

I am concluding that there must be some paths of execution that do not
flow through the doWrite() method on the HttpResponseAdapter.


Arieh
--
 Arieh Markel		                Sun Microsystems Inc.
 Network Storage                        500 Eldorado Blvd. MS UBRM11-194
 e-mail: arieh.markel@sun.COM           Broomfield, CO 80021
 Let's go Panthers !!!!                 Phone: (303) 272-8547 x78547
 (e-mail me with subject SEND PUBLIC KEY to get public key)


Mime
View raw message