[
https://issues.apache.org/jira/browse/CXF-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665211#action_12665211
]
Daniel Kulp commented on CXF-1990:
----------------------------------
I believe this is already fixed on trunk and on the 2.1.x branch (will be in
2.1.4). The fix was to not allow the get call to return the value until the
handlers have been called.
> 3 CTS tests, invokeAsyncTest(for pojo, ejb and servlet) fail
> -------------------------------------------------------------
>
> Key: CXF-1990
> URL: https://issues.apache.org/jira/browse/CXF-1990
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Reporter: Chaitanya Choleti
> Priority: Minor
>
> CTS tests jaxws.ee.w2j.document.literal.async.client.invokeAsyncCallbackTest
> (for pojo, ejb and servlet client ) fail ocassionally. The reason being....
> In the invokeAsync method of JaxWsClientProxy class, ClientCallbacks
> handleMessage method is overridden. In this method first ClientCallbacks
> field done (boolean) is set to true and then handlers
> handleResponse(Response<?>) is called. In the CTS tests, if a
> ClientCallback.get() is called in between these two requests, a
> NullPointerException is thrown as the handlers state remains unchanged.
>
> Suggested Fix : synchronize the ClientCallbacks handleResponse in the
> JaxWsClientProxy.
> Also, ClientCallback class is a not thread safe so any state change
> should be done synchronously.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
