Change workspace idle timeout for on-premises installs
See original GitHub issueThe workspace timeout is meant to be set in the codenvy.env
file in this section:
# Idle Timeout
# The length of time that a user is idel with their workspace when the system will suspend the
# workspace by snapshotting it and then stopping it. Idleness is determined by the length of
# time that the user has not interacted with the workspace, meaning that one of our agents
# has not received instructions. Leaving a browser window open counts as idleness time.
#CODENVY_MACHINE_WS_AGENT_INACTIVE_STOP_TIMEOUT_MS=600000
Requirement:
- The default value should be 14,400,000 MS (4 hours)
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Workspace 11.1.2.1.0.83 - Change Timeout? — oracle-tech
Right click on the application pool node. 4.Select Properties. 5.Select the Performance tab. 6.Change the Idle timeout value from 20 to 30 minutes....
Read more >Setting the Application Pool Timeout - Akumina Community
Access the Application Pool in the IIS Manager on the VM; Select the AppManager application; Click on “Advanced Settings” in the right column;...
Read more >Allow admins to change workspaces inactivity and run timeout
Administrators can specify the timeout for inactivity and running workspaces with the CheCluster spec.devEnvironment fields ...
Read more >Is there a default login timeout for a workspace ? Can we ...
User sessions automatically timeout after six hours of idle time. This is not configurable like @KunalGaurav (Databricks) mentioned.
Read more >Set Idle Timeout - Netskope Help
On the top right-hand side, click the Tools icon to open the Configure dialog box. Select an option from the Idle Timeout dropdown...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No - when a default codenvy.env, nothing should be uncommented by default unless it’s one of the important system config values like CODENVY_HOST. So, please rethink the requirement description.
I think I can incude this in 5.1.2 bug fix release