You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Benjamin P Ross (Jira)" <ji...@apache.org> on 2021/02/09 01:33:00 UTC

[jira] [Resolved] (GEODE-6872) Add section with more details about sticky vs non-sticky sessions for Tomcat Session Module

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

Benjamin P Ross resolved GEODE-6872.
------------------------------------
    Resolution: Done

> Add section with more details about sticky vs non-sticky sessions for Tomcat Session Module
> -------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6872
>                 URL: https://issues.apache.org/jira/browse/GEODE-6872
>             Project: Geode
>          Issue Type: Bug
>          Components: docs, http session
>            Reporter: Ryan McMahon
>            Priority: Major
>              Labels: GeodeCommons
>
> Sticky vs non-sticky sessions and the recommended configurations should be discussed in better detail the docs (it is not discussed at all for Tomcat module).  If the user configured client-server topology with non-sticky sessions, we do NOT recommend enableLocalCaching be set because it results in unpredictable asynchronous behavior/replication.  
> If they follow our recommendations and disable local caching (proxy-only client), then they should also set `gemfire.EXPIRE_SENDS_ENTRY_AS_CALLBACK`. Otherwise the expire logic will not be called on the client. The side effects of this may be benign, but if there are any listeners depending on that expiration logic, it may result in bugs or a resource leak.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)