Professional Documents
Culture Documents
The purpose of this document is to provide detailed information for the various timeout settings in a PeopleSoft environment.
Chapters 2 and 3 provide general guidelines for setting timeout parameters as well as troubleshooting tips (for when you suspect a time-out related
issue)..
Chapter 4 lists each timeout-related parameter, along with these details:
1. Name of timeout setting
2. Location of the setting
3. Default value
4. Description of timeout setting
5. Recommended setting to use
6. Symptoms (ie user experience and log messages) if the timeout setting is exceeded.
Since this document provides a great deal of detail on time-out parameters as well as troubleshooting tips for timeout-related issues, it may prove
to be most helpful in situations where you are troubleshooting an issue that you suspect may be caused by improperly configured timeout settings. If
you are merely looking for some general information about timeout settings, then you may want to refer to the PeopleBooks documentation instead,
as it provides a simple overview of the various timeout settings. Refer to Appendix A for additional resources (including link to PeopleBooks
documentation) for finding timeout information
Because there are numerous components involved when deploying PeopleSoft applications, setting timeout intervals involves setting configuration
parameters at multiple levels, all the way from browser to database.
The general rule to follow, is that the timeout values increase as you get farther from the database. Draw a diagram so it is easier to see. The
farthest (and thus, longest timeout) would be Load Balancer/Proxy/Firewall, followed by the browser (webprofile - session.timeout and
session.warning), followed by the tuxedo receive timeout in the webprofile, followed by the application server service timeouts for the PS processes,
followed by the database. You don't want to have one expire higher up the chain, because threads will then be left processing farther down the line.
OVERVIEW
This chapter lists various timeout settings in the PeopleSoft environment. As you’ll see, there are a considerable number of timeout settings (over twenty!).
Fortunately, most of the timeout settings will work just fine using the default setting. However, there are a few timeout settings that often need adjusted based on
your business needs. These settings are noted, with an exclamation point (!) in column 1 of the tables on the following pages.
Below is a list of all the timeout settings described in this section. The following pages contain detailed information on each of these settings.
PEOPLESOFT APPLICATION: WEB PROFILE TIMEOUT PARAMETERS
1. Inactivity Warning
! 2. Inactivity Logout
3. HTTP Session Inactivity (Authenticated Users)
4. HTTP Session Inactivity (Public Users)
5. Disconnect Timeout (Jolt Settings)
6. Send Timeout (Jolt Settings)
! 7. Receive Timeout (Jolt Settings)
Inactivity Warning Description: The amount of idle time before User Experience: A pop-up displays with this message
1
warning users that their browser session is (message may be different if you chose to override the default
about to expire. They can continue with their message)
Location: PeopleTools -> Web Profile -> current session by clicking the OK button in Your session is about to be timed out. As a security precaution, sessions end after x
Web Profile Configuration -> <your web the pop-up message. minutes of inactivity. Click OK to continue your current session.
profile> -> Security Tab If a user doesn't respond, the session ends
and the expired connection page appears. Log Messages:
If http access logging is enabled, PIA_access.log shows
Default Value: 1080 Seconds (18 mins) Recommendations: This setting is typically ‘WEBLIB_TIMEOUT.PT_TIMEOUTWARNING’ request
set a few minutes less than the 'Inactivity
Logout' value. Note that you can suppress
this warning by setting this value to be greater
than the sessionTimeout value
Receive Timeout (Jolt Settings) Description: Specify how long the client User Experience: A page is displayed, with this message:
7
servlet should wait after issuing a Jolt Request An Error has occurred.
! Location: PeopleTools -> Web Profile ->
Web Profile Configuration -> <your web
for a response from the application server. If your attempt fails, please contact your system administrator.
Please make sure Webserver and Appserver are up. null.
profile> -> Security Tab Make sure that this value is also greater than
your application server online service Log Messages:
timeouts, such as the Service Timeout setting PIA_stdout.log (or NTService log for Windows) shows this
Default Value: 1300 seconds (~ 22 mins.) ‘timeout error’ message:
for PSAPPSRV that appear in the
PSAPPSRV.CFG configuration file on the bea.jolt.ServiceException: bea.jolt.JoltRemoteService(ICPanel)call():
Timeout\nbea.jolt.SessionException: Connection recv error\nbea.jolt.JoltException:
application server.
[2] NwHdlr.recv(): Timeout Error
Note. Ideally, this timeout should also be
greater than the Tuxedo SANITY_SCAN PIA_servletX.log shows this message:
setting (BLOCKTIME * SCANUNIT). SEVERE psft.pt8.net.NetReqRepSvc sendRequest
bea.jolt.JoltRemoteService(ICPanel)call(): Timeout
Recommendations: This value should be set SEVERE psft.pt8.net.NetReqRepSvc sendRequest
A Jolt error has occurred while communicating with the Application server. Cancel the current
equal or greater than the maximum operation and retry. If the problem persists contact your system administrator. Error Code:100
online service timeout value on SEVERE psft.pt8.net.NetReqRepSvc sendRequest Application Server last connected
the application server. (see the ‘Application //123.45.6.78_9000
Server Timeout Settings’ section for more SEVERE psft.pt8.psc service bea.jolt.JoltRemoteService(ICPanel)call(): Timeout
SEVERE psft.pt8.psc service Web Server last connected abc.oracle.com:80
details on service timeout) SEVERE psft.pt8.psc service Please make sure Webserver and Appserver are up. null
8 Permission List - Time-Out Description: Specify an interval during which If user is idle for longer than the largest timeout value in their
Minutes a given permission list applies. The interval permission lists, then the following occurs:
starts for a user to which the permission list is
assigned when that user signs in. When the
Location: PeopleTools->Security-> timeout period elapses, the user's online User Experience: User’s browser session will be terminated
Permission & Roles -> Permission Lists session is terminated. If a user belongs to and the page will display message:
Default Value: By default, the “Never Time- multiple permission lists, the largest timeout Your PeopleSoft connection has expired.
Out” option is selected which means that value from among those permission lists is
For increased security on this site, connections are expired after x minutes of
the web profile timeout values will be used applied to the user's session during signon.
inactivity.
instead of permission list time-out value The permission list timeout is effective only if
its value is less than the web server session-
timeout. This means that all of the permission Log Messages:
list timeouts for a given user must be less than
the web server session-timeout to be effective. PIA_servletsx.log.x shows message below (in this
However, the Inactivity Warning timeout still example, the permission list timeout was set to 240
applies. seconds):
If using this parameter, make certain that no MM/DD/YY HH:MM:SS.....unknown WARNING
permissions lists are using the ‘Never Time- psft.pt8.auth.PSAuthenticator isAuthExpired PS_TOKEN has expired.
Authentication Expiration Time=....http session timeout=240000
Out’ option as the value is not taken into effect
if some permission lists, for a given user, are If http access logging is enabled, request ‘cmd=expire’
not set. will be logged to PIA_access.log
Recommendations: Whether you use this
value is dependent on your business needs.
However, note that if higher values are set,
then more web server memory is needed as
sessions will remain in heap longer.
Authentication Token expiration Description: This is really the expiration time As long as a user remains signed on, the expiration of the PS
9
Token will not impact the user in any way.
time for cookie PS_TOKEN for PeopleSoft SSO.
In other words this is only relevant during the GetCertificate
When using just one PS environment, this
request during Single Signon.
"Authentication Token expiration time" is not
Location: PeopleTools->Security-> applicable since SSO is not being used.
Security Objects -> Single Signon
This parameter is not a Timeout parameter
Default Value: 720 minutes (12 hours). used the way you would think. What happens
is that you set the time in the Content (let's
assume 2 minutes), not within the Portal.
When the user logs into the Portal, their token
is created, and it contains the token creation
time. Now, when the user is in the Portal and
navigates to the Content within the 2 minutes,
then they will log successfully into the Content
using the Single Signon. However, if they go
from the Portal into the Content after two
minutes have passed, they will get a signon
screen prompting to log in again. If the user
does log into the Portal and navigate to the
Content within 2 minutes time, then the
session created on the Content never times
out. It is not talking of time of inactivity, as it
may sound. The person can be within the
Portal and navigate anywhere. If they click on
the Content link before the 2 minutes, then
they will be able to go to the Content just fine.
If they clicks on it after 2 minutes of login into
the Portal, then it will require re-login.
[Work Listener] Init Timeout Description: Specify the amount of time that's
13
allowed for the WSL process to start.
This value is required ONLY for three-tier
Location: psappsrv.cfg located in directory
<PS_CFG_HOME>/appserv/<DOMAIN_NAME> connections.
Service Timeout Description: Maximum time that the app User Experience: If user’s transaction times out due to
15
server process will run a given process before insufficient service timeout setting, they will get this message:
The value is measured in seconds In some cases, the PIA code adds 240 second padding
to the value for ‘Inactivity Logout’. If the Web Profile has
"HTTP Session Inactivity" less than the "Inactivity
Logout", then it does NOT add 240 seconds, else it adds
that value, so that if cmd=expire request arrives right
when the session is about to expire, it does not cause
incomplete execution of the expiration logic due to not
having access to the user's Http Session.
! Location:
For Apache RPS: httpd.conf
WebLogic Server terminated
! Location:
This will vary depending on the type of load
from WebLogic Server load balancer timeout setting is too low, user will get returned
to search page. Or get a “page no longer available” message.
balancer that you have (eg F5, Cisco ACE, Recommendations: The Load Balancer's
etc). Please consult with load balancer timeout should be higher than the Web Profile
vendor to find out where to set load "Inactivity Logout" timeout. Refer to
balancer timeout. document 653998.1 for additional details
regarding configuration of load balancers in
Default Value: This will vary depending on PeopleSoft environments.
the type of load balancer that you are using
Copyright © 2012 Oracle, Inc. All rights reserved. 19
OTHER TIMEOUT SETTINGS (PROXY, LOAD BALANCER, DATABASE)
Parameter Name/ Description/Recommendations Symptoms if/when timeout occurs for this Parameter
Location/
Default Value
Oracle DB SQLNET.EXPIRE_TIME Description: The time interval to send a User Experience: A page is displayed, with this message:
25
probe to verify that client/server connections An error has occurred
Location: are active. You may attempt to sign in again
Note that if Oracle database clients are idle, If your attempt fails, please contact your System Administrator
This parameter is located in file
‘SQLNET.ORA’ on the Database Server they may be be disconnected from the
database server. The “sqlnet.expire_time” Log Messages:
parameter is used to prevent the disconnect. If tracesql is set to 31, this message is logged in tracesql
PSAPPSRV....QEPPOC RC=0 Dur=0.000148 COM Stmt=SELECT VERSION FROM
Default Value: 0 (Meaning: Disable PSVERSION WHERE OBJECTTYPENAME = 'SYS'
detection for dead connections) Recommendations: 10 minutes ...
PSAPPSRV....notSamTran RC=-1 Dur=0.000000 XER rtncd=414813456 msg=
PSAPPSRV....notSamTran RC=0 Dur=0.000015 ERR rtncd=3135 msg=ORA-03135:
connection lost contact Process ID: 6574 ...
PSAPPSRV....QEPPOC RC=0 Dur=0.000090 Disconnect