Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <1967561447.105941262898539825.JavaMail.jira@brutus.apache.org>
Date: Thu, 7 Jan 2010 21:08:59 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Assigned: (CXF-2591) MAPCodec : memory leak with an async
 client with network issues (connection timeout, read timeout etc)
In-Reply-To: <1379073710.1261661069646.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-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp reassigned CXF-2591:
--------------------------------

    Assignee: Daniel Kulp

> MAPCodec : memory leak with an async client with network issues (connection timeout, read timeout etc)
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2591
>                 URL: https://issues.apache.org/jira/browse/CXF-2591
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.2.5
>         Environment: CXF 2.2.2 & 2.2.5 / JDK 1.6 / Linux (Ubuntu 9.10)
>            Reporter: Thomas Sauzedde
>            Assignee: Daniel Kulp
>            Priority: Critical
>
> Context :
>  a JAX-WS asynchronous client, with WS-Adressing enabled
>  when there are network issues like connection timeout, read timeout etc,
> Observed facts :
> MAPCodec::uncorrelatedExchanges is not cleaned when the client is trying to request the server and there is a network issue.
> In such a case, the InterceptorChain is by-passed, so MAPCodec::handleFault() is NOT called and so the MAPCodec::uncorrelatedExchanges grows and grows until OOM :-(
> Don't have any patch (yet) to provide because this is something more architectural than technical :-(
> When a network issue occurs, this throws an ExecutionException in JaxwsClientCallback::handleResponse(), the "normal" InterceptorChain is then by-passed there IMHO ...

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