Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 24 Jan 2014 14:42:39 +0000 (UTC)
From: "Andrei Shakirin (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12690824.1390499328083.6931.1390574559472@arcas>
In-Reply-To: <JIRA.12690824.1390499328083@arcas>
References: <JIRA.12690824.1390499328083@arcas>
Subject: [jira] [Resolved] (CXF-5516) Decoupled endpoints is not compatible
 with @UseAsyncMethod annotation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrei Shakirin resolved CXF-5516.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.9
                   3.0.0-milestone2

> Decoupled endpoints is not compatible with @UseAsyncMethod annotation
> ---------------------------------------------------------------------
>
>                 Key: CXF-5516
>                 URL: https://issues.apache.org/jira/browse/CXF-5516
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Andrei Shakirin
>            Assignee: Andrei Shakirin
>             Fix For: 3.0.0-milestone2, 2.7.9
>
>
> In case of use decoupled endpoints in combination with @UseAsyncMethod annotation, code in AbstractJAXWSMethodInvoker tries to suspend transport continuation.
> It causes "java.lang.IllegalStateException: IDLE,initial" exception and doesn't make sense, because partial response is already sent to the client and new processing thread is started. Full response will be sent in separate transport connection.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)