[ 
https://issues.apache.org/jira/browse/CXF-7096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy Zhang updated CXF-7096:
----------------------------
    Environment: Windows 7, CXF3.1.6, CXF3.1.7 and CXF3.1.8, Visual Studio 12 
client, Java 7, JBoss EAP 6  (was: Windows 7, CXF3.1.6, CXF3.1.7 and CXF3.1.8, 
Visual Studio 12 client)
       Priority: Blocker  (was: Major)
    Description: 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 bigger and 
bigger and eventually the server will run out of memory.  (was: 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. It does not seem to cleanup the sequence 
completely since the memory usage gets bigger and bigger and eventually the 
server will run out of memory.)

> 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 bigger and bigger 
> and eventually the server will run out of memory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to