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



A stale connection error is generated repeatedly in the PegaRULES and Application server log file.

Error Messages

[7/27/15 16:14:06:762 EDT] 0000010a WSJdbcConnect W DSRA8650W: Error closing a JDBC child wrapper, Closed Statement
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
at java.lang.reflect.Constructor.newInstance(

Steps to Reproduce

Configure the connection pool in Websphere as described in the documentation for Oracle.

Root Cause

A third-party product issue. The problem should be resolved by specifying the appropriate information in the JDBC data source connection pool properties so that there are no stale connections given to Pega 7 to use.


Make the following change to the operating environment:

To correct the configuration, specify the following on the WebSphere Application Server data source properties.

  • Validate New Connections
  • Validate Existing Pooled connections
  • Validation by JDBC driver (Requires JDBC 4 driver)

Published September 3, 2015 - 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