The URL is the root URL for my web app, i.e. something like   or

The welcome-files entry in web.xml includes index.jsp, and that's what I'm expecting to run.  It's a fairly simple JSP, for what that's worth.

Also, the other JSPs in my webapp seem to run fine.

On Fri, Nov 7, 2008 at 9:45 AM, Kevan Miller <> wrote:
Hi Doug,

On Nov 7, 2008, at 1:29 AM, Doug Reeder wrote:

I have an app (developed in NetBeans) which passes all the verifier tests and runs fine in GlassFish.  I'm able to deploy and start it running in Geronimo (2.1.3, Jetty), but when I try to actually access one of the JSPs, I get the following error:
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
       at java.lang.String.charAt(
       at org.apache.jasper.compiler.JspUtil.makeJavaIdentifier(
       at org.apache.jasper.JspCompilationContext.getServletClassName(
       at org.apache.jasper.JspCompilationContext.getClassFileName(
       at org.apache.jasper.compiler.Compiler.isOutDated(
       at org.apache.jasper.compiler.Compiler.isOutDated(
       at org.apache.jasper.JspCompilationContext.compile(
       at org.apache.jasper.servlet.JspServletWrapper.service(
       at org.apache.jasper.servlet.JspServlet.serviceJspFile(
       at org.apache.jasper.servlet.JspServlet.service(
       at javax.servlet.http.HttpServlet.service(
       at org.mortbay.jetty.servlet.ServletHolder.handle(
       at org.apache.geronimo.jetty6.InternalJettyServletHolder.handle(
       at org.mortbay.jetty.servlet.ServletHandler.handle(
       at org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(
       at org.mortbay.jetty.servlet.SessionHandler.handle(
       at org.mortbay.jetty.handler.ContextHandler.handle(
       at org.mortbay.jetty.webapp.WebAppContext.handle(
       at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.access$101(
       at org.apache.geronimo.jetty6.handler.TwistyWebAppContext$TwistyHandler.handle(
       at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(
       at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(
       at org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle(
       at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(
       at org.apache.geronimo.jetty6.handler.TwistyWebAppContext.handle(
       at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
       at org.mortbay.jetty.handler.HandlerCollection.handle(
       at org.mortbay.jetty.handler.HandlerWrapper.handle(
       at org.mortbay.jetty.Server.handle(
       at org.mortbay.jetty.HttpConnection.handleRequest(
       at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
       at org.mortbay.jetty.HttpParser.parseNext(
       at org.mortbay.jetty.HttpParser.parseAvailable(
       at org.mortbay.jetty.HttpConnection.handle(
       at org.apache.geronimo.pool.ThreadPool$
       at org.apache.geronimo.pool.ThreadPool$
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
       at java.util.concurrent.ThreadPoolExecutor$

1) Is there an analog to the verifier tool for Geronimo?


2) Where should I be looking to fix this? None of the source code files in the stack trace are mine!

Tomcat source code, in this case. Jetty uses the Jasper compiler for JSP compilation. In particular --

What's the URI of your JSP?

Tomcat is looking for the last '/' character in your URI, creating a substring based on the remainder of the URI, and trying to create a unique java classname based on this substring. In your case, the substring is a zero length string. Massaging your uri should work-around the problem...