Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Discoverer - Version 10.1.2.1 to 10.1.2.3 [Release 10.1.2]
Information in this document applies to any platform.
Checked for relevance on 15- Jan-2016
Discoverer 10g (10.1.2) server sessions (dis51ws) are not terminating even with timeout limits are reached.
Symptoms that users may encounter are:
- The maximum process limit may be reached and users are not allowed to login. They may be presented with the message:
"Attempt 1. CORBA protocol: Hard limit on number of sessions reached.
Please contact your administrator or retry after some time"
Attempt 1. CORBA proto : 0 of 1 processes started. Hint: An administrator
can further diagnose connection problems by running the "checkdiscoverer"
script under /discoverer/util
Symptoms that Discoverer Administrators or System Administrators may encounter are:
- Discoverer Portlets may not refresh correctly due to the existing hanging sessions. You may see Infrastructure database connections to the discoverer5.PTM_XXXX tables.
- System CPU and Memory may be utilized or not released.
Discoverer Plus session timeout is changed in the pref.txt file as described in section '10.6.2 About setting the timeout value for Discoverer' of the Oracle� Business Intelligence Discoverer Configuration Guide 10g Release 2 (10.1.2.1).
Discoverer Viewer session timeout is changed in the OC4J_BI_Forms web.xml file as described in section '10.6.3 How to set the timeout value for Discoverer Viewer' of the Oracle� Business Intelligence Discoverer Configuration Guide 10g Release 2 (10.1.2.1).
Reducing the Discoverer sessions timeout does not seem help. Educating user to exit the application via the 'exit' link for Viewer instead of using the browser 'X' button does seem to help the issue in some case.
This issue mainly affects the Discoverer PortletProvider and Discoverer Viewer.
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