Last updated on SEPTEMBER 21, 2016
Applies to:COREid Access - Version: 10.1.4.2
Information in this document applies to any platform.
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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms