My Oracle Support Banner

How to set the WebGate's Maximum Client Session Time to Accept Minutes (Doc ID 871926.1)

Last updated on MARCH 18, 2019

Applies to:

COREid Access - Version 10.1.4.2 and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Goal

Some firewalls forcefully disconnect Access Server connections over a certain age or idle time, which causes a resource leak in the Access Server. If you are affected by this issue, but unable to modify firewall time-out settings,
you can use maxSessionTimeUnits to remedy the problem. The effect of lowering Maximum Client Session Time does increase the frequency with which access clients close and re-open connections to the Access Server, which increases
network traffic. Therefore, the maxSessionTimeUnits value should be as high as possible within the limits of the firewall settings.

Note that the MaxSessionTime field still reads "(hours)", however, the presense of the maxSessionTimeUnits parameter causes the Maximum Client Session Time (hours) to be interpreted in minutes.

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.