![Tuxedo Tuxedo](/uploads/1/2/5/4/125457849/556332523.jpg)
Get up and running with the Tuxedo Administration Console April 2, 2007 Posted by Duncan in Administration, Infrastructure, PeopleSoft, PS Admin, Tuxedo. Comments closed. I think I’ve stumbled across a better way of remotely administering servers than using remote control software and PSADMIN.
![Tuxedo time quincy ma Tuxedo time quincy ma](/uploads/1/2/5/4/125457849/765369235.jpg)
Timeout parameters in PeopleSoft Application stack which may need to adjust as per the organisational and business requirements.
Designating How Much Time to Process a Request Setting Up a BEA Tuxedo Application Sometimes an unexpected system error occurs, freezing a service or causing it to run out of control while it is processing a request. Obviously, it is a good idea to remove these processes, but it is difficult to detect them or determine how they developed errors. The BEA Tuxedo system provides a mechanism for terminating such processes even when you cannot identify them. To use this mechanism, set the SVCTIMEOUT parameter. The SVCTIMEOUT parameter allows you to designate an amount of time (in seconds) in which a service should be able to process a request.
If the interval defined by this parameter elapses and a service has not finished processing a request, the process for that request is killed. In essence, the service timeout mechanism acts like a scavenger for frozen or out of control application servers.
By default, the BEA Tuxedo system does not terminate any service process; you must set the SVCTIMEOUT parameter to activate this feature. You can assign a value to the SVCTIMEOUT parameter in the UBBCONFIG file or by dynamically changing the TASVCTIMEOUT attribute in TMMIB. We recommend that you set the value of SVCTIMEOUT or TASVCTIMEOUT to at least two to three times the number of seconds it takes for your longest running service to process a request. Setting the service timeout in this way guarantees that the BEA Tuxedo system removes only frozen processes. This section describes the causes and results of service timeout errors, and explains how the BEA Tuxedo system reports such errors. Advice about how to handle errors is also provided.
When a timeout occurs, the BEA Tuxedo system terminates the server process running the frozen service (but not its child processes, if any). It then returns a TPESVCERR error, indicating that an unknown problem occurred during processing. In a conversational service, the conversation event TPEVSVCERR is returned. The BEA Tuxedo system reports a service timeout through the following three mechanisms.