[jboss-jira] [JBoss JIRA] (WFLY-4262) Memory of expired session not released
Wojciech Ozga (JIRA)
issues at jboss.org
Sun Jan 18 08:40:49 EST 2015
[ https://issues.jboss.org/browse/WFLY-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wojciech Ozga updated WFLY-4262:
--------------------------------
Steps to Reproduce:
1. Set user session expiration to 20minutes in web.xml
<session-config>
<session-timeout>20</session-timeout>
<cookie-config>
<path>/</path>
</cookie-config>
</session-config>
2. Deploy project to clean WildFy 8.2
3. Simulated traffic with JMeter, creating new user session on every request, till the JVM memory is almost fully used.
4. wait 20 minutes and verify that the sessions was not removed
5. try to make new requests - verify that session waas not removed
6. perform System.gc() from the code or from fe: VisualVM
was:
1. Set user session expiration to 20minutes in web.xml
2. Deploy project to clean WildFy 8.2
3. Simulated traffic with JMeter, creating new user session on every request, till the JVM memory is almost fully used.
4. wait 20 minutes and verify that the sessions was not removed
5. try to make new requests - verify that session waas not removed
6. perform System.gc() from the code or from fe: VisualVM
> Memory of expired session not released
> --------------------------------------
>
> Key: WFLY-4262
> URL: https://issues.jboss.org/browse/WFLY-4262
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.2.0.Final
> Environment: Running on Windows 7
> Wildfly 8.2
> Primefaces 5.1
> Reporter: Wojciech Ozga
> Assignee: Jason Greene
> Attachments: Expired session still available.png, JVM memory usage.png
>
>
> Expecting Wildfly to remove expired user session data after 20 minutes. But the data is never removed, neither by container, neither by GC, neither when new requests reach the server.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jboss-jira
mailing list