[
https://issues.apache.org/jira/browse/CXF-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669918#comment-15669918
]
Bjørn Hilstad commented on CXF-6590:
------------------------------------
I reopened this issue some time ago but I am not sure it has been picked up.
[~dkulp]: Will this be fixed or should I create a new case?
> MAPCodec: memory leak with sync client when soapfaults returned from endpoint
> -----------------------------------------------------------------------------
>
> Key: CXF-6590
> URL: https://issues.apache.org/jira/browse/CXF-6590
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 3.0.6
> Environment: CXF 3.0.6, JDK 1.7, CXF 3.1.2
> Reporter: Bjørn Hilstad
> Assignee: Daniel Kulp
> Fix For: 3.1.3, 3.0.7
>
> Attachments: cxfoom.zip, wiremock.zip
>
>
> This bug is similar to CXF-2591 but relates to sync clients.
> A simple client using a service with WS-Addressing which makes repeated calls
> to a service that returns a soapfault will cause a build up of objects in
> MAPCodec::uncorrelatedExchanges.
> The real use case is an application using Apache Camel to keep invoking a
> service that returns a fault (for instance wsa:DestinationUnreachable) using
> the built in redelivery-functions of Apache Camel.
> A simple CXF client that reproduces the issue has been created. The client
> just invokes a service in a loop and by observing the used memory (jconsole)
> and performing memory dumps which can be analyzed using MAT, you can see the
> issue.
> A standalone wiremock functions as the endpoint.
> The reproducers will be attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
