actually it seems there's no specific number for it, just under the 500
umbrella.
However, is there a way to make the root cause of an error - along with its
exception class -- as part of an error exception type attribute in the web.xml
file?
i.e.
<error-page>
<exception-type>java.sql.SQLException.Exhausted
ResultsSet</exception-type>
<location>/chngctrl/500error.jsp</location>
</error-page>
I've tested this to no avail...only the initial exception cause, the SQL
Exception, will return the error to the error page. Not the specified error.
I've tried separating it with a colon, space and other formats. TC never throws
an error on startup, but the error never forwards to the page either.
Would this require a filter I suppose?
-----Original Message-----
From: Propes, Barry L [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 10, 2007 11:55 AM
To: Tomcat Users List
Subject: customized error page for tomcat depending on code
someone else posted a similar topic the other day, but I didn't want to
"thread-hijack" so I started this new topic.
Anyone know of the error code number for an Exhausted ResultSet error? Or does
it just fall under the generic 500 error series?
i.e. like a page not found is 404 or forbidden section is 403, etc.
I've only seen Tomcat log it as a 500 error under the generic SQL Exception
error.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
