Administer TcServer timeouts in the Teamcenter management console

The server manager may time out (terminate) idle TcServer instances. A TcServer instance is considered idle if it does not receive any requests from the client application. Use the Global Pool Config tab to dynamically configure Teamcenter server timeout values. To reach the tab, choose Server Manager>[pool name]>Config>Global Pool Config. When you modify timeout values on the Global Pool Config tab and then click Submit, the timeout values are immediately applied to all Server Manager pools and all TcServer instances in the cluster. Note After you complete deployment of the Server Manager, future changes to Server Manager parameters must be made through the Teamcenter management console. Changes are not retrieved from the serverPooldatabase-name.properties file after initial deployment. After you make changes to Server Manager parameters, you must restart server pools for changes to take effect. How server manager computes timeout application The server manager computes the timeout value to apply to a server instance based on a combination of the server pool load, the instance's server mode, and the applicable timeout parameter value. Hard and Soft timeout parameters specify a range of timeout values for each of three server modes. Situation Server mode Result of timing out the server The client has made unsaved edits. Example Structure Manager uses edit mode to allow users to edit a BOM structure through multiple operations that change temporary data in the server and client until the user saves the data. Edit Changes are lost. The client has cached data in its working memory, but no edits are unsaved. Read A performance or functional issue may occur, but no loss of edits occurs. The cost of timing out a TcServer in Read mode is the time a user has to spend to get back to the state in existence at the time the server was timed out. No persistent data is cached in memory. Stateless No performance, functional issue, or loss of data occurs. The only cost of timing out a TcServer in Stateless mode is the cost of a server assignment and authentication when the client does become active again. Edit and Read mode occur mostly with rich client and NX. Stateless mode occurs mostly with Active Workspace. The server manager never applies timeout values that are longer than the Hard values. Therefore, each Soft value should be set less than or equal to the corresponding Hard value. As the count of TcServer instances exceeds the Process Target value, the server manager incrementally reduces the timeout value it applies, from the Hard value to the Soft value. The total number of TcServer instances includes both assigned and warm processes. When the count reaches 110% of Process Target, the server manager fully applies the Soft timeout value. If the total count of TcServers reaches 95% of Process Max (PROCESS_MAX), the server manager further incrementally reduces timeout values. This reduction proceeds to as low as 20% of the Soft timeout values. The following table describes the additional timeout parameters that appear on the Global Pool Config tab: This parameter Configures this Process Max Per User The maximum number of running processes (server instances) allowed per user. User Timeout Stateless If a user hits the limit defined by the Process Max Per User value, the timeout value applied to stateless server instances that are assigned to the user. Query Timeout The maximum time a server is allowed to process a single request. If this time is exceeded, the server is terminated. A value of 0 turns off the query timeout, allowing a server to continue processing a request indefinitely. Example log messages The server manager logs messages for automated changes in idle timeout values and when a TcServer does timeout: Copy PoolA.00041.ServerStarter4Tier - Adjust idle timeouts to 60% of soft timeouts: PoolA.00041.ServerStarter4Tier - Edit idle timeout: 04:48:00 (17280s) PoolA.00041.ServerStarter4Tier - Read idle timeout: 04:48:00 (17280s) PoolA.00041.ServerStarter4Tier - Stateless idle timeout: 12:00 (720s) ... vcl6006.96233728.tcserver93.2 - TcServer tcserver93@PoolA@81958@vcl6006 stateless idle timeout. vcl6006.96233728.tcserver93.3 - TcServer tcserver93@PoolA@81958@vcl6006 removed. vcl6006.96233728.tcserver93.3 - TcServer tcserver93@PoolA@81958@vcl6006 finished. Each TcServer instance also records in the syslog changes to the idle timeouts and when the TcServer does timeout: Copy EDIT IDLE timeout limit: 04:48:00 (17280s) READ IDLE timeout limit: 04:48:00 (17280s) STATELESS IDLE timeout limit: 12:00 (720s) ... Exceeded the STATELESS IDLE timeout limit: 720 seconds