Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319678 - testInstallSimpleWar fails on mac build
Summary: testInstallSimpleWar fails on mac build
Status: CLOSED FIXED
Alias: None
Product: Gemini.Web
Classification: RT
Component: unknown (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-13 05:59 EDT by Steve Powell CLA
Modified: 2010-09-08 06:29 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Powell CLA 2010-07-13 05:59:29 EDT 
TomcatServletContainerTests.testInstallSimpleWar (org.eclipse.gemini.web.test.tomcat) test fails during builds of Gemini Web Container (intermittently) with stacktrace:

java.io.IOException: Server returned HTTP response code: 400 for URL: http://localhost:8080/test/index.html
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1313)
    at org.eclipse.gemini.web.test.tomcat.TomcatServletContainerTests.validateURL(TomcatServletContainerTests.java:300)
    at org.eclipse.gemini.web.test.tomcat.TomcatServletContainerTests.testInstallSimpleWar(TomcatServletContainerTests.java:113)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
    at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
    at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
    at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
    at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
    at org.eclipse.virgo.test.framework.OsgiTestRunner.run(OsgiTestRunner.java:73)
    at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39)
    at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420)
    at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911)
    at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:743)
Comment 1 Glyn Normington CLA 2010-07-15 11:26:10 EDT 
We need to get a stack trace, if one is available, from the deployment, probably by digging into log.log.

Once deployment has failed, the 400 stack trace above gives no clues as to the reason for the problem.
Comment 2 Steve Powell CLA 2010-09-08 06:27:28 EDT 
This problem appears not to occur anymore.  Should we close this?
Comment 3 Glyn Normington CLA 2010-09-08 06:29:42 EDT 
I would say so.