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

Connection is closed on running extract rules



While running multiple extract rules through agents, connection is closed for the extract rules with large number of records. This occurs if the extract rules are run manually through Designer Studio.

Error Messages

802 [ PegaRULES-Batch-4] [  ] [ UM:] ( internal.access.ExtractImpl)INF - #Instances Retrieved till this batch: 45690 -- 64.76% Complete - Last Id Processed in this Batch Execution: ANTM-CARE-UM-WORK-SR A-6465236
855 [ PegaRULES-Batch-4] [  ] [UM:] (internal.access.ExtractImpl)ERROR - SQL error getting the next row to be extracted
855 [ PegaRULES-Batch-4] [  ] [UM:] (internal.access.ExtractImpl)ERROR - SQL error while reading the blob: errorCode = 0 errorMessage:The connection is closed.

Steps to Reproduce

Run the multiple extract rules through an agent.

Root Cause

All the exceptions occur at ~300 seconds. In the data base connection pool setting, removeAbandoned= True and removeAbandonedTimeout= 300.


Make the following change to the operating environment:
  1. Set removeAbandonedTimeout= 600
  2. Set removeAbandoned= False

Published 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