You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (Jira)" <ji...@apache.org> on 2020/11/03 18:32:00 UTC
[jira] [Created] (GEODE-8684) Setting a session's
maxInactiveInterval does not work when the commit valve is disabled
Jens Deppe created GEODE-8684:
---------------------------------
Summary: 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
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}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)