[
https://issues.apache.org/jira/browse/CXF-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955129#comment-15955129
]
Daniel Kulp commented on CXF-7096:
----------------------------------
Is it possible that there were un-acknowledged messages? Digging though the
code and running some tests, if all the messages are acknowledged, it seems to
cleanup fine. If there are un-acknowledged messages, then it doesn't
completely clean up. I'm going to fix that, but I'm wondering if that's a
possibility for your case.
> Server side memory leaking if clients do not send CloseSequence
> ---------------------------------------------------------------
>
> Key: CXF-7096
> URL: https://issues.apache.org/jira/browse/CXF-7096
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 3.1.6, 3.1.7, 3.1.8
> Environment: Windows 7, CXF3.1.6, CXF3.1.7 and CXF3.1.8, Visual
> Studio 12 client, Java 7, JBoss EAP 6
> Reporter: Andy Zhang
> Priority: Blocker
> Labels: features
>
> I have a dot net client that invokes a RM web service many times. It does not
> send CloseSequence at the end. The server side tries to terminate the
> sequence based on inactivityTimeout in the WSDL. But it does not seem to
> cleanup the sequence completely since the memory usage gets larger and larger
> and eventually the server will run out of memory. java.lang.OutOfMemoryError:
> Java heap space
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
