Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <10146692.1170963306344.JavaMail.jira@brutus>
Date: Thu, 8 Feb 2007 11:35:06 -0800 (PST)
From: "Ajay Paibir (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Assigned: (CXF-415) Decoupled Endpoint Observer should not
 insert HttpRequest and HttpResponse instances into the Message.
In-Reply-To: <25281646.1170963306286.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ajay Paibir reassigned CXF-415:
-------------------------------

    Assignee: Ajay Paibir

> 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.