With our 12c migration in final live testing we have started to develop an issue that we are not sure now to resolve. It seems that for whatever reason, if I client does not terminate the local java session of forms on the client the FRMWEB.EXE on the server does not also terminate leaving ghosted server processes as well as active DB connections.
We have a workflow that limits the number of active DB connections by user to forms sessions. This is checked after the client connects to the DB by checking “V$SESSION” for the username running forms. If that count exceeds a threshold their forms session exists programatically. However is the client session does not terminate normally it leaves the sessions active and when clients connect using a new session it quickly exceeds the threshold.
What is the proper method to detect and terminate these ghosted FRMWEB.EXE sessions? I have read about FORMS_TIMEOUT but that also requires I believe the heartbeat configuration parameter, but that is confusing in the way these 2 relate. Any suggestions?