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

Failed to retrieve Rule-Service-HTTP due to Requestor

SA-17322

Summary



Failed to retrieve Rule-Service-HTTP due to Requestor. The HFix-10155 addressed the issue partially.

Error Messages


This is one of several exception in two service packages.

2015-10-23 15:49:28,085 [ WebContainer : 2] [ STANDARD] [ ] ( internal.services.ServiceAPI) ERROR server-name|ip-address|HTTP|CentralDecisionHub|Decisioning|RunStrategy - HTTP service [CentralDecisionHub][Decisioning][RunStrategy] failed:Service page lookup failed:com.pega.pegarules.pub.services.ServiceException: Service page lookup failed
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.preLockSetup(ServiceAPI.java:967)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequest(EngineAPI.java:326)
at com.pega.pegarules.integration.engine.internal.services.http.HTTPService.invoke(HTTPService.java:319)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:312)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:263)
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:221)
...
​Caused by: com.pega.pegarules.pub.PRException: Failed to retrieve Rule-Service-HTTP instance CentralDecisionHub.Decisioning.RunStrategy using access group CentralDecisionHub:Administrators
From: (A4AD430088F366433F3F0667793B1ABF9)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.getServiceInstance(ServiceAPI.java:2891)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.getServiceMethodInner(ServiceAPI.java:2593)
at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1090)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:798)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.getServiceMethod(ServiceAPI.java:2556)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.preLockSetup(ServiceAPI.java:959)
... 50 more


Steps to Reproduce



This happens intermittently in the production environments.


Root Cause



A defect in Pegasystems’ code or rules. HFix-10155 addresses the issue when requestor is returned to the pool after being "borrowed" before.  When it is retrieved again by a client calling "borrowRequestor", it is not re-initialized.

Resolution



Apply HFix-24927. This solution modifies the "borrowRequestor" method to insure any requestor "that is not new" gets re-initialized.

 

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