[
https://issues.apache.org/jira/browse/AMBARI-20220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888148#comment-15888148
]
Hudson commented on AMBARI-20220:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #6885 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6885/])
AMBARI-20220 - Parameterize the Startup Web Server Timeout Default Value
(jhurley:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=76c1fc2473b311ea25512cbde7019b28f0b47ad9])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java
* (edit) ambari-server/src/main/python/ambari_server_main.py
* (edit) ambari-server/src/test/python/TestAmbariServer.py
* (edit) ambari-server/docs/configuration/index.md
* (edit) ambari-server/src/main/python/ambari_server/serverConfiguration.py
> Parameterize the Startup Web Server Timeout Default Value
> ---------------------------------------------------------
>
> Key: AMBARI-20220
> URL: https://issues.apache.org/jira/browse/AMBARI-20220
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-20220.patch
>
>
> The {{ambari-server start}} and {{ambari-server restart}} commands are
> currently hard coded to wait a maximum of 50 seconds for the Jetty server to
> bind to port 8080 (or whatever the configured port is).
> Under normal circumstances, this value should be fine. However, since Jetty
> loads classes from views, the more views which are installed increases the
> total load time before Jetty binds to the server port.
> {code}
> ambari-server restart --debug
> Using python /usr/bin/python
> Restarting ambari-server
> Waiting for server stop...
> Ambari Server stopped
> Ambari Server running with administrator privileges.
> Organizing resource files at /var/lib/ambari-server/resources...
> Ambari database consistency check started...
> Server PID at: /var/run/ambari-server/ambari-server.pid
> Server out at: /var/log/ambari-server/ambari-server.out
> Server log at: /var/log/ambari-server/ambari-server.log
> Waiting for server
> start............................................................
> DB configs consistency check found warnings. See
> /var/log/ambari-server/ambari-server-check-database.log for more details.
> ERROR: Exiting with exit code 1.
> REASON: Server not yet listening on http port 8080 after 50 seconds. Exiting.
> {code}
> Although this a general problem with the architecture of Views, it's still
> valuable to have this startup property configurable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
