[
https://issues.apache.org/jira/browse/CXF-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15612371#comment-15612371
]
Akitoshi Yoshida commented on CXF-7096:
---------------------------------------
[~zzaili] you can look at the possibility to remove the sequences by adding
some clean-up code in Destination.java.
I have no time to look at this now and the following is from my memory.
I think there is no active component to delete those expired sequences.
By the way, there is property maxSequences to limit the number of active
sequences.
regards, aki
p.s. why is your client creating a new sequence without terminating the old
sequence or not using the old sequence if it is not terminated?
> 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: Core
> 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
> Fix For: 3.1.9
>
>
> 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.4#6332)
