3 Replies Latest reply on Nov 5, 2011 12:14 AM by jaikiran pai

    Compiler error

    Nathan Howe Newbie

      We just started getting a compiler error on ur older but until-recently-working Jboss 3.2 server.  We have examined the issue endlessly but are admittedly not JBoss or Java experts.  Can anyone here give some pointers?  The error is below.  Thank you.

       

       

      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: Unable to compile class for JSP
      An error occurred at line: 4 in the jsp file: /RBDisplayReport.jsp
      Generated servlet error:
      C:\jboss-4.0.1sp1\server\default\work\jboss.web\localhost\RB7\org\apache\jsp\RBDisplayReport_jsp.java:48: error: cannot access DOMHandler
              thebean = (ReportBuilder.ReportRunner) _jspx_page_context.getAttribute("thebean", PageContext.SESSION_SCOPE);
                        ^
        class file for com.summit.utility.DOMHandler not found
      
      An error occurred at line: 4 in the jsp file: /RBDisplayReport.jsp
      Generated servlet error:
      C:\jboss-4.0.1sp1\server\default\work\jboss.web\localhost\RB7\org\apache\jsp\RBDisplayReport_jsp.java:49: error: bad operand types for binary operator '=='
              if (thebean == null){
                          ^
        first type:  ReportRunner
        second type: <null>
      
      An error occurred at line: 4 in the jsp file: /RBDisplayReport.jsp
      Generated servlet error:
      C:\jboss-4.0.1sp1\server\default\work\jboss.web\localhost\RB7\org\apache\jsp\RBDisplayReport_jsp.java:51: error: no suitable method found for setAttribute(String,ReportRunner,int)
                _jspx_page_context.setAttribute("thebean", thebean, PageContext.SESSION_SCOPE);
                                  ^
          method PageContext.setAttribute(String,Object,int) is not applicable
            (actual argument ReportRunner cannot be converted to Object by method invocation conversion)
          method PageContext.setAttribute(String,Object) is not applicable
            (actual and formal argument lists differ in length)
      3 errors
      
       org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
       org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:332)
       org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:412)
       org.apache.jasper.compiler.Compiler.compile(Compiler.java:472)
       org.apache.jasper.compiler.Compiler.compile(Compiler.java:451)
       org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
       org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:511)
       org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:295)
       org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
       org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
       javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
       org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:670)
       org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:637)
       org.apache.jsp.runInRep_jsp._jspService(runInRep_jsp.java:304)
       org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
       javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
       org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
       org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
       org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
       javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
       org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:75)
      
      note The full stack trace of the root cause is available in the Apache Tomcat/5.0.28 logs.
      
      --------------------------------------------------------------------------------
      Apache Tomcat/5.0.28
      

       

      To give more detail, this server has been chugging along for 5+ yearsbut came back up after a 36-hour power outage over the weekend and has been doing this ever since.  Thanks.