OBDX Managed Server Health in Warning With the Exceptions - weblogic.jdbc.extensions.ConnectionDeadSQLException & weblogic.common.resourcepool.ResourceDeadException
(Doc ID 2717828.1)
Last updated on JUNE 06, 2024
Applies to:
Oracle Banking Digital Experience - Version 18.1.0.0.0 to 18.1.0.0.0 [Release 18]Information in this document applies to any platform.
Symptoms
OBDX (Oracle Banking Digital Experience) managed Servers was observed to be going into Warning State since last couple of days with restart being taken to resolve the Issue,
The following errors observed on Logs.
Weblogic Version - 12.2.1.2.0
ERROR
-----------------------
In Application Logs -->
Caused by: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection for datasource 'DIGX'. The DBMS driver exception was: IO Error: Got minus one from a read call
Caused by: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection for datasource 'DIGX'. The DBMS driver exception was: IO Error: Broken pipe (Write failed)
In Database Alert Logs -->
WARNING: inbound connection timed out (ORA-3136)
ORA-609: opiodr aborting process unknown ospid
STEPS
-----------------------
There are no steps as such. The Weblogic Health was observed as Warning during continuous monitoring
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users are facing issues in doing their day to day transactions.
Changes
Change in Datasource Connection Parameters during switching from DR to Production could have caused this.
Apart from that some Database errors due to Database OS and Log File sync activity was causing Connection related Issues.
Cause
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
Symptoms |
Changes |
Cause |
Solution |