Question

7
Replies
7236
Views
Jarrod Bezzina (Jarrod)
PEGA
Consulting Manager, Pega Consulting
Pegasystems Inc.
NL
Jarrod Member since 2012 13 posts
PEGA
Posted: February 29, 2016
Last activity: June 9, 2016
Posted: 29 Feb 2016 8:51 EST
Last activity: 9 Jun 2016 6:33 EDT
Closed

Not returning connection X for database "pegadata" to the pool as it previously encountered the following error

I've been monitoring AES for a number of nodes in a cluster and found that we have a large number of Database connections open (in some cases >2000).  After investigation it was found that these were not active connections but the total number of forced closed plus currently active connections (WAS has a policy enabled that will release an idle connection after 2 hours).  The question still remains, why doesn't pega release the connection.  An extensive analysis of the logs found a number of entries stating:

Not returning connection X for database "pegadata" to the pool as it previously encountered the following error.  It was also found that the error in occur also for the pegarules database.

When the database encounters an exception, shouldn't Pega always return the connection back to the pool rather than keep it open, considering (if WAS wasn't configured to force close the connection) the total resources required by Pega to keep the connection open?

We also see an ORA-01000: Maximum number of open cursors exceeded.  I presume this error is due to the force close of the connection without closing the cursor?

Data Integration System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.