[ https://issues.apache.org/jira/browse/GEODE-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723467#comment-16723467 ]
Dan Smith commented on GEODE-6215: ---------------------------------- It looks like this has been broken since geode 1.0.0. The changes in 7ca571c turned the metadata region into Scope.LOCAL, which stopped this feature from working. As a workaround, users of older versions can ensure the region is created on all members by creating the region *before* starting any tomcat servers using the below gfsh command: {code} create region --name=gemfire_modules_sessions --type=PARTITION_REDUNDANT --enable-statistics --entry-idle-time-custom-expiry=org.apache.geode.modules.util.SessionCustomExpiry {code} If regionName or regionAttributesId are set in the context.xml, the --name and --type parameters in the above command should be set to match. > Session module does not create region on all servers > ---------------------------------------------------- > > Key: GEODE-6215 > URL: https://issues.apache.org/jira/browse/GEODE-6215 > Project: Geode > Issue Type: Bug > Components: http session > Reporter: Jacob S. Barrett > Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > When session modules bootstrap, the region responsible for distributing the > session region configuration is not created as a replicated region. This > results in the session region only being created on the server that the web > container executes the initial create region function on. -- This message was sent by Atlassian JIRA (v7.6.3#76005)