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

System takes 40 minutes to start all agents incorrectly



After having upgraded from Pega 7.1.9 to Pega 7.2 the system is behaving incorrectly. The application server is a Weblogic version 11.
The issue is happening with existing agents, there is no error when stopping and starting manually the agent, but when it runs it is not running the second time.
There is nothing on broken queue either.

The PegaRULES logs are showing more than 30 minutes to start the agents:

2016-06-09 17:14:05,009 [ ] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) INFO - PegaRULES engine successfully started.
2016-06-09 17:47:26,372 [fault (self-tuning)'] [ STANDARD] [ ] [ ] ( internal.async.Agent) INFO - All startup agent finished, set node's run state to running!!!

Error Messages

Not applicable

Steps to Reproduce

  1. After restart, agents are not shown on the SMA, Pega agents and applications agents are not available = > list of agents is empty.
  2. 1h after the restart, the list is available but the Last run start and Last run finish dates are empty.
  3. After stop/start the agents run once, and they did not start on the Next run time.

Root Cause

The upgrade sequence has been verified and an incorrect EAR file was used. The MANIFEST was showing the following:

where it should be:

"Build-For: coreCode_72_264 "
Build-Date: 2016-02-03 18.44 EST
Build-Target: J2EE 1.3
Pega-Assembly-Date: 2016-02-03 18.44 EST


The new EAR file has been deployed to solve this issue
Suggest Edit

Published June 19, 2016 - 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