In Weblogic Server Console ODI_server1 JDBC Data Source Connection Pool Status Changes to "Overloaded" Causing ODI Console to Hang in ODI 12.2.1
Last updated on JANUARY 11, 2017
Applies to:Oracle Data Integrator - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
When logging in with ANY user that does not have the supervisor privilege the weblogic JDBC Connection pool produces a lot of sessions which in turn produce a JDBC Overload error and then the ODI Console freezes.
There are too many sessions generated for non supervisor user as compared to supervisor user. The number of sessions increase by 4-5 with each user login, while with a supervisor user, number of sessions increase by 1.
This can be seen from WebLogic Server console:
Weblogic Server console -> odi_domain -> Servers -> ODI_Server1 -> Monitoring -> Health
In Weblogic Server console -> odi_domain -> Servers -> ODI_Server1 -> Monitoring -> JDBC
By default in Weblogic Server console -> odi_domain -> Services -> Data Sources -> odiMasterRepository -> Connection Pool -> Maximum Capacity = 15
By increasing this number this issue may pass unnoticed. And by restarting the managed server odi_server1 the sessions are cleared.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms