jmx-console null pointer exception
gsrz036 Nov 14, 2002 10:10 AMWhen I start Jboss (on NT 2000) using run.bat, things appear to start OK (lots of info - couple of warnings but nothing that looks disastrous), but when I try to bring jmx-console up in my browser (IE5.5) I get the following error (clipped from the browser window)
org.apache.jasper.JasperException: Unable to compile class for JSP
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:479)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:184)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
with a root cause of
java.lang.NullPointerException
at org.apache.tools.ant.util.FileUtils.resolveFile(FileUtils.java:330)
at org.apache.tools.ant.Project.resolveFile(Project.java:618)
at org.apache.tools.ant.types.Path.resolveFile(Path.java:451)
at org.apache.tools.ant.types.Path.translatePath(Path.java:353)
at org.apache.tools.ant.types.Path$PathElement.setPath(Path.java:119)
at org.apache.tools.ant.types.Path.setPath(Path.java:167)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:262)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:324)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:474)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:184)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
I thought I'd try to start with debug options to try and find what file wasn't being located, but when I added the -Xdebug option to the java start line, the console starts OK.
I couldn't use remote debugging because my jdb session couldn't attach to shared memory.
Any ideas how I can find what file is not being located?
I could leave the -Xdebug option in my java start line but would like to resolve this if possible.
Thanks for any help you can give.
tc