How to setup "timeout" for clients (jas.ini,jde.ini,jdbj.ini,web.xml,OAS)

How to setup \"timeout\" for clients (jas.ini,jde.ini,jdbj.ini,web.xml,OAS)

Hi,
we are running on 8.96F1, Application server on a MS Cluster, database on SQL 2005 (64bit) and OAS 10g (WAS/JAS). We have had some problems with stability (not performance) and additionally it looks like our "timeout" setup is a nightmare. Our "consultants" are not interested in helping us anymore, so maybe I can get some explanations via this forum. We would like to have a timeout of 2 hours for our clients (Production - as always). I know that there are some timeout parameters in the jde.ini, in the jas.ini, in the jdbj.ini. Additionally the OAS (so Apache Tomcat I think) is coming with a httpd.conf where you can also setup a timeout for user sessions. And from Oracle you get the information to change a web.xml. For Websphere you can read that the jas.ini and the http server should get a higher value than the "Websphere" ... but what about this kind of things while using an OAS (WAS/JAS)? Is there anybody on this planet able to explain me what we should do to get those 2 hours for timeout without creating locks on the database or crashing JDE?
Please ... thanks

Re: How to setup \"timeout\" for clients (jas.ini,jde.ini,jdbj.ini,web.xml,OAS)

This might help you.

PROBLEM:
How to set Inactive Timeout Settings for JAS to determine the length of inactivity for a JAS client before the connection is dropped by the JAS server.

RESOLUTION:
The following settings define the amount of time a JAS client can be inactive before the connection will be cleaned up. In addition to the documented changes to the JAS.INI, modifications to the WebSphere configuration is required. In some cases, the web server timeout may need to be adjusted for latency issues.

Note:
The JAS.INI setting(s) and HTTP Server settings for timeout should be set a greater value than the timeout setting in WebSphere Application Server. The ultimate goal is to have WebSphere Application Server time the session out to avoid record locking. Example: WebSphere timeout setting for 1 hour session, JAS.ini and HTTP server timeout set for 1.5 hours.

JAS.INI:
Under the [CACHE] section of the JAS.INI file, modify the UserSession setting. The UserSession value is read in all Service Pack levels, and needs to be adjusted for the timeout.

[CACHE]
# These intervals are in milliseconds. For example, 60000ms = 1 minute, 3600000ms= 1 hour
UserSession=5400000 <====


WEBSPHERE CONFIGURATION FOR WAS V5.0.2.X AND WAS 6.0.2.X (Two settings, one in Application Server and one in Enterprise Application):
Follow this path: Servers > Application Servers > AS_JS_port_MachineName> Web Container > Session Management
Select the "set Session timeout" radio button and fill in the minutes field (for this example, set the value to 60 minutes).
Set this value to be, at most, half the time specified in the JAS.INI for the "UserSession" value.
Click the "Apply" button on the Session Management Configuration screen.
Click the "Save" link that appears at the top of the screen.
Click the "Save" button that appears to update the Master Configuration.

Folow this path for Enterprise Application: Applications > Enterprise Applications > EA_JS_port_MachineName > Session Management
Select the "set Session timeout" radio button and fill in the minutes field (for this example, set the value to 60 minutes).
Set this value to be, at most, half the time specified in the JAS.INI for the "UserSession" value.
Click the "Apply" button on the Session Management Configuration screen.
Click the "Save" link that appears at the top of the screen.
Click the "Save" button that appears to update the Master Configuration.

Stop and restart the Application Server

MICROSOFT INTERNET INFORMATION SERVICES (IIS):
Highlight the web site that has been configured for the JAS web instance (usually "Default Web Site" or "OneWorld").
Either right click on the web site and go to properties, or go to the "Action" menu and choose properties.
On the "Web Site" tab locate "Connection Timeout".
Set this value to the same time limit that the "UserSession" setting in the [CACHE] section in the jas.ini was set to. ***Keep in mind that the timeout for IIS is measured in seconds rather than milliseconds (for this example, set the value to 5,400).
Click OK.
Stop and restart the modified Web Site.

IBM HTTP SERVER
In the httpd.conf file, adjust the timeout setting.
Set this value to the same time limit that the "UserSession" setting in the jas.ini was set to. ***Keep in mind that the timeout for IBM HTTP server is measured in seconds rather than milliseconds (for this example, set the value to 5,400). After the change is made to the file, save the httpd.conf file
Stop and restart the HTTP services for the change to take affect.

example of httpd.conf file:
# Timeout: The number of seconds before receives and sends time out
Timeout 5400

Re: How to setup \"timeout\" for clients (jas.ini,jde.ini,jdbj.ini,web.xml,OAS)

Here's another one for OAS. I checked no problem.
Summary:
E1: OAS: How to set session timeout value in Oracle application server jas insta
Details: ISSUE:
Customer is running a JAS server using OAS and needs to find out how to set the time out settings. From an HTML client, the system times out within 15 minutes.

SOLUTION:
Session timeout. This is by default set to 20 minutes. To set higher timeout, please follow the steps as described here.
1. Navigate to JAS Application under <ORACLE_HOME>/j2ee/<oc4j>/applications/jasapp/webclient/WEB-INF
2. Make sure that server is not running.
3. Edit the web.xml file with notepad.
4. Place the 3-line session-timeout stanza in the web.xml file like this:
...
<servlet>
<servlet-name>MOViewerServlet</servlet-name>
<display-name>MOViewerServlet</display-name>
<servlet-class>com.peoplesoft.e1.container.MafletServiceContainer</servlet-class>
<init-param>
<param-name>maflet.name</param-name>
<param-value>MOViewerServlet</param-value>
</init-param>
</servlet>

<session-config>
<session-timeout>40</session-timeout>
</session-config>
Where the number is the session timeout in minutes.

Please note that this is a crucial timeout value, setting it higher than 30 minutes may cause higher memory usage and out of memory conditions. Please take care in using this setting

Note:
The JAS.INI setting(s) and HTTP Server settings for timeout should be set a greater value than the timeout setting in Oracle Application Server. The ultimate goal is to have Oracle Application Server time the session out to avoid record locking. Example: OAS timeout setting for 1 hour session, JAS.ini and HTTP server timeout set for 1.5 hours.

JAS.INI:
Under the [CACHE] section of the JAS.INI file, modify the UserSession setting. The UserSession value is read in all Service Pack levels, and needs to be adjusted for the timeout.

[CACHE]
# These intervals are in milliseconds. For example, 60000ms = 1 minute, 3600000ms= 1 hour
UserSession=5400000 <====

HTTP SERVER
In the httpd.conf file, adjust the timeout setting.
Set this value to the same time limit that the "UserSession" setting in the jas.ini was set to. ***Keep in mind that the timeout for IBM HTTP server is measured in seconds rather than milliseconds (for this example, set the value to 5,400). After the change is made to the file, save the httpd.conf file
Stop and restart the HTTP services for the change to take affect.

example of httpd.conf file:
# Timeout: The number of seconds before receives and sends time out
Timeout 5400