tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arshad Mahmood" <>
Subject Some tomcat issues
Date Tue, 04 Apr 2006 02:35:06 GMT


I have a couple of questions which I wonder if the developers can answer.
These are not strictly user problems that is why I am sending them to this


1.	I am trying to write my own errorReportValveClass. I note in my
valve that the request that I am passed seems to have only a single
attribute assigned (the exception). I was hoping that the request would be
the main request as I have some very useful stuff assigned as attributes
that would come in handy in handling the error. I wasn't sure whether this
behaviour is part of the spec because the spec is very light on error
handling issues.
2.	My application originally ran on Resin and I have converted it to
tomcat. I note that when I use a tag like <xyz:tag value="${}" />.
If the value of is null then tomcat seems to converts the value to
a string, under resin I was used to getting a null value passed and now it
seems to want send an empty string.
3.	The default installation of tomcat seems to be missing a log for the
exceptions that are generated. The manual says that in the old system they
would go to stdout.log but under the new scheme they should go to
localhost.out. There seems to be no log of any exceptions to any log files
at all, is this a consequence of errorReportValveClass ?
4.	Is there any way when an exception is generated while processing a
JSP page that the response can be committed. Again resin is very loose on
what can appear in the JSP page and I hadn't noticed all sorts of errors in
the pages that have now shown up under Tomcat (excellent by the way!!). But
it does mean that I have to manually put in "out.flush()" all over the place
to find exactly where the exception occurred.


Apologies if this message has been sent to the wrong list but I thought
these were more development issues than user queries. 


I haven't used Tomcat for over a year and I have to say that I am extremely
impressed. Thank you very much for producing such an excellent piece of



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message