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

RDB-List Call failing



The users notice an error in the Pega Platform logs when they call an RDB-List through an activity.

Error Messages

2017-03-06 19:02:59,065 [ PegaRULES-Batch-7] [ STANDARD] [ ] [Ruleset:Version] ( internal.mgmt.Executable) ERROR - Exception caught exception during autocommit check
at com.pegarules.generated.activity.ra_action_activityname_f234b4c8dc8c8e8170e591e41f0e13e8.step1_circum0(
at com.pegarules.generated.activity.ra_action_activityname_f234b4c8dc8c8e8170e591e41f0e13e8.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.runActivity(
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
Caused by: DSRA9110E: Connection is closed.

Steps to Reproduce

  1. Advanced agent queues to standard agent
  2. Standard agent runs RDB-List in 1st step and retrieve records
  3. RDB-List is failing and not getting processed.

Root Cause

A defect or configuration issue in the application server : Pega is using a *closed* JDBC connection, which causes the action to fail.


Perform the following local-change: Following change to Web Sphere Application Server(WAS) based upon the version is required, which makes WAS check if a connection is usable before assigning it from the connection pool.
In the administrative console, click Resources > JDBC providers.
  1. Select a provider and click Data Sources under Additional properties.
  2. Select a data source and click Web Sphere Application Server data source properties under Additional properties.
  3. Select the PreTest Connections check box.
  4. Type a value for the PreTest Connection Retry Interval, which is measured in seconds. This property determines the frequency with which a new connection request is made after a pretest operation fails.
  5. Type a valid SQL statement for the PreTest SQL String. Use a reliable SQL command, with minimal performance impact; this statement is processed each time a connection is obtained from the free pool.
This worked for WAS 8.

For further details check IBM's support site at

Suggest Edit

Published March 26, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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