You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Maciej Kwiecien (JIRA)" <ji...@apache.org> on 2008/09/01 12:41:44 UTC
[jira] Created: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
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
Reporter: Maciej Kwiecien
Priority: Critical
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.
[jira] Commented: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
Posted by "Maciej Kwiecien (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628343#action_12628343 ]
Maciej Kwiecien commented on CXF-1778:
--------------------------------------
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.
[jira] Closed: (CXF-1778) Memory leak occurs in specific cases when
WS-Addressing feature is enabled
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang closed CXF-1778.
-----------------------------
> 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.
[jira] Updated: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
Posted by "Maciej Kwiecien (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
Posted by "Maciej Kwiecien (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maciej Kwiecien updated CXF-1778:
---------------------------------
Affects Version/s: 2.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
>
> 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.
[jira] Updated: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp updated CXF-1778:
-----------------------------
Affects Version/s: (was: 2.2)
2.1.2
Fix Version/s: 2.1.3
> 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.
[jira] Resolved: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1778.
------------------------------
Resolution: Fixed
> 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.
[jira] Issue Comment Edited: (CXF-1778) Memory leak occurs in
specific cases when WS-Addressing feature is enabled
Posted by "Maciej Kwiecien (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
Posted by "Maciej Kwiecien (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maciej Kwiecien updated CXF-1778:
---------------------------------
Attachment: cxf-ws-addr-memory-leak.zip
Pleas find below detailed description how to reproduce bug using attached project.
Prerequisite:
1. Import project to Eclipse
Case #0: No WS-Addressing feature enabled, No memory leaks
1. Run EchoServer
2. Run LoadRunner with two arguments:
24 - number of simulated client
1800- test duration in seconds
and one JVM arg:
-Dorg.apache.cxf.Logger=org.apache.cxf.common.logging.Log4jLogger (let log4j deal with logging)
3. Observe memory usage for EchoServer and LoadRunner (Wait for a while)
4. Stop EchoServer
5.Wait for a while - memory leak should not be observed :)
Case #1: WS-Addressing enabled on client and service side.
1. Enable WS-Addressing feature
Uncomment <!-- <wsa:addressing /> --> in cxf.xml filen in src/main/resources directory
2. Run EchoServer
3. Run LoadRunner (the same way as in Case #0)
4. Observe memory usage for EchoServer and LoadRunner (Wait for a while)
5. Stop EchoServer
6. Observe memory usage for LoadRunner (memory usage should increase and after a few minutes OOM should appear ( in my case: I run LoadRunner with default heap size value and OOM is thrown when LoadRunner memory usage is aprox. 100MB)
Case #2: WS-Addressing enabled only on client side, server does not support WS-Addressing
1. Disable WS-Addressing feature on EchoServer side.
Uncomment following section in EchoServer:
// SpringBusFactory busFactory = new SpringBusFactory();
// URL cxfConfig = new URL("file:src/main/resources/cxf-server.xml");
// Bus bus = busFactory.createBus(cxfConfig);
// BusFactory.setDefaultBus(bus);
2. Run EchoServer
3. Run LoadRunner (the same way as in Case #0)
4. Observe memory usage for LoadRunner (memory usage should increase even faster than in Case #1 and after a few minutes OOM should appear
> 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
>
>
> 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.
[jira] Resolved: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-1778.
------------------------------
Resolution: Fixed
> 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.
[jira] Assigned: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp reassigned CXF-1778:
--------------------------------
Assignee: Daniel Kulp
> 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
> Assignee: Daniel Kulp
> 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.
[jira] Reopened: (CXF-1778) Memory leak occurs in specific cases
when WS-Addressing feature is enabled
Posted by "Maciej Kwiecien (JIRA)" <ji...@apache.org>.
[ 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.