2 Replies Latest reply on Feb 18, 2010 7:07 PM by Lana Slisenko

    Server side script errors ignored

    Lana Slisenko Newbie

      I have a simple jsp page that compiles and displays just fine in a browser. I want to "break" it on purpose so that when I visit this page, I get a 500 internal error on the page (Page can not be displayed). To do this, I go into jboss/server/default/deploy/servlet.war/error.jsp and put in some garbage letters inside the "<% %>" tags. I save it and refresh the page in the browser and it still displays just fine - it's like the server is completely ignoring the error! Is there a configuration in jboss that tells the server to ingnore server-side script errors? We have JBoss 4.0.4RC1 and I'm attaching the error.jsp page. Please help! Thank you.

        • 1. Re: Server side script errors ignored
          Peter Johnson Master

          Did you try hitting the refersh button on the browsers? Sometimes you have to do that to get it to ask for the page again.

           

          The other place to look is at the "<servlet><servlet-name>jsp</servlet-name>..." entry in the server/xxx/deploy/jbossweb-tomcat55.sar/conf/web.xml, especially if the attributes checkInterval, modificationTestInterval, or development have been set.

          1 of 1 people found this helpful
          • 2. Re: Server side script errors ignored
            Lana Slisenko Newbie

            Peter, thank you so much for your quick response! I really appreciate it. I played with the settings in my web.xml, but I still have no success - errors are still ignored. I do want to mention that I got to the point where the contents of the page are not displayed if there is an error - the page is simply blank - it does not display http 500 error. I've tried uncommenting out "checkInterval" and "development" init-params - same result. I also added "reloading" init-param and that did not seem to help. Do you have any other thoughts on this? Thank you in advance.

             

            <servlet>
                  <servlet-name>jsp</servlet-name>
                  <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
                    <!--<init-param>
                        <param-name>checkInterval</param-name>
                        <param-value>10</param-value>
                    </init-param>-->
                    <init-param>
                        <param-name>compilerSourceVM</param-name>
                        <param-value>1.5</param-value>
                    </init-param>
                    <init-param>
                        <param-name>compilerTargetVM</param-name>
                        <param-value>1.5</param-value>
                    </init-param>
                    <!--<init-param>
                        <param-name>development</param-name>
                        <param-value>false</param-value>
                    </init-param>-->
                  <init-param>
                     <param-name>fork</param-name>
                     <param-value>false</param-value>
                  </init-param>
                  <init-param>
                     <param-name>xpoweredBy</param-name>
                     <param-value>false</param-value>
                  </init-param>
                  <!-- Use a custom options class to allow the shared tag lib descriptors
                   to be loaded from jars in the tomcat sar conf/tlds directory. The
                   standard options implementation can only find taglibs based on the
                   class loader classpath.
                  -->
                  <init-param>
                     <param-name>engineOptionsClass</param-name>
                     <param-value>org.jboss.web.tomcat.tc5.jasper.JspServletOptions</param-value>
                  </init-param>
                  <!-- Specify the jars relative to the jbossweb-tomcat55.sar that should
                    be scanned for common tag lib descriptors to include in every war
                    deployment.
                  -->
                  <init-param>
                     <description>MyFaces tlds</description>
                     <param-name>tagLibJar0</param-name>
                     <param-value>jsf-libs/myfaces-impl.jar</param-value>
                  </init-param>

             

                  <load-on-startup>3</load-on-startup>
               </servlet>