[jira] [Closed] (GEODE-8684) Setting a session's maxInactiveInterval does not work when the commit valve is disabled

["Owen Nichols (Jira)" <ji...@apache.org>]

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

Owen Nichols closed GEODE-8684.
-------------------------------

> Setting a session's maxInactiveInterval does not work when the commit valve is disabled
> ---------------------------------------------------------------------------------------
>
>                 Key: GEODE-8684
>                 URL: https://issues.apache.org/jira/browse/GEODE-8684
>             Project: Geode
>          Issue Type: Bug
>          Components: http session
>    Affects Versions: 1.14.0
>            Reporter: Jens Deppe
>            Assignee: Jens Deppe
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.2, 1.13.3, 1.14.0
>
>
> 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:
> {code:java}
> query --query="select e.key,e.value.maxInactiveInterval from /gemfire_modules_sessions.entries as e
> {code}
> My {{context.xml}} includes the following:
> {code:xml}
>       <Manager className="org.apache.geode.modules.session.catalina.Tomcat8DeltaSessionManager"
>           enableLocalCache="false"
>           enableCommitValve="false"
>           regionAttributesId="PARTITION_REDUNDANT"
>       />
> {code}



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