Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

PRPC fails to start with "Connection has already been closed"



Using Tomcat 7, when trying to start the PRPC application, the server startup fails.

Error Messages

java.sql.SQLException: Connection has already been closed.
at org.apache.tomcat.jdbc.pool.ProxyConnection.invoke( 

Steps to Reproduce

Not applicable

Root Cause

The root cause of this problem is the database performance issue causing the tomcat connection pool abandons certain seemingly idle connections.


Address the database performance with tje DBA (in this case recycling the database server) and adjust the 
removeAbandonedTimeout value in the PegaRULES datasource definition to a higher value (e.g., from the current 300 seconds to 600 seconds).

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us