cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maciej Kwiecien (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CXF-1778) Memory leak occurs in specific cases when WS-Addressing feature is enabled
Date Mon, 01 Sep 2008 11:09:44 GMT

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

Maciej Kwiecien updated CXF-1778:
---------------------------------

    Attachment: histoEchoServerWithoutWsAddr.log
                histoConnectionRefused.log

Last but not least,  I attach memory histograms created using jmap.

histoConnectionRefused.log - created for case #1
histoEchoServerWithoutWsAddr.log -  created for case #2




> 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.2
>            Reporter: Maciej Kwiecien
>            Priority: Critical
>         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.


Mime
View raw message