[
https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628343#action_12628343
]
makwieci edited comment on CXF-1778 at 9/4/08 7:11 AM:
--------------------------------------------------------------
Thanks for quick fix again.
I've tested case#1 (invoked sevice does not respond at all) and it is not the
issue any more.
Regards,
Maciej
was (Author: makwieci):
Thanks for quick fix again.
I've tested case#1 (invoked sevice does not respond at all) and it is not the
issue any more\
Regards,
Maciej
> Memory leak occurs in specific cases when WS-Addressing feature is enabled
> --------------------------------------------------------------------------
>
> Key: CXF-1778
> URL: https://issues.apache.org/jira/browse/CXF-1778
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.1.2
> Reporter: Maciej Kwiecien
> Assignee: Daniel Kulp
> Priority: Critical
> Fix For: 2.1.3
>
> Attachments: cxf-ws-addr-memory-leak.zip, histoConnectionRefused.log,
> histoEchoServerWithoutWsAddr.log
>
>
> I observed memory leak (OOM thrown) in following situations:
> 1.WS-Addressing enabled on client and server side. When server stops
> responding (connection refused on client side)
> client memory usage is increasing until OOM is thrown.
> 2.WS-Addressing enabled only on client side, server provide service without
> WS-Addressing feature (or WS-Addressing configuration is incorrect). Client
> memory heap is building up even faster than in first case.
> I will provide a sample application and more detailed description how to
> reproduce bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
