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

Agents fail and does not restart normally

SA-15955

Summary



The PegaRULES logfile shows IllegalStateExceptions and a variety of Websphere datasource connection errors. Agents in the environment are failing and are not restarting normally in Pega 7.1.8. 


Error Messages



2015-10-02 23:12:47,689 [WorkManager : 1529] [  STANDARD] [                    ] (ernal.async.BatchRequestorTask) ERROR   - Batch activity "PegaAESRemote-.PushLogUsageData" threw:
java.lang.IllegalStateException: Internal state is compromised; cannot write out application hierarchy and/or rulesets
                at com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.populateApplicationRuleHierarchy(GlobalContextCache.java:1776)

Caused by:
com.ibm.websphere.ce.cm.ObjectClosedException: DSRA9110E: Connection is closed.
                at com.ibm.ws.rsadapter.jdbc.WSJdbcWrapper.createClosedException(WSJdbcWrapper.java:110)


2015-10-02 23:12:46,051 [WorkManager : 1462] [  STANDARD] [     Your_App:04.02.01] (  internal.access.DatabaseImpl) ERROR   - There was a problem with the database when getting a list:
com.pega.pegarules.pub.database.ConnectionException: Database-General     Problem encountered when getting connection for database pegadata           0              08S01    Connection reset
From: (B750FD75E0614C8EB460656FBD203A733)
Caused by SQL Problems.
Problem #1, SQLState 08S01, Error code 0: com.ibm.websphere.ce.cm.StaleConnectionException: Connection reset
Problem #2, SQLState 08S01, Error code 0: com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset
 


Steps to Reproduce



Not Applicable.


Root Cause



A defect or configuration issue in the operating environment. The database is taken offline for backup without stopping the application server. This led to failed datasource connections, and agent failures.

Resolution



Make the following change to the operating environment:

​Update the datasource to add connection pre-testing and failing connection clean-up. This will further safeguard against any temporary database outages. 

 

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% 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