Details
Description
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)