OTA Player Spawning Many Idle Sessions Through An F5 Load Balancer
(Doc ID 2175290.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Learning Management - Version 12.1 HRMS RUP5 and later
Information in this document applies to any platform.
On : 12.1 HRMS RUP5 version, Content Admin
OTA Player spawning many idle sessions
Customer is seeing constant growth in the number of sessions attributable to the ota.player.server.PlayerAM module.
The number of sessions seems to grown until it exhausts the number of available session in the database.
It seems as though once a session is started it does not let go of the session and the only way to do so is to bounce the web server and oc4j oacore processes.
Manually killing the sessions in the database does not seem to relieve them either.
Customer has four self service nodes, each one has 6 oacore processes. Customers database has 4200 as the sessions parameter.
The issue can be reproduced at will with the following steps:
Customer is seeing that each OC4J oacore has a single process. And that each process has close to 100 sessions...and that the number of sessions per oacore it growing for no apparent reason....
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