Dan Smith created GEODE-1982:
--------------------------------
Summary: Heap LRU with filter based session replication does not
actually free up memory
Key: GEODE-1982
URL: https://issues.apache.org/jira/browse/GEODE-1982
Project: Geode
Issue Type: Improvement
Components: http session
Reporter: Dan Smith
Using the session replication module for generic app servers, we install a
ServletFilter that wraps sessions in a GemfireHttpSession object. That
GemfireHttpSession object has a reference to an underlying native session, and
modifications to the GemfireHttpSession are made to the underlying native
session as well.
When the module is configured in client/server mode with a client side cache,
the client side region has heap lru enabled. Unfortunately, when entries are
removed due to heap lru, the application server is still going to retain a
reference to the native session. I've observed this happening in a debugger,
unfortunately I don't have a reproducible test case for this yet.
With Jetty, at least, it retains a weak reference to the session, so I suppose
the session could eventually be removed, but other application servers may not
use weak references.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
