Starting Concurrently Many (say >20) WLS Managed Servers That Host IM/IC/IMWS instances May Result Some Fail With "DB Connection Not Valid Exception"
Last updated on AUGUST 16, 2016
Applies to:Oracle Knowledge - Version 8.6 and later
Information in this document applies to any platform.
When you have a large Prod IM env (say >20 instances of IM/IC/IMWS) distributed/deployed among >20 WLS Managed servers, you may start them all up concurrently via the WLS Admin Console UI in one shot. If you do so, you may find that some of them (say 2 or 3 randomly) may fail to startup with "DB Connection Not Valid Exception" error.
It is a known issue due to how IM instances's DB drivers handshake with the underneath Oracle IMDB to establish an DB connection that if many of them (say >20) are being initiated concurrently, a few of them (say 2-3) may got the error 500 returned with below message in the IM logfile:
[ProcessChangesQueue] 2016-05-16 10:18:40,144 ERROR com.inquira.services.application.AppStartUpCheck - Can't connect to database -- Database connection is not valid!
IO Error: Connection reset java.net.SocketException: Connection resetat oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:752)
This public KM article provide a couple simple workaround solutions for it.
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