Felix Knecht pisze:
Since this commit I get the following error when trying to access the
first page of my custom block:
HTTP ERROR: 500
-1
RequestURI=/yellowpages-block/people.html
Caused by:
java.lang.ArrayIndexOutOfBoundsException: -1
at org.mortbay.jetty.HttpStatus.getResponseLine(HttpStatus.java:211)
at
org.mortbay.jetty.HttpGenerator.completeHeader(HttpGenerator.java:302)
at
org.mortbay.jetty.HttpConnection.commitResponse(HttpConnection.java:522)
at
org.mortbay.jetty.HttpConnection$Output.flush(HttpConnection.java:797)
at
org.apache.cocoon.util.BufferedOutputStream.realFlush(BufferedOutputStream.java:128)
at
org.apache.cocoon.environment.AbstractEnvironment.commitResponse(AbstractEnvironment.java:268)
at
org.apache.cocoon.servlet.RequestProcessor.process(RequestProcessor.java:361)
at
org.apache.cocoon.servlet.RequestProcessor.service(RequestProcessor.java:163)
at
org.apache.cocoon.sitemap.SitemapServlet.service(SitemapServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.cocoon.servletservice.ServletServiceContext$PathDispatcher.forward(ServletServiceContext.java:537)
at
org.apache.cocoon.servletservice.ServletServiceContext$PathDispatcher.forward(ServletServiceContext.java:519)
at
org.apache.cocoon.servletservice.spring.ServletFactoryBean$ServiceInterceptor.invoke(ServletFactoryBean.java:229)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at $Proxy0.service(Unknown Source)
at
org.apache.cocoon.servletservice.DispatcherServlet.service(DispatcherServlet.java:106)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:459)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:360)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:231)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:629)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:453)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
at org.mortbay.jetty.Server.handle(Server.java:303)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:452)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:721)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:509)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:349)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:320)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Probably this is also in conjunction with commit r530406.
Did I missed any configuration changes or could it really be a problem?
I have to different custom blocks and the error occurs in both of them. I start
the block with jetty:run.
Same here.
It's really problem of setting status code to the meaningless (and invalid)
"-1" value. Jetty fails on this line:
return __responseLine[status];
Because it assumes that status code has valid (positive) and meaningful value. I strongly believe that default value should be 200 and will
commit change setting that because trunk is broken, now.
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
