[ 
https://issues.apache.org/jira/browse/CXF-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-1990.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.4
         Assignee: Jarek Gawor


Fixed by jgawor in rev 724485

> 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
>            Assignee: Jarek Gawor
>            Priority: Minor
>             Fix For: 2.1.4
>
>
> 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.

Reply via email to