Re: strange JSP/tomcat problem

["Scott P. Smith" <ssmith@scott-smith.com>]

Check the tomcat log files to see if any errors are being logged.  You might
have to increase the level of logging detail.

The custom tags write directly to the stream, so even though the last tag is
processed, if the connection is closed before the stream is flushed, you
would see this.

I would if the client (browser) closed the connection prematurely.  I saw
that once before.  It caused errors that Tomcat logged as something like:
"client prematurely closed connection".  Try looking at the page with a
different browser.


----- Original Message -----
From: "Poorav Chaudhari" <pooravc@yahoo.com>
To: <ajug-members@ajug.org>
Sent: Friday, February 21, 2003 2:49 PM
Subject: Re: strange JSP/tomcat problem


> >
> > Did you write a custom (in-house) Servlet or custom tag library that's
being
> > used here?
> No i did not write any custom tag libraries
> >
> > If you are using straight Action and ActionForm objects with standard
Struts
> > tag libraries, then it's probably not a flush issue.
>
> yup, i am using straight action and action form objects with the standard
tag
> libraries.
>
> it seems to me like the JSP is being fully processed. The reason i this is
> because the last input tag is converted from the html:text tag. But then i
am
> not sure of the processing order so i might be wrong.
>
> =====
> Poorav Chaudhari
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - forms, calculators, tips, more
> http://taxes.yahoo.com/
>
>