Troubleshooting Spinning/Rogue frmweb Processes Consuming 100% of CPU in 11gR2 or 12c Forms
(Doc ID 2386477.1)
Last updated on MAY 08, 2020
Applies to:Oracle Forms - Version 6.0.8 and later
Information in this document applies to any platform.
Spinning/rogue frmweb processes can have a serious impact on system performance since they can consume all CPU resources.
An frmweb process is associated with a user client session and should usually terminates immediately once a user closes their session. Depending upon what the user session was doing there may be some cleanup required when a session is closed so the frmweb may exist a few moments longer after session closure. If the frmweb session does not terminate within 15 minutes of the closed session, an internal mechanism should terminate it.
For various reasons - a product defect, unexpected session abort, application coding, operating system problem, etc. - an frmweb session disassociated from a user session may start "spinning" and eventually consume all of a system's CPU resources.
This note describes ways to prevent this as well as diagnose the cause of the issue.
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