If your web.xml is properly configured then the stack trace should never be visible (unless your errors.jsp page likes to show the stack traces).
On Thu, May 22, 2014 at 1:24 AM, Ravikumar S <[email protected]>wrote: > I do have configuration in web.xml to display another page for 500 error > or an exception. > Below is the code snippet from web.xml. > > <error-page> > > <exception-type>org.springframework.context.ApplicationContextException</exception-type> > <location>/WEB-INF/view/jsp/brokenContext.jsp</location> > </error-page> > > <error-page> > <error-code>500</error-code> > <location>/WEB-INF/view/jsp/errors.jsp</location> > </error-page> > > <error-page> > <exception-type>java.sql.SQLException</exception-type> > <location>/WEB-INF/view/jsp/errors.jsp</location> > </error-page> > > <error-page> > <error-code>404</error-code> > <location>/WEB-INF/view/jsp/errors.jsp</location> > </error-page> > > > On Wed, May 21, 2014 at 5:08 PM, Scott Battaglia < > [email protected]> wrote: > >> Do you have any configuration in your web.xml to display another page on >> a Server 500 error or an Exception? >> >> If not, you should configure one. >> >> >> On Wed, May 21, 2014 at 3:25 AM, Ravikumar S < >> [email protected]> wrote: >> >>> Thank for your quick reply. Instead upgrading to 4.0, any possible >>> ways out there to fix in 3.5.x. >>> >>> >>> >>> On Wed, May 21, 2014 at 1:16 AM, Misagh Moayyed <[email protected]>wrote: >>> >>>> I remember seeing this issue, and it’s a bug, although I remember it in >>>> the case of ldap connection timeouts but it’s pretty much the same. >>>> >>>> >>>> >>>> This has been fixed in 4.0 >>>> >>>> >>>> >>>> *From:* Ravikumar S [mailto:[email protected]] >>>> *Sent:* Tuesday, May 20, 2014 4:47 AM >>>> *To:* [email protected] >>>> *Subject:* [cas-dev] CAS login displaying stack trace if DB is down >>>> >>>> >>>> >>>> Hi, >>>> >>>> I have come across a situation which needs to be discussed with you all. >>>> >>>> I have no idea, if this is already been discussed. Though I am posting >>>> it as this has become a critical issue for us. >>>> >>>> The scenario is as follows, >>>> >>>> 1. Go to the CAS URL >>>> >>>> 2. Enter credentials >>>> >>>> 3. Being displayed with exception stack trace if DB is down. Below is >>>> the attached image with stack trace. >>>> >>>> What is required is, system should be displaying a proper message >>>> informing user about DB. I tried all the possible ways from my end. Tried >>>> to display other page as well if DB is down, but no success. >>>> Can anyone please help me to come over this issue? >>>> >>>> Thanks, >>>> Ravi R S >>>> >>>> >>>> >>>> -- >>>> >>>> You are currently subscribed to [email protected] as: >>>> [email protected] >>>> >>>> To unsubscribe, change settings or access archives, see >>>> http://www.ja-sig.org/wiki/display/JSG/cas-dev >>>> >>>> -- >>>> You are currently subscribed to [email protected] as: >>>> [email protected] >>>> >>>> >>>> >>>> >>>> >>>> To unsubscribe, change settings or access archives, see >>>> http://www.ja-sig.org/wiki/display/JSG/cas-dev >>>> >>>> >>> -- >>> You are currently subscribed to [email protected] as: >>> [email protected] >>> >>> >>> >>> To unsubscribe, change settings or access archives, see >>> http://www.ja-sig.org/wiki/display/JSG/cas-dev >>> >>> >> -- >> You are currently subscribed to [email protected] as: >> [email protected] >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev >> >> > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
