Hi, Dave.
Did you check your log files for exceptions? I've seen behavior similar
to what you're describing with Tomcat 4.0.x running Standalone. What I've
seen is that it gets a full buffer's (defaults to 8K, like you're seeing, but
can be set to different size) worth of content and displays it. Then, it runs
into a NullPointerException (or probably some other exception, but, usually
for me, it's a good ole NPE) while trying to generate the next buffer's worth
of content. At this point, the browser doesn't show an error page but just
stops with only the one buffer's worth of content displayed. Maybe Apache
renders the page as blank, but I usually get the partially returned page, as
far as it can be rendered. Besides the partial page, the only sign that
something went wrong is in the log. I've been meaning to look into this to
see if it's a reported bug, but haven't yet. Is this what you're running
into?
-Jeff
"Short, Dave"
<dave.short@p To: "'Tomcat Users List'"
<[EMAIL PROTECTED]>
fizer.com> cc:
Subject: Apache 2.0.39 and Tomcat 4.1.8
Servlet issue
07/24/02
10:59 AM
Please
respond to
"Tomcat Users
List"
There is an issue with Apache 2.0.39 and Tomcat 4.1.8 (actually this issue
first appeared with Apache 2.0.36 and Tomcat 4.0.x). It seems, if a servlet
returns content (dynamically built HTML for instance) which exceeds 8192 in
length, the content is truncated at 8192 and a blank page is rendered by
Apache. Actually, Apache renders what was returned by Tomcat (8192 bytes of
the dynamically generated HTML page). Basically, an incomplete HTML page -
hence it is displayed as blank.
--
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]>
