APEX Session Management
I am working on a client site that has an implementation of APEX 2.2.1. While attempting to set up a session trace, we discovered that only active sessions from APEX show up in v$session. Additionally when the session is inactive and becomes active again it shows up in v$session with a different sid.
We suspect that this is the reason the customer has had issues with the listener.log file growing out of control. Also it would seem that all of this connecting/disconnecting would generate a lot of overhead for no reason.
My question is, are there parameters within the http.conf or the dad.conf or anywhere else that need to be changed to allow a session to keep the same sid or at least reuse a persistant connection?
Thanks