java.io.IOException: FULL head

Apache's JIRA Issue Tracker | Jarek Gawor | 9 years ago
  1. 0

    On Jetty the testsuite/console-testsuite/advanced tests usually fail with strange errors while the same works fine on Tomcat. On the server I see the following errors: 16:22:43,046 WARN [log] handle failed java.io.IOException: FULL head at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:276) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:201) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:331) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) The tests fail with different errors e.g. (it changes from run to run): testNewJMSResource(org.apache.geronimo.testsuite.console.JMSResourcesTest) Time elapsed: 7.86 sec <<< FAILURE! com.thoughtworks.selenium.SeleniumException: ERROR: Element //input[@value='Add Destination'] not found at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:73) at com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:82) at org.apache.geronimo.testsuite.console.JMSResourcesTest.testNewJMSResource(JMSResourcesTest.java:47)

    Apache's JIRA Issue Tracker | 9 years ago | Jarek Gawor
    java.io.IOException: FULL head
  2. 0

    On Jetty the testsuite/console-testsuite/advanced tests usually fail with strange errors while the same works fine on Tomcat. On the server I see the following errors: 16:22:43,046 WARN [log] handle failed java.io.IOException: FULL head at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:276) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:201) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:331) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) The tests fail with different errors e.g. (it changes from run to run): testNewJMSResource(org.apache.geronimo.testsuite.console.JMSResourcesTest) Time elapsed: 7.86 sec <<< FAILURE! com.thoughtworks.selenium.SeleniumException: ERROR: Element //input[@value='Add Destination'] not found at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:73) at com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:82) at org.apache.geronimo.testsuite.console.JMSResourcesTest.testNewJMSResource(JMSResourcesTest.java:47)

    Apache's JIRA Issue Tracker | 9 years ago | Jarek Gawor
    java.io.IOException: FULL head
  3. 0

    Problems with large request/response headers

    Google Groups | 7 years ago | Matthew McGinty
    java.io.IOException: FULL head
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    GWT 1.7.1 don't show app in hosted mode (Jetty bug: FULL head)

    Google Groups | 7 years ago | lain
    java.io.IOException: FULL head
  6. 0

    In Hosted mode, GWT Stopped displaying Widgets

    Google Groups | 7 years ago | Raju
    java.io.IOException: FULL head

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      FULL head

      at org.mortbay.jetty.HttpParser.parseNext()
    2. Jetty Server
      SelectChannelEndPoint.run
      1. org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:276)
      2. org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
      3. org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
      4. org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:396)
      4 frames
    3. Geronimo Framework, Modules :: Core
      ThreadPool$ContextClassLoaderRunnable.run
      1. org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:201)
      2. org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:331)
      2 frames
    4. Java RT
      Thread.run
      1. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
      2. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
      3. java.lang.Thread.run(Thread.java:595)
      3 frames