cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <>
Subject [jira] Commented: (CXF-2019) Test failure in systest http ClientServerSessionTest.testPublishOnBusyPort
Date Mon, 02 Feb 2009 07:39:59 GMT


Willem Jiang commented on CXF-2019:

Hi  Christian,

The exception is not we want, I just did a quick trace and found if we set the reuseAddress
to be false (the default one is false) , we will get the expecting exception.
So I need to do some configuration work to get the test work again ;)



> Test failure in systest http ClientServerSessionTest.testPublishOnBusyPort
> --------------------------------------------------------------------------
>                 Key: CXF-2019
>                 URL:
>             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
> 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
> 	at org.apache.cxf.systest.http.ClientServerSessionTest.testPublishOnBusyPort(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at org.junit.internal.runners.TestMethod.invoke(
> 	at org.junit.internal.runners.MethodRoadie.runTestMethod(
> 	at org.junit.internal.runners.MethodRoadie$
> 	at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(
> 	at org.junit.internal.runners.MethodRoadie.runTest(
> 	at
> 	at org.junit.internal.runners.JUnit4ClassRunner.invokeTestMethod(
> 	at org.junit.internal.runners.JUnit4ClassRunner.runMethods(
> 	at org.junit.internal.runners.JUnit4ClassRunner$
> 	at org.junit.internal.runners.ClassRoadie.runUnprotected(
> 	at org.junit.internal.runners.ClassRoadie.runProtected(
> 	at
> 	at
> 	at
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> 	at
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message