Web Server Timeouts
You specify web server timeouts using the Web Profile Configuration component (WEB_PROFILE). To access these settings in PIA, select , then select the appropriate page.
The following table provides basic information about the web server timeout settings, which are more completely documented in the PeopleTools Portal Technology PeopleBook.
|
Page Element |
Page Name |
Description |
Default |
|---|---|---|---|
|
Inactivity Warning |
Security |
Specify how long the portal should wait before warning users that their browser session is about to expire. They can continue with their current session by clicking the OK button in the message. If a user doesn't respond, the session ends and the expired connection page appears. Suppress this warning by setting this value to be greater than the sessionTimeout value. |
1080 seconds (18 minutes) |
|
Inactivity Logout |
Security |
Specify the inactivity timeout interval of the PeopleSoft application for which the user is currently authenticated. When the interval passes with no user activity, the user's browser displays the page specified by the Expire Page - Page field on the Web Profile Configuration - Look and Feel page. Note: Depending on the application implementation, authenticated users might also experience an HTTP session inactivity timeout. |
1200 seconds (20 minutes) |
|
Authenticated Users - HTTP Session Inactivity |
Security |
Specify the HTTP session inactivity timeout interval that applies to authenticated users. When the interval passes with no user activity, the web server discards all session information, including cached page states. The next time the user submits a request, the web server creates a new HTTP session. If not set, the HTTP interval for an authenticated user is the same value as the inactivity logout. |
0 seconds for all profile types. |
|
Public Users - HTTP Session Inactivity |
Security |
Specify in seconds the inactivity timeout interval that applies to public users. When the interval passes with no user activity, the web server discards all session information, including cached page states. The next time the user submits a request, the web server creates a new HTTP session. Unlike authenticated users, public users are not signed out of their PeopleSoft application when this interval expires. However, PIA releases their application states from memory. If users click a link, they regain access to the application at the search dialog. This setting prevents an overload of web server resources for inactive public users. |
DEV, KIOSK profile: 1200 seconds (20 minutes). TEST, PROD profile: not set. |
|
Disconnect Timeout |
Security |
Specify the amount of time to wait before disconnecting the Jolt connection. A value of 0 seconds (the default) means no limit. This means that the client connection must be retained throughout the session. If the connection becomes invalid (due to one one of the other timeouts) the session will be expired. Note: If you specify 0 seconds, the Jolt client attempts to connect the Jolt Server Handler (JSH) in RETAINED mode. If any positive value is specified, the Jolt client attempts to connect the JSH in RECONNECT mode. |
0 seconds |
|
Send Timeout |
Security |
Specify the maximum time permitted between the sending of the Jolt Request by the client servlet and its full receipt on the application server. Note: You might need to increase this value where a large amount of data is being sent to the application server, or the network is slow. |
50 seconds |
|
Receive Timeout |
Security |
Specify how long the client servlet should wait after issuing a Jolt Request for a response from the application server. This value should be considerably larger than the Send Timeout. Make sure that this value is also greater than your application server online service timeouts, such as the Service Timeout setting for PSAPPSRV that appear in the PSAPPSRV.CFG configuration file on the application server. Note: Ideally, this timeout should also be greater than the Tuxedo SANITY_SCAN setting (BLOCKTIME * SCANUNIT). |
1300 seconds |
You specify the web server session-timeout using the Inactivity Logout property and HTTP Session Inactivity property in the web profile.
PeopleSoft Interaction Hub normally depends on a content reference timeout setting to determine how long to wait for a pagelet to load before it considers the pagelet to be unavailable. However, if the remote server is unavailable, the content reference timeout setting is ignored. If the portal can’t establish a connection to the remote host, it uses the default system timeout.
The default system timeout defaults to 20 seconds. If you expect the remote server to be slow or down for longer than 20 seconds, you should specify a longer default system timeout, by configuring your web server to set the defaultConnectTimeout JVM environment variable to an appropriate value using one of the following procedures.
For example,
SET JAVA_OPTIONS_WIN32=-server -Xmsnnnm -Xmxnnnm -XX:MaxPermSize=nnnm
-Dsun.net.client.defaultConnectTimeout=default_timeoutWhere default_timeout is the number of milliseconds that the portal should wait to establish the connection to the host.
See Your web server documentation for instructions on modifying this JVM environment variable.