You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/12/06 18:01:00 UTC
[jira] [Commented] (AMBARI-22597) Jetty Session Timeout Is
Overridden By Views Initialization
[ https://issues.apache.org/jira/browse/AMBARI-22597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280586#comment-16280586 ]
Hudson commented on AMBARI-22597:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8498 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8498/])
AMBARI-22597. Jetty Session Timeout Is Overridden By Views (mpapyrkovskyy: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cfb2321f8769bdc92a1c08ad354e604f104ac629])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariServer.java
> 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)