Committed before 404 null

Bug #586786 reported by Hadmut Danisch
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
jetty (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: jetty

Hi,

when I try to run a servlet, even the most standard one:

  public void doGet(HttpServletRequest request, HttpServletResponse response)
      throws ServletException, IOException {

      // neu
      response.setContentType("text/html");

      PrintWriter out = response.getWriter();

      out.println("<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.0 " +
                  "Transitional//EN\">\n" +
                  "<html>\n" +
                  "<head><title>Hello WWW</title></head>\n" +
                  "<body>\n" +
                  "<h1>Hello WWW</h1>\n" +
                  "</body></html>");
  }

jetty aborts with the error message

2010-05-28 14:02:10.088:WARN::Committed before 404 null
2010-05-28 14:02:10.089:WARN::/app/abc.xxx
java.lang.IllegalStateException: Committed
        at org.mortbay.jetty.Response.resetBuffer(Response.java:1024)
        at org.mortbay.jetty.Response.sendError(Response.java:240)
        at org.mortbay.jetty.Response.sendError(Response.java:342)
        at org.mortbay.jetty.servlet.DefaultServlet.doGet(DefaultServlet.java:425)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
        at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
        at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
        at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
        at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
        at org.mortbay.jetty.Server.handle(Server.java:326)
        at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
        at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
        at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

Even if it was an error in my servlet, jetty should not crash with an uncaught exception.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: jetty 6.1.22-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Fri May 28 14:03:11 2010
EcryptfsInUse: Yes
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/usr/bin/tcsh
SourcePackage: jetty

Revision history for this message
Hadmut Danisch (hadmut) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.