tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Smith <d...@cornell.edu>
Subject Re: error-page and TC 5.5.23
Date Thu, 10 May 2007 15:19:58 GMT
Reading the comments on the bug issue you cited, it looks like it's 
fixed, but with side effects -- namely the exception traps aren't 
available any more.  What do you want anyone to say here?

--David

gb1071nx wrote:

>Is this just a boring question, or has no-one else run into the problem?
>
> 
>
>  
>
>>-----Original Message-----
>>From: gb1071nx [mailto:gb1071nx@globallyboundless.com] 
>>Sent: Tuesday, May 08, 2007 2:22 PM
>>To: Tomcat Users List
>>Subject: RE: error-page and TC 5.5.23
>>
>>I'm just adding to this: 
>>
>>When I remove the mapping for the error-code 500, then I get 
>>the standard tc5.5 error page.  So my exception-type 
>>error-page directive is being ignored. 
>>
>>So it does appear that
>>http://issues.apache.org/bugzilla/show_bug.cgi?id=37062#c4  
>>isn't fixed.
>>And won't be fixed? 
>>
>>It occurs to me that this should break quite a few "working" 
>>apps though, so surely someone else has reported it? 
>>Searching further, I found this:
>>
>>http://issues.apache.org/bugzilla/show_bug.cgi?id=40135
>>
>>Is it then now a requirement that for JSP's, we *must* use 
>>the errorPage directive?  Or is there a way to get the more 
>>generic web.xml error-page config to work? 
>>
>>And can anyone explain what is meant by "development mode" 
>>(from comment in bug 37062 and how to switch it off (to see 
>>if that makes my error-page's work again)
>>
>>
>>
>>    
>>
>>>-----Original Message-----
>>>From: gb1071nx [mailto:gb1071nx@globallyboundless.com]
>>>Sent: Tuesday, May 08, 2007 12:39 PM
>>>To: Tomcat Users List
>>>Subject: error-page and TC 5.5.23
>>>
>>>
>>>Hello,
>>>
>>>I'm starting the process of migrating some of our server from
>>>5.0.29 to 5.5.23, and I've found that the 'nice' useful stacktraces 
>>>with
>>>linenumbers are back, and working beautifully in 5.5.23.   
>>>
>>>But I do find the following issues as well: 
>>>
>>>I have the following test page: 
>>>
>>><html>
>>><body>
>>><%
>>> if (true) {
>>>  throw new java.sql.SQLException("TEST");  } %> </body> </html>
>>>
>>>
>>>And the following web.xml:
>>>
>>><?xml version="1.0" encoding="ISO-8859-1"?> <web-app 
>>>xmlns="http://java.sun.com/xml/ns/j2ee"
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
>>>http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
>>>version="2.4">
>>>
>>>
>>><error-page>
>>>	<exception-type>java.sql.SQLException</exception-type> 
>>>	<location>/error/database.jsp</location>
>>></error-page>
>>><error-page>
>>>	<error-code>500</error-code> 
>>>	<location>/error/500.jsp</location>
>>></error-page>
>>>
>>></web-app>
>>>
>>>
>>>
>>>And when I call the page throwing the SQLException, I get the error 
>>>page
>>>for the error-code 500.   Tomcat5.0 does not behave like 
>>>that, 5.5 does.
>>>Which is the correct behaviour? (or perhaps:  is there a way to 
>>>configure 5.5 so that it acts like 5.0?)  I recall this bug report:
>>>http://issues.apache.org/bugzilla/show_bug.cgi?id=37062#c4 .  
>>>Has the bug reported in comment#4 been fixed?  Is this the bug I'm 
>>>experiencing in my test page?
>>>
>>>
>>>
>>>
>>>Also, I can confirm the following bug, I also experience it: 
>>>http://issues.apache.org/bugzilla/show_bug.cgi?id=42314
>>>
>>>      
>>>
>
>---------------------------------------------------------------------
>To start a new topic, e-mail: users@tomcat.apache.org
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
>  
>


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message