Question
Optum
IN
Last activity: 7 Sep 2016 5:35 EDT
After upgrading from 6.1 SP2 to 7.1.9 none of the agents are working
Post upgrade none of the agents are working and our system is a single node environment. Tried to clear all the cache tables but nothing works.Followed the below process but nothing works. Can any one please suggest any better way if that's proved to be working.
- Stop the server,
- truncate below caching tables
Tables to be truncated are:
TRUNCATE TABLE PEGA_RULES.PR_SYS_CACHE_ENTRY;
TRUNCATE TABLE PEGA_RULES.PR_SYS_CACHE_DEP;
TRUNCATE TABLE PEGA_RULES.PR_SYS_APPCACHE_DEP;
TRUNCATE TABLE PEGA_RULES.PR_SYS_APPCACHE_SHORTCUT;
TRUNCATE TABLE PEGA_RULES.PR_SYS_APPCACHE_ENTRY;
TRUNCATE TABLE PEGA_RULES.PR_SYS_CACHE_IMPL;
TRUNCATE TABLE PEGA_RULES.PR_SYS_QUEUE_FTSINDEXER;
TRUNCATE TABLE PEGA_DATA.PR_SYS_QUEUE_FTSINDEXER;
TRUNCATE TABLE PEGA_RULES.PR_SYS_UPDATESCACHE;
TRUNCATE TABLE PEGA_RULES.PR4_RULE_SYSGEN;
TRUNCATE TABLE PEGA_RULES.PR_ASSEMBLEDCLASSES - remove extract marker file and clear all temp content and cache
- start the server.
Accepted Solution
Optum
IN
Below is the resolution and cause for this issue.
- Since PRPC specific ear files needs special handling when Jboss is concerned, the HornetQ needs to be enabled in Jboss as all batch processes (including all OOTB agents - APIs like queueBatchActivity - SOAP invoke with parallel mode etc) are handled by MDB PRAsync which uses the built-in HornetQ for topic communication. Following pdn article can be referenced for more information on this:
https://collaborate.pega.com/question/why-prpc-needs-hornetq-enabled-jboss-deployment - After enabling the HornetQ in Jboss server and deleting al the stale agent schedule instances from pr_Data, the agent schedule got created automatically and the issue was resolved in both dev and test environments.
Pegasystems Inc.
IN
From which version to which version you upgraded ?
Apart from the queries put forwarded by Rajesh and Nick, I would also like to understand what happens after manually enabling one of the stopped agent ? Is it running properly or getting stopped with exception ? You can follow this video and try tracing one of those agent to see what exactly is happening before they are getting stopped . https://collaborate.pega.com/discussion/video-support-guide-how-trace-agent-designer-studio
Accepted Solution
Optum
IN
Below is the resolution and cause for this issue.
- Since PRPC specific ear files needs special handling when Jboss is concerned, the HornetQ needs to be enabled in Jboss as all batch processes (including all OOTB agents - APIs like queueBatchActivity - SOAP invoke with parallel mode etc) are handled by MDB PRAsync which uses the built-in HornetQ for topic communication. Following pdn article can be referenced for more information on this:
https://collaborate.pega.com/question/why-prpc-needs-hornetq-enabled-jboss-deployment - After enabling the HornetQ in Jboss server and deleting al the stale agent schedule instances from pr_Data, the agent schedule got created automatically and the issue was resolved in both dev and test environments.