Uploaded image for project: 'Geode'
  1. Geode
  2. GEODE-8684

Setting a session's maxInactiveInterval does not work when the commit valve is disabled

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      I was using the CommandServlet, in an external test, and noticed that when the commit valve is disabled, attempting to set the session's maxInactiveInterval does not cause the session's maxInactiveInterval to be changed and it remains at the default.

      My setup consisted of 2 Geode servers and a single Tomcat instance (9.0.39). I was checking the sessions with the following gfsh query:

      query --query="select e.key,e.value.maxInactiveInterval from /gemfire_modules_sessions.entries as e
      

      My context.xml includes the following:

            <Manager className="org.apache.geode.modules.session.catalina.Tomcat8DeltaSessionManager"
                enableLocalCache="false"
                enableCommitValve="false"
                regionAttributesId="PARTITION_REDUNDANT"
            />
      

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jens.deppe Jens Deppe
            jens.deppe Jens Deppe
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment