Set proper GRID TIMEOUT value

Author: wheleph

Hub/Dockerfile

@@ -16,7 +16,7 @@ ENV GRID_NEW_SESSION_WAIT_TIMEOUT -1
 ENV GRID_JETTY_MAX_THREADS -1
 ENV GRID_NODE_POLLING  5000
 ENV GRID_CLEAN_UP_CYCLE 5000
-ENV GRID_TIMEOUT 30000
+ENV GRID_TIMEOUT 30
 ENV GRID_BROWSER_TIMEOUT 0
 ENV GRID_MAX_SESSION 5
 ENV GRID_UNREGISTER_IF_STILL_DOWN_AFTER 30000

Hub/Dockerfile.txt

@@ -11,7 +11,7 @@ ENV GRID_NEW_SESSION_WAIT_TIMEOUT -1
 ENV GRID_JETTY_MAX_THREADS -1
 ENV GRID_NODE_POLLING  5000
 ENV GRID_CLEAN_UP_CYCLE 5000
-ENV GRID_TIMEOUT 30000
+ENV GRID_TIMEOUT 30
 ENV GRID_BROWSER_TIMEOUT 0
 ENV GRID_MAX_SESSION 5
 ENV GRID_UNREGISTER_IF_STILL_DOWN_AFTER 30000

Hub/README.md

@@ -16,7 +16,7 @@ Note: You can optionally override default configuration settings using environme
 See the [Hub's Dockerfile](Dockerfile) to view the list of variables and their default values.
 
 ```
-$ docker run -d -P --name selenium-hub -e GRID_TIMEOUT=10000 selenium/hub
+$ docker run -d -P --name selenium-hub -e GRID_TIMEOUT=10 selenium/hub
 ```