[
https://issues.apache.org/jira/browse/CXF-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang updated CXF-3132:
------------------------------
Attachment: CXF-3132-testcase.patch
attach a testcase which expose this issue
> 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
>
>
> 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.
