3 Replies Latest reply on May 19, 2009 12:45 PM by peterj

    Getting 'ClassNotFoundException' error message

    aroc0725

      I'm running version 5.0 of JBoss under Windows XP Professional Version 2002 SP3. When I try to look at the details of a Topic within the 'web-console' I get the following error message:

      org.apache.jasper.JasperException: java.lang.ClassNotFoundException: org.apache.jsp.Topic_jsp
      org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:151)
      org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
      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:803)
      org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

        • 1. Re: Getting 'ClassNotFoundException' error message
          peterj

          Hmm, I wonder if the web console even knows how to work with JBoss Messaging? I bet the JSP compiler couldn't compile tha JSP because it was using old JBossMQ classes. I was right! The Topic jsp inherits form org.jboss.mq.server.jmx.TopicMBean which is part of JBosMQ which is no longer present.

          My recommendation: forget web-console, It is an old apps that has not been updated in years. Use Embedded Jopr instead. though you will have to download the source code and compile it to get a 5.0.x-friendly version.

          • 2. Re: Getting 'ClassNotFoundException' error message
            aroc0725

            Peter, thanks for taking the time to respond.

            I'm able to use the web console on another computer running JBoss, and see the details of a given Topic without getting any error messages, but that's actually an earlier version, version 4.2.3.GA. I guess I should switch to that version, but I will take a look at Jopr, thanks again.

            • 3. Re: Getting 'ClassNotFoundException' error message
              peterj

              Of course it works on 4.2.3 - that version still uses JBossMQ.