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

Agent cannot find its Access Groups

SA-8333

Summary



Pega HTTP service is returning a 500 error because of an exception in the logs with regard to an access group not found.


Error Messages



Error seen in Pega logs:

2013-06-19 11:51:24,147 [fault (self-tuning)'] [ STANDARD] [ ] ( pegarules.services.ServiceAPI) WARN AAAA - Current Requestor with ID:AD390627EFF27DB87ED1FA77602F16C16 in the pool for service package XXXX Couldn't find Rule-Service-HTTP instance YYYY using access group ZZZZ

2013-06-19 11:51:24,147 [fault (self-tuning)'] [ STANDARD] [ ] ( pegarules.services.ServiceAPI) WARN AAAA - Requestor with ID:AD390627EFF27DB87ED1FA77602F16C16 in the pool for service package XXXX has a default access group: PegaRULES:Unauthenticated that does not match service package access group ZZZZ

2013-06-19 11:51:24,147 [fault (self-tuning)'] [ STANDARD] [ ] ( pegarules.services.ServiceAPI) ERROR AAAA - Failed to get service rule instance:
com.pega.pegarules.pub.PRException: Couldn't find Rule-Service-HTTP instance YYYY using access group ZZZZ
From: (AD390627EFF27DB87ED1FA77602F16C16)
at com.pega.pegarules.services.ServiceAPI.getServiceInstance(ServiceAPI.java:2445)
at com.pega.pegarules.services.ServiceAPI.getServiceMethodInner(ServiceAPI.java:2162)
at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.pega.pegarules.engine.context.PREnvironment.doWithRequestorLocked(PREnvironment.java:909)
at com.pega.pegarules.engine.context.PREnvironment.doWithRequestorLocked(PREnvironment.java:674)
at com.pega.pegarules.services.ServiceAPI.getServiceMethod(ServiceAPI.java:2137)
at com.pega.pegarules.services.ServiceAPI.preLockSetup(ServiceAPI.java:713)
at com.pega.pegarules.services.EngineAPI.processRequest(EngineAPI.java:257)
at com.pega.pegarules.services.http.HTTPService.invoke(HTTPService.java:247)
at com.pega.pegarules.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:270)
at com.pega.pegarules.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:223)
at com.pega.pegarules.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:204)
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngineInner(JNDIEnvironment.java:274)
at com.pega.pegarules.priv.context.JNDIEnvironment.invokeEngine(JNDIEnvironment.java:219)
at com.pega.pegarules.web.impl.WebStandardImpl.makeEtierRequest(WebStandardImpl.java:307)
at com.pega.pegarules.web.impl.WebStandardImpl.doPost(WebStandardImpl.java:201)
at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
<etc>


Steps to Reproduce



This error is seen as a side effect of a passivation issue.

Root Cause



The root cause of this problem is a defect in Pegasystems’ code or rules.
If passivation failes and PRPC recreates service requestor, it incorrectly creates them with a default access group ( PegaRULES:Unauthenticated),  rather than the service package access group.


Resolution



This issue is resolved by hotfix item Hfix-2400.

Published January 31, 2016 - Updated 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