Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <1102774162.1220436944391.JavaMail.jira@brutus>
Date: Wed, 3 Sep 2008 03:15:44 -0700 (PDT)
From: "Maciej Kwiecien (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Reopened: (CXF-1778) Memory leak occurs in specific cases
 when WS-Addressing feature is enabled
In-Reply-To: <230493166.1220265704486.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-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maciej Kwiecien reopened CXF-1778:
----------------------------------


Daniel,

First of all, I am very gratefull for really quick bug fix.
Memory leak does not occur  when server doesn't respond with addressing information any more. 
However, there is still memory leak when server doesn't respond at all (client receives Connection refused).

Given that case #1 is stil the issue, let me reopen it. I hope case #1 might be also fixed.

Thanks,
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.