Set Up JDBC Connection Pool In WebLogic To Properly Handle Database Restarts
(Doc ID 1062543.1)
Last updated on DECEMBER 05, 2019
Applies to:Oracle Communications Order and Service Management - Version 6.2.0 to 7.2.4 [Release 6.2.0 to 7.2]
Information in this document applies to any platform.
***Checked for relevance on 04-Mar-2013***
***Checked for relevance on 07-Oct-2014***
***Checked for relevance on 08-Mar-2016***
***Checked for relevance on 11-Jan-2019***
Quite often, the WebLogic JDBC connection pools are not setup correctly and the database of these JDBC connection pools is re-started for various business reasons. This will cause applications hosted in WebLogic to become unavailable and huge log files created with endless errors due to invalid JDBC connections. The following is such an example:
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
|Questions and Answers|
|What can be done to avoid disconnects on DB restarts?|