Return-Path: 
 <issues-return-15046-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
Delivered-To: apmail-cxf-issues-archive@www.apache.org
Received: (qmail 38618 invoked from network); 19 Nov 2010 09:40:04 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 19 Nov 2010 09:40:04 -0000
Received: (qmail 46041 invoked by uid 500); 19 Nov 2010 09:40:36 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 45937 invoked by uid 500); 19 Nov 2010 09:40:36 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 45929 invoked by uid 99); 19 Nov 2010 09:40:35 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Nov 2010 09:40:35 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Nov 2010 09:40:34 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oAJ9eEfU013032
	for <issues@cxf.apache.org>; Fri, 19 Nov 2010 09:40:14 GMT
Message-ID: <16276736.193641290159614430.JavaMail.jira@thor>
Date: Fri, 19 Nov 2010 04:40:14 -0500 (EST)
From: "Freeman Fang (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Resolved: (CXF-3132) asynchronous client can't get correct
 error if non-runtimeexcpetion happen
In-Reply-To: <17116033.171781290071893458.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Freeman Fang resolved CXF-3132.
-------------------------------

    Resolution: Fixed

commit fix

http://svn.apache.org/viewvc?rev=1036397&view=rev
http://svn.apache.org/viewvc?rev=1036765&view=rev for trunk

http://svn.apache.org/viewvc?rev=1036401&view=rev
http://svn.apache.org/viewvc?rev=1036766&view=rev for 2.3 branch

http://svn.apache.org/viewvc?rev=1036774&view=rev
http://svn.apache.org/viewvc?rev=1036405&view=rev for 2.2 branch

> asynchronous client can't get correct error if non-runtimeexcpetion happen
> --------------------------------------------------------------------------
>
>                 Key: CXF-3132
>                 URL: https://issues.apache.org/jira/browse/CXF-3132
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 2.3.0, 2.2.11
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2.2.12, 2.3.1, 2.4
>
>         Attachments: CXF-3132-testcase.patch, non-recurse.patch
>
>
> when use asynchronous cxf client handler, if there's a non-runtimeexception thrown, the asynchronous client handler can't get correct reason but get TimeoutException.
> For example if client receive a very complex soap message response with a greate amount of element level like
> <soap:envelope><soap:body><a1><a2>...<an></an>...</a2</a2></soap:body></soap:envelope>
> here n could be very big which can cause StackOverflowError in StatxUtils as StatxUtils use recursive way to parse soap message.
> In this case if we use asynchronous cxf client, the client has no way to know there's a StackOverflowError but just get TimeoutException.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.