[
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.
