[
https://issues.apache.org/jira/browse/AMBARI-22597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myroslav Papirkovskyi resolved AMBARI-22597.
--------------------------------------------
Resolution: Fixed
Pushed to trunk
> Jetty Session Timeout Is Overridden By Views Initialization
> -----------------------------------------------------------
>
> Key: AMBARI-22597
> URL: https://issues.apache.org/jira/browse/AMBARI-22597
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.0
> Reporter: Myroslav Papirkovskyi
> Assignee: Myroslav Papirkovskyi
> Priority: Critical
> Fix For: 3.0.0
>
>
> Setting {{server.http.session.inactive_timeout=60}} does not work as
> expected. After 60 seconds, the session which was created is still active and
> has not been invalidated by the Jetty scavenger.
> Upon inspection, this valid is being set correctly by {{AmbariServer.java}}
> in the Jetty {{SessionManager}}. However, when a new session is opened, the
> original value of 1800 is being used. The instance of the {{SessionManager}}
> is the same, which means that something has reset this value after we set it
> correctly.
> I believe that View-initialization might be causing this...
> STR:
> - Change server.http.session.inactive_timeout=60 and restart ambari server
> - $ curl -i -u admin:admin -b /tmp/ambarisessionfile -c
> /tmp/ambarisessionfile http://ambari-host:8080/api/v1/clusters
> - Wait for 2 minutes
> - $ curl -i -b /tmp/ambarisessionfile -c /tmp/ambarisessionfile
> http://ambari-host:8080/api/v1/clusters
> The final command will still work, even though the session should be
> invalidated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
