[
https://issues.apache.org/jira/browse/CXF-2019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CXF-2019:
---------------------------------
Assignee: Willem Jiang
> Test failure in systest http ClientServerSessionTest.testPublishOnBusyPort
> --------------------------------------------------------------------------
>
> Key: CXF-2019
> URL: https://issues.apache.org/jira/browse/CXF-2019
> Project: CXF
> Issue Type: Test
> Components: Build system, Transports
> Affects Versions: 2.1.3
> Environment: Windows Vista, JDK 1.5.0-update 16
> Reporter: Christian Schneider
> Assignee: Willem Jiang
>
> When running the systest I get the following error in
> ClientServerSessionTest.testPublishOnBusyPort.
> It seems the Endpoint.publish should fail as the port is already open. I have
> traced the flow till SelectChannelConnector.open().
> There it seems the _acceptChannel is not null. So it does not try to open the
> port.
> Could it be that the port is opened in the same process so it is no problem
> to publish another service to the port?
> It is also strange that this issue does not seem to happen on the integration
> test system. Is this a windows only issue?
> It would be great if we could solve this one as it is the only remaining test
> failure I have on my system for jdk 1.5.
> java.lang.AssertionError: Should have failed to publish as the port is busy
> at org.junit.Assert.fail(Assert.java:74)
> at
> org.apache.cxf.systest.http.ClientServerSessionTest.testPublishOnBusyPort(ClientServerSessionTest.java:105)
> 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:585)
> at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:59)
> at
> org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:98)
> at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:79)
> at
> org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:87)
> at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:77)
> at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:42)
> at
> org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(JUnit4ClassRunner.java:88)
> at
> org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:51)
> at
> org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:44)
> at
> org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:27)
> at
> org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:37)
> at
> org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:42)
> at
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
