[
https://issues.apache.org/jira/browse/GEODE-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144113#comment-16144113
]
ASF subversion and git services commented on GEODE-3513:
--------------------------------------------------------
Commit c5b1211758ece1346a4f69bf72f31b8d4b2a8441 in geode's branch
refs/heads/develop from [~upthewaterspout]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=c5b1211 ]
GEODE-3513: Removing the use of native sessions session caching
In the session module for generic app servers, we were asking the
application server for a 'native' session and then wrapping it on our
own GemfireHttpSession. However, we were not cleaning up that native
session, which means that in PROXY mode we were leaving these sessions
on the client with them being useful.
The GemfireHttpSession now no longer wraps a native session. We are
still temporarily creating a native session because it is the only way
for us to get the session timeout value that was configured in web.xml,
but the native session is immediately invalidated.
Adding and extending cargo session tests to test how sessions are being
cleaned up from the clients and the server.
This closes #740
> Generic session replication module leaves native sessions around even in
> proxy mode
> -----------------------------------------------------------------------------------
>
> Key: GEODE-3513
> URL: https://issues.apache.org/jira/browse/GEODE-3513
> Project: Geode
> Issue Type: Bug
> Components: http session
> Reporter: Dan Smith
> Assignee: Dan Smith
>
> The session module for app servers is creating native sessions in the user's
> application server and never cleaning them up in client/server mode.
> In proxy mode this means we end up using up memory for the session, even
> though we are fetching the session from the server on every request.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
