Problems encountered when setting the access group for the queue activity
Agents are failing and getting below error message in logs, this is happening for all agents enabled in the application. Agent status showing as successful in the dev portal, but agent activity is not executed and observed exceptions in the logs with below message.
"Problems encountered when setting the access group for the queue activity".
Agents are failing and getting below error message in logs, this is happening for all agents enabled in the application. Agent status showing as successful in the dev portal, but agent activity is not executed and observed exceptions in the logs with below message.
"Problems encountered when setting the access group for the queue activity".
"2018-07-31 03:46:16,320 [ PegaRULES-Batch-39] [ STANDARD] [ ] [ PegaRULES:07.10] ( internal.async.AgentQueue) ERROR - Agent COMFW #1: ABCD-FW-COMFW-Data.SaveData encountered an execution error. Restarting after delay.\ncom.pega.pegarules.pub.context.PRSecurityException: Problems encountered when setting the access group for the queue activity\n\tat com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:963) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1357) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1105) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:986) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:763) ~[prprivate.jar:?]\n\tat com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:991) ~[prjsr166java6-3.0.jar:?]\n\tat com.pega.jsr166backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:532) ~[prjsr166java6-3.0.jar:?]\n\tat java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]\nCaused by: java.lang.NullPointerException\n\tat com.pega.pegarules.session.internal.authorization.context.ContextUtils.calculateRoleHashUsingRuleSets(ContextUtils.java:1036) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.context.BasicApplicationContextImmutableImpl.initializeBaseOnDefinition(BasicApplicationContextImmutableImpl.java:446) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.context.BasicApplicationContextImmutableImpl.<init>(BasicApplicationContextImmutableImpl.java:166) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.context.ApplicationContextFactory.createBasicApplicationContext(ApplicationContextFactory.java:74) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getBasicApplicationContext(GlobalContextCache.java:420) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.context.GlobalContextCache.getLocalizedApplicationContext(GlobalContextCache.java:441) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.context.AuthorizationContextManagerImpl.getContext(AuthorizationContextManagerImpl.java:102) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(SessionAuthorization.java:488) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.SessionAuthorization.getContext(SessionAuthorization.java:432) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.SessionAuthorization.setAvailableAccessGroups(SessionAuthorization.java:526) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.Authorization.setAvailableAccessGroups(Authorization.java:607) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.Authorization.resetForAgent(Authorization.java:231) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:952) ~[prprivate.jar:?]\n\t... 7 more"
Cisco Systems
IN
Hi
what was the solution here..? I am facing same issue. Access group is present in application. Queue instances are still in scheduled state and not getting picked up. Getting the below error in logs
==
[STACK][com.pega.pegarules.pub.context.PRSecurityException: Problems encountered when setting the access group for the queue activity
Ernst & Young LLP
MT
Assuming it's a standard agent and NOT an advanced agent -
Go to the broken queue, open up any of those entries that agent failed to process, open up the xml of that entry, look for value of this property 'pyAccessGroup'.
This value will indicate the access group that your standard agent will use to setup authorization context for processing that particular queued entry.
Now, first check if that access group exists in that environment.
If it does exists, try to save that access group or use 're validate and save' utility to compile that access group, and see if PRPC returns any error.
Assuming it's a standard agent and NOT an advanced agent -
Go to the broken queue, open up any of those entries that agent failed to process, open up the xml of that entry, look for value of this property 'pyAccessGroup'.
This value will indicate the access group that your standard agent will use to setup authorization context for processing that particular queued entry.
Now, first check if that access group exists in that environment.
If it does exists, try to save that access group or use 're validate and save' utility to compile that access group, and see if PRPC returns any error.
Caused by: java.lang.NullPointerException\n\tat com.pega.pegarules.session.internal.authorization.context.ContextUtils.calculateRoleHashUsingRuleSets(ContextUtils.java:1036) ~[prprivate.jar:?]\n\tat com.pega.pegarules.session.internal.authorization.context.BasicApplicationContextImmutableImpl.initializeBaseOnDefinition(BasicApplicationContextImmutableImpl.java:446)
As per the following part of the exception log, PRPC somehow failed while loading up that access group.
Possibly that access group is possibly in mis-configured state in that environment.