EBS TIMEOUT



 
1306678.1

Oracle Applications Framework - Version 12.0.4 to 12.2 [Release 12 to 12.2]

Example of time out setting:

ICX:Session Timeout - 240 (minutes)
"s_sesstimeout" context variable -  14400000 (milliseconds)
"s_oc4j_sesstimeout" context variable - 240 (minutes)
JTF_INACTIVE_SESSION_TIMEOUT - 240 (minutes)

Howeverthe user session get timed out even though the idle time is setto 4 hours.

It was determined that the cause of this session expiration was a low value of
"ICX: Limit connect" profile option.

1. To retrieve the user_id and session_id for a test user:

select USER_ID, USER_NAME
from FND_USER
where USER_NAME = '<a testuser name>';

select SESSION_ID
from ICX_SESSIONS
where USER_ID = <USER_IDretrieved previously>'
order by CREATION_DATE DESC;

The SESSION_ID being the last created for this user.

2. To check the session several times
(after each few actions performed in the Applications, until and after the time out error):

SELECTSESSION_ID, XSID, TIME_OUT, LIMIT_TIME, LIMIT_CONNECTS, COUNTER, TO_CHAR(SYSDATE,'DD-MM-YYYY HH24:MI:SS'), TO_CHAR(FIRST_CONNECT,'DD-MM-YYYY HH24:MI:SS'),TO_CHAR(LAST_CONNECT,'DD-MM-YYYY HH24:MI:SS'), DISABLED_FLAG
FROM ICX_SESSIONS
WHERE SESSION_ID = <SESSION_IDretrieved previously>

It showed that the COUNTER value reached LIMIT_CONNECTS threshold and disconnection happened.

Solution

Update the "ICX: Limit connect" profile option from1000 to 2000
(or higher, depending of your need) at Site level.

As per the definition:

"ICX: Limit Connect" is a profile option which determines the max number of connection requests a usercan make in a single session. If a user sends more requests than the value specified by this profile option in a single session, then the session will expire.

This needs to be bumped up to 2000 +, because each time session time is checked it adds anotherICX connection. This is not determined by the number of user connections.
The more ICX checks itself the more ICX connections you are going to see for a user.

How to Change User Session Timeout in e-Business Suite R12 (Doc ID 1067115.1)

1. Edit the.xml file in $INST_TOP/appl/admin directory

2. Ensure that value of profile option "ICX: Session Timeout" and autoconfig variable "s_oc4j_sesstimeout" in context file match

s_oc4j_sesstimeout  >> In Minutes
s_sesstimeout /1000*60 >>> Autoconfig uses this to populate ICX_SEESION_TIMEOUT value
soset the time out to 60 mins:
Update context file on all MT's:
s_oc4j_sesstimeout to 60
s_sesstimeout  to 3600000

How AutoConfig sets profile option 'ICX: Session Timeout' (Doc ID 307149.1)

The 'ICX:Session Timeout' profile option indicates when an Application's session expires after inactivity.
- zone.properties is not used in Release 12.
- A second context file parameter, s_oc4j_sesstimeout, specifies when an HTTP session in the container expires due to inactivity

R12.0 / R12.1 : Oracle EBS Context Variables (Doc ID 458282.1)

OC4J Session Timeout

s_oc4j_sesstimeout

Defines OC4J's servlet session timeout in minutes. It is specified in orion-web.xml of all the web modules deployed under each OC4J instances. A negative value indicates no timeout. A value of 0 results in an immediate timeout. Default value is 30 minutes. The value for the OC4J session timeout should be equivalent to or higher than the Applications session timeout (s_sesstimeout). For more details, please refer

Oracle HTTP Server Timeout

s_ohstimeout

This parameter stands for the amount of time (in seconds) the Oracle HTTP Server will wait for certain events(GET,POST,PUT etc) before failing a request