[
https://issues.apache.org/jira/browse/CXF-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Smyth closed CXF-691.
----------------------------
Resolution: Invalid
This is apparently a bug in maven.
There is this comment in some system tests using WS-Addressing, e.g.
MAPTestBase:
// special case handling for WS-Addressing system test to avoid
// UUID related issue when server is run as separate process
// via maven on Win2k
boolean inProcess = "Windows 2000".equals(System.getProperty("os.name"));
assertTrue("server did not launch correctly", launchServer(Server.class,
inProcess));
Although this may not be expected (at least I did not expect it) the fork mode
of the server also affects the behaviour of the client, which is where the
difference between synchronous and asynchronous invocation comes into play.
But running the server in process does fix the problem of the asynchronous
client hanging in UUID generation.
Must be the combination of the asynchronicity and the forking of a child
process, as forking the server and synchronous invocations work OK.
> WS-Addressing: Broken when used in JAX-WS asynchronous incovations
> ------------------------------------------------------------------
>
> Key: CXF-691
> URL: https://issues.apache.org/jira/browse/CXF-691
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Reporter: Andrea Smyth
>
> See System test case org.apache.cxf.systest.ws.addressing.DecoupledAsyncTest.
> Possibly to do with pausing execution of thread on which interceptor chain
> started executing and resuming on executor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
