You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Ajay Paibir (JIRA)" <ji...@apache.org> on 2007/02/09 11:36:05 UTC
[jira] Resolved: (CXF-415) Decoupled Endpoint Observer should not
insert HttpRequest and HttpResponse instances into the Message.
[ https://issues.apache.org/jira/browse/CXF-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ajay Paibir resolved CXF-415.
-----------------------------
Resolution: Fixed
> Decoupled Endpoint Observer should not insert HttpRequest and HttpResponse instances into the Message.
> ------------------------------------------------------------------------------------------------------
>
> Key: CXF-415
> URL: https://issues.apache.org/jira/browse/CXF-415
> Project: CXF
> Issue Type: Bug
> Components: Transports
> Affects Versions: 2.0-M1
> Reporter: Ajay Paibir
> Assigned To: Ajay Paibir
> Fix For: 2.0-RC
>
>
> The Decouple Endpoint Observer inserts HttpRequest,HttpResponse instances into the Application supplied response context. Now if the ClientImpl.invoke is generally called on a thread different from the thread on which decoupled endpoint received the response then a race condition is introduced. The thread on which invoke was called may sometime see a IllegalStateException for the HttpResponse instance inserted into the context during decoupled endpoint thread processing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.