[jira] [Commented] (GEODE-8781) The Tomcat session state module in P2P mode doesn't re-establish the session region after a reconnect

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-8781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17247538#comment-17247538 ] 

ASF subversion and git services commented on GEODE-8781:
--------------------------------------------------------

Commit f8b2cae2376c944064ff03bcc2260694d801ca85 in geode's branch refs/heads/feature/GEODE-8781 from Barry Oglesby
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f8b2cae ]

GEODE-8781: Added ReconnectListener to PeerToPeerSessionCache


> The Tomcat session state module in P2P mode doesn't re-establish the session region after a reconnect
> -----------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-8781
>                 URL: https://issues.apache.org/jira/browse/GEODE-8781
>             Project: Geode
>          Issue Type: Bug
>          Components: http session
>            Reporter: Barrett Oglesby
>            Priority: Major
>              Labels: pull-request-available
>
> In the PeerToPeerSessionCache, the createOrRetrieveRegion method creates the region when the Tomcat server is started.
> The PeerToPeerSessionCache stores this region in a field called sessionRegion. It also stores the cache in a field called cache, and the fronting region in a field called operatingRegion if local caching is enabled.
> When the DistributedSystem is disconnected, the cache and its regions are closed.
> When the DistributedSystem is reconnected, the cache is recreated but not the regions. This is because they were created using API rather than in XML or cluster configuration. This can be changed by setting use-cluster-configuration=false, but it won't really make a difference.
> Thats because the PeerToPeerSessionCache's references are to the closed cache and regions.
> Adding a ReconnectListener to the PeerToPeerSessionCache so that these references are re-established will address this issue.



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