7/18/2013

PeopleTools 8.5x Timeout Settings

Last Updated: March 2013

Copyright © 2012 Oracle, Inc. All rights reserved. 1

Chapter 1 – Introduction and Overview of Document .............................................................................................3

Chapter 2 – General Guidelines for Setting Timeout Parameters ..........................................................................4

Chapter 3: How to Troubleshoot Time-Out Related Issues ....................................................................................5

Chapter 4: Timeout Parameters in a PeopleSoft Environment ..............................................................................6

Overview ......................................................................................................................................................................... 6
PeopleSoft Application: Web Profile Timeout Parameters ....................................................................................... 7
Inactivity Warning .................................................................................................................................................. 7
Inactivity Logout ..................................................................................................................................................... 7
HTTP Session Inactivity (Authenticated Users) ..................................................................................................... 8
HTTP Session Inactivity (Public Users) ................................................................................................................. 8
Disconnect Timeout (Jolt Settings) ......................................................................................................................... 9
Send Timeout (Jolt Settings) ................................................................................................................................... 9
Receive Timeout (Jolt Settings) ............................................................................................................................ 10
PeopleSoft Applicaton: Other Timeout Parameters (Outside of Web Profile) .......................................................11
Permission List - Time-Out Minutes ..................................................................................................................... 11
Authentication Token expiration time ................................................................................................................... 12
Application Server Timeout Parameters ....................................................................................................................13
[JOLT Listener] Client Cleanup Timeout ............................................................................................................. 13
[JOLT Listener] Init Timeout................................................................................................................................ 13
[Workstation Listener] Client Cleanup Timeout ................................................................................................... 13
[Work Listener] Init Timeout ................................................................................................................................ 14
Spawn Threshold .................................................................................................................................................. 14
Service Timeout .................................................................................................................................................... 15
Restart Period (PSBRKDSP_dflt, PSSUBDSP_dflt, PSPUBDSP_dflt) .............................................................. 15
TM_RESTARTSRV ............................................................................................................................................. 16
TM_BOOTTIMEOUT .......................................................................................................................................... 16
Tuxedo Sanity Scans and Blocking Timeouts:...................................................................................................... 17
WebLogic TimeOut Parameters..................................................................................................................................18
session-timeout ..................................................................................................................................................... 18
TimeoutSecs .......................................................................................................................................................... 18
Max Inactive Interval ............................................................................................................................................ 18
Other Timeout Settings (Proxy, Load Balancer, Database) ......................................................................................19
Proxy Plug-In WLIOTimeoutSecs ....................................................................................................................... 19
Load Balancer TimeOut ........................................................................................................................................ 19
Oracle DB SQLNET.EXPIRE_TIME................................................................................................................... 20

Appendix A – Where to Find Additional Documentation for Timeout Settings ..................................................21

Copyright © 2012 Oracle, Inc. All rights reserved. 2

Chapter 1 – Introduction and Overview of Document

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

Copyright © 2012 Oracle, Inc. All rights reserved. 3

Chapter 2 – General Guidelines for Setting Timeout Parameters

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.

Copyright © 2012 Oracle, Inc. All rights reserved. 4

Chapter 3: How to Troubleshoot Time-Out Related Issues
There are a couple different issues that can occur if time-out parameters are not set properly:
 Issue #1: If any of the timeout values are too low, users may not be able to successfully complete some of their longer-running transactions
or users may get abruptly exited out of the PeopleSoft application..
 Issue #2: If timeout values are set too high, and if there is a larger user base and/or users running a lot of long-running transactions, it may
result in the system resources getting overloaded which could result in slow performance and/or app server/web server resource-related
issues (eg running out of memory and/or sockets)

Below are tips on troubleshooting Issue#1 and Issue #2

Troubleshooting Tips for Issue#1: Timeout value(s) are too low

If users are experiencing issues that you suspect may be related to timeout settings being too low, do the following:
 Review the timeout settings, in Chapter 4, placing the most emphasis on the timeout settings with an exclamation point in front of them, as
these are the timeout settings that most commonly cause issues. Validate that the settings are high enough, for longest running transaction.
Also, validate that your timeout settings increase as you get farther from the database
 Refer to Chapter 4 and review the “Symptoms….” column, and check against your logs and what users are reporting, in order to see if any of
the symptoms match against the problem you are seeing.
 If you have any transactions that take a long time to complete (eg 3+minutes), try to optimize the transactions so that timeout settings do not
have to be set too high. You may need to work with your DBA in order to optimize long-running SQL’s.

Troubleshooting Tips for Issue#2: Timeout value(s) are too high

If you suspect that high timeout settings are contributing to performance issues or overloaded server resources (CPU/memory), do the following:
 Review the timeout settings, in Chapter 4 placing the most emphasis on the timeout settings with an exclamation point in front of them. If you
have timeout settings that are considerably higher than recommended settings, then lower them if possible. Note that if you have long-
running transactions, you will not be able to lower some of the timeout settings, unless you are able to first optimize the long-running
transactions so that they finish faster.
 Ideally, all transactions should complete in less than 3-5 minutes. You may want to set logfence=4 on your app server in order to determine
which transactions are taking a long time to complete. This can be done as follows:
1. Set “logfence=4” in psappsrv.cfg in order to log each user request (if you do not have "Allow Dynamic Changes" set to “Y”, you
will need to go into PSADMIN and reload the configuration and restart the app server, in order to pick up the change)
2. After making the above change, file APPSRV_MMDD.log will show the transaction “elapsed time”. So you can look for
transactions taking longer amounts of time. You may need to work with your DBA in order to optimize long-running SQL’s.
 Customers sometimes have out-of-memory errors on the web server due to setting ‘session inactivity’ timeout to a high value. This occurs
because the session information is stored in java heap. So the higher the ‘session inactivity’ timeout is set, the longer the session remains in
web server heap memory. If there are excessive active web server sessions (eg 500 or higher), the java heap may be depleted, resulting in
a web server ‘out of memory’ error. If using WebLogic, you can check the number of web server sessions via the WebLogic console as
described in document 662319.1. When viewing session info, via WebLogic console, check ‘max inactive interval’ to determine how long
sessions remain active before being removed.

Copyright © 2012 Oracle, Inc. All rights reserved. 5

Chapter 4: Timeout Parameters in a PeopleSoft Environment

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)

PEOPLESOFT APPLICATON: OTHER TIMEOUT PARAMETERS (OUTSIDE OF WEB PROFILE)

8. Permission List - Time-Out Minutes
9. Authentication Token expiration time

APPLICATION SERVER TIMEOUT PARAMETERS

10. [JOLT Listener] Client Cleanup Timeout
11. [JOLT Listener] Init Timeout
12. [Workstation Listener] Client Cleanup Timeout
13. [Work Listener] Init Timeout
14. Spawn Threshold
! 15. Service Timeout
16. Restart Period (PSBRKDSP_dflt, PSSUBDSP_dflt, PSPUBDSP_dflt)
17. TM_RESTARTSRV
18. TM_BOOTTIMEOUT
19. Tuxedo Sanity Scans and Blocking Timeouts: SCANUNIT/SANITYSCAN/BLOCKTIME

WEBLOGIC TIMEOUT PARAMETERS

20 session-timeout
21 TimeoutSecs
22 Max Inactive Interval

OTHER TIMEOUT SETTINGS (PROXY, LOAD BALANCER AND DATABASE)

! 23 Proxy Plug-In WLIOTimeoutSecs
! 24 Load Balancer TimeOut
25 Database SQLNET.EXPIRE_TIME
Copyright © 2012 Oracle, Inc. All rights reserved. 6
PEOPLESOFT APPLICATION: WEB PROFILE TIMEOUT PARAMETERS
Name / Location / Default Value
Inactivity Warning
1
Location: PeopleTools -> Web Profile ->
Web Profile Configuration -> <your web
profile> -> Security Tab
Default Value: 1080 Seconds (18 mins)
Inactivity Logout
2 Description: Amount of idle time before user
! Location: PeopleTools -> Web Profile ->
Web Profile Configuration -> <your web
profile> -> Security Tab
Default Value: 1200 Seconds (20 mins)
Copyright © 2012 Oracle, Inc. All rights reserved.
Description/Recommendations
Description: The amount of idle time 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 pop-up message.
If a user doesn't respond, the session ends
and the expired connection page appears.
Recommendations: This setting is typically
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
is logged out. 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.
Recommendations: This should be set
based on your business requirements. But
note that the higher this value is set, the more
web server heap is needed as the session
information is stored in the web server heap.
Symptoms if/when timeout occurs for this Parameter
User Experience: A pop-up displays with this message
(message may be different if you chose to override the default
message)
Your session is about to be timed out. As a security precaution, sessions end after x
minutes of inactivity. Click OK to continue your current session.
Log Messages:
If http access logging is enabled, PIA_access.log shows
‘WEBLIB_TIMEOUT.PT_TIMEOUTWARNING’ request
User Experience: An expire page is displayed (message
may be different if you chose to override default message)
Your PeopleSoft connection has expired.
For increased security on this site, connections are expired after x minutes of
inactivity.
Log Messages:
 PIA_servlet.log shows a ‘PS_TOKEN has expired’
message. Example:
WARNING psft.pt8.auth.PSAuthenticator isAuthExpired PS_TOKEN has
expired. Authentication Expiration Time=1328121121000, current time in
milliseconds=1328121481891; http session timeout=360000

 If http access logging is enabled, PIA_access log shows a
logout request. Example:
/psp/ps/EMPLOYEE/PT_LOCAL/?cmd=expire
7
PEOPLESOFT APPLICATION: WEB PROFILE TIMEOUT PARAMETERS
Name / Location / Default Value
3 HTTP Session Inactivity
(Authenticated Users)
Location: PeopleTools -> Web Profile ->
Web Profile Configuration -> <your web
profile> -> Security Tab
Default Value: 0 seconds (Setting to 0
makes it take same value as inactivity
logout)
4 HTTP Session Inactivity (Public
Users)
Location: PeopleTools -> Web Profile ->
Web Profile Configuration -> <your web
profile> -> Security Tab
Default Value: 0 seconds (Setting to 0
makes it take same value as inactivity
logout)
Copyright © 2012 Oracle, Inc. All rights reserved.
Description/Recommendations
Description: Amount of idle time before 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.
Recommendations: This is typically set to 0
so that it takes same value as inactivity logout.
If you set it lower, than inactivity logout, then
the web server does not use as much memory
since session info is discarded sooner. But
disadvantage is that user could lose info if in
they are in middle of transaction and remain
inactive longer than the value you set for
HTTP Session Inactivity.
If you set ‘HTTP Session Inactivity’ higher
than inactivity logout, it has same effect as
setting a higher inactivity logout value.
Description: The amount of idle time before
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.
Recommendations: This is typically set to 0
so that it takes same value as inactivity logout
This should be set based on your business
requirements. But note that the higher this
value is set, the more web server heap is
needed as the session information is stored in
the web server heap
Symptoms if/when timeout occurs for this Parameter
User Experience:
If user resumes activity AFTER the 'HTTP Session Inactivity'
timeout but BEFORE the 'Inactivity Logout', then they will
notice the following:
1. If user is navigating through menu, when resuming
activity, they will be unaffected
2. If user is in the middle of a transaction when resuming
activity, they will remain logged in, but will be returned to
search menu. Any information, that was entered in
transaction (but not yet saved), will be lost
Log Messages:
There are no messages logged when this timeout occurs.
However, if you are monitoring HTTP sessions via the
WebLogic console (see doc# 661808.1), you will see that
WebLogic removes the session when it has been idle for a
time longer than that specificed in HTTP Session Inactivity.
If the user resumes activity after the WebLogic session has
been removed (but before the ‘Inactivit Logout’), then a new
Weblogic session is created for the user.
User Experience:
1. If user is navigating through menu, when resuming
activity, they will be unaffected
2. If user is in the middle of a transaction when resuming
activity, they will remain logged in, but will be returned to
search menu. Any information, that was entered in
transaction (but not yet saved), will be lost. In some
situations, user may receive error (example ‘Error has
occurred’ if idle time was exceeded while in middle of
transactions)
Log Messages:
No messages are logged when timeout occurs. However, if
you are monitoring HTTP sessions via the WebLogic console
(see 661808.1), you will see that WebLogic removes the
session when it has been idle for a time longer than that
specificed in Public User HTTP Session Inactivity (if no time is
specified in ‘Public User HTTP Session Inactivity’, then the
value in ‘Inactivity Logout’ is used)
If the user resumes activity after the WebLogic session has
been removed (but before the ‘Inactivity Logout’, then a new
Weblogic session is created for the user.
8
PEOPLESOFT APPLICATION: WEB PROFILE TIMEOUT PARAMETERS
Name / Location / Default Value
5 Disconnect Timeout (Jolt
Settings)
Location: PeopleTools -> Web Profile ->
Web Profile Configuration -> <your web
profile> -> Security Tab
Default Value: 0 seconds (A value of 0
means no limit)
Description/Recommendations
Description: 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 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.
Symptoms if/when timeout occurs for this Parameter
User Experience: This setting has no impact on the user
Log Messages:
No messages are logged. However, note that messages such
as the following in TUXLOG.MMDDYY, could indicate issues
with reconnecting. If you see these messages set the
Disconnect Timeout back to the default value of 0 seconds:
JOLT_CAT:1596: "ERROR: Received J_RECONNECT
message with invalid context"


Recommendations: Keep the default value

of 0 seconds

6 Send Timeout (Jolt Settings) Description: Specify the maximum time

Location: PeopleTools -> Web Profile ->
Web Profile Configuration -> <your web
profile> -> Security Tab
Default Value: 50 seconds
permitted between the sending of the Jolt
Request by the client servlet and its full receipt
on the application server.
Recommendations: The default value
should be used. Note that it is rare to see
issues where the request is not sent to
application server in a timely manner. You
would have to have severe network issues
and/or send a very large request for this to be
a problem.

Copyright © 2012 Oracle, Inc. All rights reserved. 9

PEOPLESOFT APPLICATION: WEB PROFILE TIMEOUT PARAMETERS
Name / Location / Default Value
Receive Timeout (Jolt Settings)
7
! Location: PeopleTools -> Web Profile ->
Web Profile Configuration -> <your web
profile> -> Security Tab
Default Value: 1300 seconds (~ 22 mins.)
Copyright © 2012 Oracle, Inc. All rights reserved.
Description/Recommendations
Description: Specify how long the client
servlet should wait after issuing a Jolt Request
for a response from the application server.
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).
Recommendations: This value should be set
equal or greater than the maximum
online service timeout value on
the application server. (see the ‘Application
Server Timeout Settings’ section for more
details on service timeout)
Symptoms if/when timeout occurs for this Parameter
User Experience: A page is displayed, with this message:
An Error has occurred.
If your attempt fails, please contact your system administrator.
Please make sure Webserver and Appserver are up. null.
Log Messages:
 PIA_stdout.log (or NTService log for Windows) shows this
‘timeout error’ message:
bea.jolt.ServiceException: bea.jolt.JoltRemoteService(ICPanel)call():
Timeout\nbea.jolt.SessionException: Connection recv error\nbea.jolt.JoltException:
[2] NwHdlr.recv(): Timeout Error
 PIA_servletX.log shows this message:
SEVERE psft.pt8.net.NetReqRepSvc sendRequest
bea.jolt.JoltRemoteService(ICPanel)call(): Timeout
SEVERE psft.pt8.net.NetReqRepSvc sendRequest
A Jolt error has occurred while communicating with the Application server. Cancel the current
operation and retry. If the problem persists contact your system administrator. Error Code:100
SEVERE psft.pt8.net.NetReqRepSvc sendRequest Application Server last connected
//123.45.6.78_9000
SEVERE psft.pt8.psc service bea.jolt.JoltRemoteService(ICPanel)call(): Timeout
SEVERE psft.pt8.psc service Web Server last connected abc.oracle.com:80
SEVERE psft.pt8.psc service Please make sure Webserver and Appserver are up. null
 If you are monitoring HTTP sessions via the WebLogic
console (as described in My Oracle Support document
661808.1), you will see that WebLogic removes the user’s
session
 If you are monitoring the jolt sessions (via psadmin ‘client
status’), you’ll see that the user’s jolt session (which was
previously status ‘BUSY’), has been terminated.
10
PEOPLESOFT APPLICATON: OTHER TIMEOUT PARAMETERS (OUTSIDE OF WEB PROFILE)
Parameter Name/
Location/
Default Value
8 Permission List - Time-Out
Minutes
Location: PeopleTools->Security->
Permission & Roles -> Permission Lists
Default Value: By default, the “Never Time-
Out” option is selected which means that
the web profile timeout values will be used
instead of permission list time-out value
Copyright © 2012 Oracle, Inc. All rights reserved.
Description/Recommendations Symptoms if/when timeout occurs for this Parameter
Description: Specify an interval during which If user is idle for longer than the largest timeout value in their
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
timeout period elapses, the user's online User Experience: User’s browser session will be terminated
session is terminated. If a user belongs to and the page will display message:
multiple permission lists, the largest timeout Your PeopleSoft connection has expired.
value from among those permission lists is
For increased security on this site, connections are expired after x minutes of
applied to the user's session during signon.
inactivity.
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.
11
PEOPLESOFT APPLICATON: OTHER TIMEOUT PARAMETERS (OUTSIDE OF WEB PROFILE)
Parameter Name/ Description/Recommendations Symptoms if/when timeout occurs for this Parameter
Location/
Default Value

Authentication Token expiration
9
time
Location: PeopleTools->Security->
Security Objects -> Single Signon
Default Value: 720 minutes (12 hours).
Description: This is really the expiration time As long as a user remains signed on, the expiration of the PS
Token will not impact the user in any way.
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
applicable since SSO is not being used.
This parameter is not a Timeout parameter
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.

Copyright © 2012 Oracle, Inc. All rights reserved. 12

APPLICATION SERVER TIMEOUT PARAMETERS
Parameter Name/
Location/
Default Value
10 [JOLT Listener] Client Cleanup
Timeout
Location: psappsrv.cfg located in directory
<PS_CFG_HOME>/appserv/<DOMAIN_NAME>
(refer to the Jolt section in this document)
Default Value: 10 Minutes
[JOLT Listener] Init Timeout
11
Location: psappsrv.cfg located in directory
<PS_CFG_HOME>/appserv/<DOMAIN_NAME>
Default Value: 5 Minutes
12 [Workstation Listener] Client
Cleanup Timeout
Location: psappsrv.cfg located in directory
<PS_CFG_HOME>/appserv/<DOMAIN_NAME>
(refer to the Jolt section in this document)
Default Value: 60 Minutes
Copyright © 2012 Oracle, Inc. All rights reserved.
Description/Recommendations
Description: Maximum time that the jolt
session stays active
Recommendations: We recommend default
timeout. If number is too high, more app
server resources are allocated. If it is too low,
there may be unnecessary reinstatiation of
resources for clients who pass inactivity
interval
Description: Specify the amount of time that's
allowed for the JSL process to start.
Recommendations: We recommend default
setting. It is not necessary to adjust this
setting.
Description: Maximum time that the Work
Station session stays active
This value is required ONLY for three-tier
connections.
Recommendations: We recommend default
timeout. If number is too high, more app
server resources are allocated. If it is too low,
there may be unnecessary reinstatiation of
resources for clients who pass inactivity
interval
Symptoms if/when timeout occurs for this Parameter
User Experience: This setting doesn't affect user
experience. Note that if user runs another transaction after
their Jolt Session has been terminated, then another Jolt
Session is activated and this process is invisible to user
Log Messages:
 When using jolt pooling (which is enabled, by default), a
jolt session will not be removed unless no users have
accessed it for a time greater than that specified in ‘Client
Cleanup Timeout’. So this may not occur often. When a
jolt session does remain idle, for longer than the client
cleanup timeout setting, then the following is logged to
TUXLOG.MMDDYY:
INFO: Userid: [JPOOL_1], Clientid: [abc] timed out due to inactivity
WARN: Forced shutdown of client; user name 'JPOOL_1'; client name 'abc'
 If you are monitoring the jolt sessions (via psadmin ‘client
status’), you’ll see that the jolt session (eg ‘JPOOL_1’) is
no longer present
User Experience: This setting doesn't affect user
experience. Note that if user runs another transaction after
their WorkStation Session has been terminated, then another
WorkStation Session is activated and this process is invisible
to user
13
APPLICATION SERVER TIMEOUT PARAMETERS
Parameter Name/
Location/
Default Value
[Work Listener] Init Timeout
13
Location: psappsrv.cfg located in directory
<PS_CFG_HOME>/appserv/<DOMAIN_NAME>
Default Value: 5 Minutes
Spawn Threshold
14
Location: psappsrv.cfg located in directory
<PS_CFG_HOME>/appserv/<DOMAIN_NAME>
Default Value: 1,600:1:1
Copyright © 2012 Oracle, Inc. All rights reserved.
Description/Recommendations Symptoms if/when timeout occurs for this Parameter
Description: Specify the amount of time that's
allowed for the WSL process to start.
This value is required ONLY for three-tier
connections.
Recommendations: We recommend default
setting. It is not necessary to adjust this
setting.
Description: Applies only if spawning is
enabled (ie “Max Instances > Min Instances” in
psappsrv.cfg)
Specify the rates at which PSAPPSRV
processes spawn and decay.
The spawn rate is determined by the last two
numbers, and the decay rate is determined by
the first two numbers.
Using the default value as an example, for the
spawn rate of 1,1 an extra PSAPPSRV
process is spawned if there is at least 1
oustanding service request on the application
server request queue for 1 second or more.
This spawning will continue until the
PSAPPSRV Max Instances value is reached.
For the decay rate of 1,600 a server process is
decayed if less than 1 service request is in the
application server request queue for 600
seconds (ten minutes) or more.
Recommendations: These default settings
should not be changed
14
APPLICATION SERVER TIMEOUT PARAMETERS
Parameter Name/
Location/
Default Value
Service Timeout
15
! Location: psappsrv.cfg located in directory
<PS_CFG_HOME>/appserv/<DOMAIN_NAME>
Default Value:
This setting is defined for each type of server
process. Default settings are as follows:
 PSAPPSRV: 300 seconds (5 minutes)
 PSSAMSRV: 300 seconds
 PSQCKSRV: 300 seconds
 PSQRYSRV: 1200 seconds (20 minutes)
 PSBRKHND_dflt: 1200 seconds
 PSSUBHND_dflt: 1200 seconds
 PSPUBHND_dflt: 1200 seconds
16 Restart Period (PSBRKDSP_dflt, Description: Specify how long each
dispatcher should wait before redispatching a
PSSUBDSP_dflt, PSPUBDSP_dflt) message if the associated handler has not
Location: psappsrv.cfg located in directory
<PS_CFG_HOME>/appserv/<DOMAIN_NAME>
Default Value: 120 seconds
Copyright © 2012 Oracle, Inc. All rights reserved.
Description/Recommendations
Description: Maximum time that the app
server process will run a given process before
it is terminated by Tuxedo
If the service has not completed
within the allotted time period
Tuxedo will terminate the server
processing being run and then
restart the server process.
Recommendations: For each server process,
specify the longest time that any service is
expected to take.
But note that if it is set high, then long-running
(or runaway processes) will consume more
resources
started processing it.
Symptoms if/when timeout occurs for this Parameter
User Experience: If user’s transaction times out due to
insufficient service timeout setting, they will get this message:
An Error has occurred.
Please make sure Webserver and Appserver are up. null.
Log Messages:
 TUXLOG.MMDDYY shows this message:
WARN: Server(7212) processing terminated with SIGKILL after SVCTIMEOUT
WARN: Server APPSRV/2 terminated
INFO: Server APPSRV/2 being restarted
 PIA_stdout.log or PIA_stderr.log shows:
bea.jolt.ServiceException: TPESVCERR - server error while handling request
at bea.jolt.JoltRemoteService.decodeCALL(JoltRemoteService.java:465)
etc etc
 PIA_servletX.log.X shows this message:
SEVERE psft.pt8.net.NetReqRepSvc sendRequest TPESVCERR - server error while
handling request
SEVERE psft.pt8.net.NetReqRepSvc sendRequest An error occurred on the application
server within Jolt while running the service. Cancel the current operation and retry. If the
problem persists contact your system administrator. Error Code:10
SEVERE psft.pt8.net.NetReqRepSvc sendRequest Application Server last connected
//11.222.333.444_9000
SEVERE psft.pt8.psc service TPESVCERR - server error while handling request
SEVERE psft.pt8.psc service Web Server last connected myserver.us.oracle.com:8000
SEVERE psft.pt8.psc service Please make sure Webserver and Appserver are up. null
15
APPLICATION SERVER TIMEOUT PARAMETERS
Parameter Name/ Description/Recommendations Symptoms if/when timeout occurs for this Parameter
Location/
Default Value

TM_RESTARTSRV Description: Specify the time period that a Log Messages:

17
Location: psappsrv.ubx located in
directory
<PS_CFG_HOME>/appserv/<DOMAIN_NAME>
Default Value: 120 seconds
domain server process (for example,  TUXLOG.MMDDYY shows this message:
PSAPPSRV, PSWATCHSRV, PSSAMSRV) is APPSRV/1: CMDTUX_CAT:1860: ERROR: On restart, server process ID 1708
failed to initialize within 120 seconds
permitted to remain in restart mode before it is
killed by Tuxedo. This setting resolves
processes hanging during restart.
Recommendations: The default setting of 120
seconds is typically plenty of time for a process
to restart, but can be increased if needed

TM_BOOTTIMEOUT Description: Specify the time period that a Log Messages:

18
domain server process (for example,  TUXLOG.MMDDYY shows this message:
PSAPPSRV, PSWATCHSRV, PSSAMSRV) is CMDTUX_CAT:1859: ERROR: Server process ID 2224 failed to initialize within 120
Location: psappsrv.ubx located in seconds
permitted to remain in start mode before it is
directory CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
<PS_CFG_HOME>/appserv/<DOMAIN_NAME> killed by Tuxedo.

Default Value: 120 seconds Recommendations: The default setting of 120

seconds is typically plenty of time for a process
to start, but can be increased if needed

Copyright © 2012 Oracle, Inc. All rights reserved. 16

APPLICATION SERVER TIMEOUT PARAMETERS
Parameter Name/ Description/Recommendations Symptoms if/when timeout occurs for this Parameter
Location/
Default Value
19 Tuxedo Sanity Scans and Description: User Experience: A page is displayed, with this message:
 SCANUNIT: The time in seconds between An Error has occurred.
Blocking Timeouts: scans by the BBL to look for old transactions If your attempt fails, please contact your system administrator.
 SCANUNIT and time-out blocking calls. Please make sure Webserver and Appserver are up. null.
 SANITYSCAN  SANITYSCAN: A multiplier of SCANUNIT
(SCANUNIT * SANITYSCAN seconds) that sets Log Messages:
 BLOCKTIME the time between BBL checks on local servers.  PIA_stdout.log (or NTService log for Windows) shows this
(SCANUNIT * SANITYSCAN seconds) ‘timeout error’ message:
Location: psappsrv.ubx located in  BLOCKTIME: A multiplier of SCANUNIT bea.jolt.ServiceException: TPETIME - timeout occurred at
directory (SCANUNIT * BLOCKTIME) for timing-out a bea.jolt.JoltRemoteService.decodeCALL(JoltRemoteService.java:465)
<PS_CFG_HOME>/appserv/<DOMAIN_NAME> blocking call from the client
 PIA_servletX.log.X shows this message:
Default Value: Recommendations: These default settings SEVERE psft.pt8.net.NetReqRepSvc sendRequest TPETIME - timeout occured
SCANUNIT = 5 seconds should not be changed SEVERE psft.pt8.net.NetReqRepSvc sendRequest The application server is busy and the
SANITYSCAN= 2 seconds request timed out. Try again later. Error Code:13
BLOCKTIME=6000 seconds SEVERE psft.pt8.net.NetReqRepSvc sendRequest Application Server last connected
//12.345.678.988_9000
SEVERE psft.pt8.psc service TPETIME - timeout occured
SEVERE psft.pt8.psc service Web Server last connected abc.oracle.com:80
SEVERE psft.pt8.psc service Please make sure Webserver and Appserver are up. null

Copyright © 2012 Oracle, Inc. All rights reserved. 17

WEBLOGIC TIMEOUT PARAMETERS
Parameter Name/Location/Default Value Description/Recommendations Symptoms
if/when
timeout
occurs for
this
Parameter

20 session-timeout Description: This is the session timeout for the webserver.

However, note that PeopleSoft no longer uses session
Location: web.xml located in directory timeout control set on the web server. The session timeouts
<PS_CFG>/webserv/<DOMAIN_NAME>/applications/peoplesoft/PORTAL.WAR/WEB-INF set in the Web Profiles override any HTTP session timeouts
set on the webserver at runtime.
Default Value: 20 minutes
Recommendations: Starting with PeopleTools 8.49, this
setting is not used and can be ignored

21 TimeoutSecs Description: This is the session timeout for the webserver

Location: weblogic.xml located in directory
<PS_CFG>/webserv/<DOMAIN_NAME>/applications/peoplesoft/PORTAL.WAR/WEB-INF
Default Value: This parameter is not defined, by default
(same as session-timeout in web.xml, but has lower
precedence). However, note that PeopleSoft no longer uses
this value. (same as the setting in web.xml)
The session timeouts set in the Web Profiles override any
HTTP session timeouts set on the webserver at runtime.

Recommendations: Starting with PeopleTools 8.49, this

setting is not used and can be ignored

22 Max Inactive Interval Description: Number of seconds until session expires.

Location: This parameter is displayed when viewing the http session
details via the WebLogic console (as per document 661808.1)..
Default Value: This parameter is derived from the PIA code based on the
web profile settings for “inactivity logout” and “http session inactivity”.
This parameter is set by the PIA based code. The value is
determined based on these settings:
1) Web Profile “Inactivity Logout” setting
2) Web Profile “HTTP Session Inactivity” setting
3) “Permission List” setting

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.

Copyright © 2012 Oracle, Inc. All rights reserved. 18

OTHER TIMEOUT SETTINGS (PROXY, LOAD BALANCER, DATABASE)
Parameter Name/
Location/
Default Value
Proxy Plug-In WLIOTimeoutSecs
23
! Location:
For Apache RPS: httpd.conf
For OHS RPS: mod_wl_ohs.conf
For IIS RPS: iisproxy.ini
For Sun Java System: obj.conf
Default Value: 300 seconds (5 minutes)
Load Balancer TimeOut
24
! Location:
This will vary depending on the type of load
balancer that you have (eg F5, Cisco ACE,
etc). Please consult with load balancer
vendor to find out where to set load
balancer timeout.
Default Value: This will vary depending on
the type of load balancer that you are using
Copyright © 2012 Oracle, Inc. All rights reserved.
Description/Recommendations
Description: The amount of time the plug-in
waits for a response to a request from
WebLogic Server
Recommendations: Timeout
should be set to the same value
specified for the Tuxedo
Receive Timeout in your
Webprofile.
Description: The amount of time the load
balancer waits for a response to a request
from WebLogic Server
Recommendations: The Load Balancer's
timeout should be higher than the Web Profile
"Inactivity Logout" timeout. Refer to
document 653998.1 for additional details
regarding configuration of load balancers in
PeopleSoft environments.
Symptoms if/when timeout occurs for this Parameter
User Experience: The request will continue to clock until the
inactivity logout is reached. Then user’s session is
terminated
Log Messages:
 If debug logging is enabled on the proxy plug-in, then the
proxy debug log file will show some sort of timeout
message. The error may vary depending on the proxy
you are using. Below is the message from an Apache
debug log:
*******Exception type [READ_TIMEOUT] (no read after 300 seconds) raised at line
212 of ../nsapi/Reader.cpp
caught exception in readStatus: READ_TIMEOUT [os error=0, line 212 of
../nsapi/Reader.cpp]: no read after 300 seconds at line 826
 The proxy log may also show an error. The error may
vary depending on the proxy you are using. Below are
portions of the error message from an Apache log:
[error] .....trying POST /psc/ps/EMPLOYEE/.... at backend host.... got exception
'PROTOCOL_ERROR [line 835 of ../nsapi/URL.cpp]: Backend Server not
responding',
 If viewing threads from WebLogic console, you may
notice multiple threads working on the same request.
This is because the plug-in resubmits the request each
time it reaches the timeout specified in
WLIOTimeoutSecs
User Experience: The issue may vary depending on type of
load balancer, but some customers have reported that if the
load balancer timeout setting is too low, user will get returned
to search page. Or get a “page no longer available” message.
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

 PIA_servletX.log.X shows this message:

SEVERE psft.pt8.psp service VP1 123.45.6.789
http://abc.oracle.com:8801/psp/PS/?cmd=login&languageCd=ENG POST UNKNOWN ....
SEVERE psft.pt8.psp service Web Server last connected abc.oracle..com:8801
SEVERE psft.pt8.psp service Please make sure Webserver and Appserver are
up.TPESVCFAIL - application level service failure

Copyright © 2012 Oracle, Inc. All rights reserved. 20

Appendix A – Where to Find Additional Documentation for Timeout Settings

The PeopleBooks Timeout Settings can be located as follows:

-Go to the Oracle-Host PeopleBooks site located at
http://docs.oracle.com/cd/E17566_01/epm91pbr0/eng/psbooks/psft_homepage.htm
-Click on the hyperlink for your PeopleTools release. Example: PeopleTools Release 8.52 (PT)
-From the 'Administration Tools' section, click hyperlink 'PeopleTools 8.5x System and Server Administration'
-From the 'System and Server Administration' table of contents, choose 'Appendix: PeopleSoft Timeout Settings'

Additional Timeout information can also be found in the following document:

Doc ID 747389.1: PeopleTools Performance Guidelines White Paper

Copyright © 2012 Oracle, Inc. All rights reserved. 21