Last updated on JUNE 15, 2017
Applies to:Oracle Knowledge - Version 8.5.1 and later
Information in this document applies to any platform.
It is fairly common for custom codes (like custom iAuth, custom UI helper classes to import/report/list/display IM info or even to run IM batch jobs, ...) to use/share the OOTB internal IMDB connection pool. So potentially those custom code may introduce IMDB connection leaks in the OOTB internal IMDB connection pool that will lead to unexpected IM instances (IM Console, Infocenter, IMWS) hung due to IMDB connection pool exhaustion. This document provides some helpful parameters to debug/avoid IM instances (IM Console, Infocenter, IMWS) hung due to IMDB connection pool exhaustion.
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