3 Replies Latest reply on Feb 10, 2010 8:36 AM by Max Rydahl Andersen

    JBoss EAP 5 throws JasperException if started with JBoss Tools

    Jochen Riedlinger Newbie

      Hi,

       

      I configured a new eclipse using JBoss Tools 3.1 CR. Unfortunately I get a strange behaviour with some web applications, if my JBoss EAP 5.0.0 is started with JBossAS Tools 2.1.0.v200912250601M-H198-CR1 from within eclipse.

       

      I get this exception page in the browser:

       

       

      HTTP Status 500 -

       

      type Exception report

       

      message

       

      description The server encountered an internal error () that prevented it from fulfilling this request.

       

      exception

       

      org.apache.jasper.JasperException: An exception occurred processing JSP page /restricted/startseite.jsp at line 15

       

      12:         <c:set var="content" value="${sessionScope[Constants.CONTENT_STARTSEITE]}" scope="page" />
      13:         <div id="seitenkopf">
      14:             <%@ include file="../common/seitenkopf.jspf"%>
      15:             <sec:granted permission="#FiolaAccess">
      16:                 <c:if test="${not content.mitarbeiterGesperrt}">
      17:                     <%@ include    file="/restricted/common/workflow/menu.jspf"%>
      18:                 </c:if>

       


      Stacktrace:
          org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:498)
          org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:411)
          org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
          org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
          javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
          org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1056)
          org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:388)
          org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:231)
          org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
          org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
          javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
          de.lbank.framework.web.struts.LActionServlet.service(LActionServlet.java:53)
          javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
          org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

       

      root cause

       

      java.lang.NullPointerException
          java.text.MessageFormat.applyPattern(MessageFormat.java:422)
          java.text.MessageFormat.<init>(MessageFormat.java:350)
          java.text.MessageFormat.format(MessageFormat.java:811)

       

       

       

      This error does not occur if I start my JBoss on the commandline and it does not occur if I start the server using the old version  JBossAS Tools    2.1.0.v200909110340M-H277-M3  of the JBoss tools.

       

      ( If you wonder about the "#" character in my JSP. this is not the "#" from JSP syntax, but belongs to a bad third-party framwork we use (www.common-controls.com). )

       

       

      Another strange thing with the newer version of JBossAS Tools is that the log output from JBoss is not always written to the eclipse console.

       

       

      Do you have any ideas what's wrong?

       

      Thanks

      Jochen

        • 1. Re: JBoss EAP 5 throws JasperException if started with JBoss Tools
          Max Rydahl Andersen Master

          Could you reduce your war to the simplest possible and create a jira about this with it attached ?

           

          Then we can better hunt it down.

           

          With respect to the console output is the console view open when you start AS and then logging stops or just doesnt start ?

          • 2. Re: JBoss EAP 5 throws JasperException if started with JBoss Tools
            Jochen Riedlinger Newbie

            Sorry, it was my fault.....

             

            I just built a very simple example, but unfortunately this didn't show the same error.

             

            Meanwhile, after debugging a lot I found out wht causes the issue. I configured an additonal configuration folder which shoul be in the classpath and configured it with "-C file:/%JBOSS_HOME%/server/production/custom_conf". This was in the startscript for the commandline and my old eclipse....but I forgot to copy it into the program-arguments field of my new eclipse....;-(

             

             

            Actually this causes a feature request. I think it would be nice, if eclipse could be configured to use the scripts run.bat/run.sh to start JBoss so that one doesn't have to put in the same parameters at different places.

             

             

            The issue with the console output is still there randomly. Sometimes logging just does not start. If it starts it logs fine.

             

            Thanks

            Jochen

            • 3. Re: JBoss EAP 5 throws JasperException if started with JBoss Tools
              Max Rydahl Andersen Master

              Meanwhile, after debugging a lot I found out wht causes the issue. I configured an additonal configuration folder which shoul be in the classpath and configured it with "-C file:/%JBOSS_HOME%/server/production/custom_conf". This was in the startscript for the commandline and my old eclipse....but I forgot to copy it into the program-arguments field of my new eclipse....;-(

               

               

              Actually this causes a feature request. I think it would be nice, if eclipse could be configured to use the scripts run.bat/run.sh to start JBoss so that one doesn't have to put in the same parameters at different places.


              You set the configuration on the server runtime and this is handled for you.

               

              About run.bat/run.sh there are multiple issues concerning this, but please open jira request for it. It would most likely require a new server type which provides zero control vs the current configurable one.

               

              The issue with the console output is still there randomly. Sometimes logging just does not start. If it starts it logs fine.

               

              I still would like you to report a jira on it. possibly record a screencast of it so we are aligned with what you are actually seeing ?

               

              /max