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

InvalidParameterException for APP Requestors

SA-80566

Summary



Recurrent InvalidParameterException exceptions are generated in the logs for application requestors.


Error Messages



com.pega.pegarules.pub.clipboard.InvalidParameterException: Invalid value for Requestor parameter: APPRWR39IL7CFH3JPNGX9S0TY20MQ7N5R 
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doUnsafeAccessToUnlockedRequestor(PRSessionProviderImpl.java:549) 
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doUnsafeAccessToUnlockedRequestor(PRSessionProviderImpl.java:510)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doUnsafeAccessToUnlockedRequestor(PRSessionProviderImpl.java:2131) 
at com.pega.pegarules.monitor.internal.context.ManagementDaemonImpl.checkRequestors(ManagementDaemonImpl.java:356) 
at com.pega.pegarules.monitor.internal.context.ManagementDaemonImpl.performManangementActions(ManagementDaemonImpl.java:287) 
at sun.reflect.GeneratedMethodAccessor82.invoke(Unknown Source) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:498) 
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1297) 
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1034) 
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:856) 
at com.pega.pegarules.session.external.async.AbstractDaemon.performProcessing(AbstractDaemon.java:317) at com.pega.pegarules.session.external.async.AbstractDaemon.run(AbstractDaemon.java:262) 
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(AsyncServant.java:253) 
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.invoke(AsyncServant.java:168) at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:331)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.invokeEngine(EngineImpl.java:274) 
at com.pega.pegarules.session.internal.engineinterface.etier.ejb.EngineBean.invokeEngine(EngineBean.java:225) 
at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:498) 
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411) 
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224) 
at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingException(AppServerBridgeToPega.java:246) 
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBeanBoot.java:168)...



Steps to Reproduce



Not Applicable


Root Cause



A defect in Pegasystems’ code or rules.
The exception was raised by the ManagementDaemon when existing requestors were retrieved and inspected to determine if a PEGA0019 alert occurred in case of long running requestors.
For short living requestors the check failed because the application requestor was removed.



Resolution



Apply HFix-53325.

Published August 15, 2019 - 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