Support Article

Database connection close is not happenning

SA-31667

Summary



When user connects to an external DB, the session that is created at DB is not getting closed by Pega.

Only the sessions become inactive sometimes and sometimes the session is active more than three hours.


Error Messages



Not applicable

Steps to Reproduce



Hit the external DB and see the session that is created is not getting closed by Pega and the session or connection still remains the same.

Root Cause



A defect or configuration issue in the operating environment.

The external DB instance which user configured as with JDBC URL as connection type which is leading user to a performance issue as there is no connection pool each time user connects to DB the connection object is never deleted until the session get deleted by DB server.

Resolution



For better performance user must connect to connection pool by using JNDI or 'use with preferences' option to connect to DB.
 

 

Published December 20, 2016 - Updated January 2, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.