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

Connect_REST-Run_IN_Parallel issue

SA-47088


Summary



When trying to use Run_In_Parallel with two Connect_REST in an activity, user gets error message, when is executed same Connect-REST rules as synchronous call, then it works.


Error Messages



2017-10-10 17:18:35,028 [v2_svpprc,maxpri=10]] [ STANDARD] [ PegaSample:01.01] (nvoke.Rule_Connect_REST.Action) ERROR User1 - com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
com.pega.pegarules.pub.services.ConnectorException: Caught unhandled exception: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_410497452ae304b355cff4d17daace5e.step5_circum0(ra_action_pyinvokerestconnector_410497452ae304b355cff4d17daace5e.java:1407)
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_410497452ae304b355cff4d17daace5e.perform(ra_action_pyinvokerestconnector_410497452ae304b355cff4d17daace5e.java:140)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3020)
at com.pegarules.generated.activity.ra_action_invoke_db6a6695924a86e67ba1b3b2707ed8cc.step7_circum0(ra_action_invoke_db6a6695924a86e67ba1b3b2707ed8cc.java:1051)
at com.pegarules.generated.activity.ra_action_invoke_db6a6695924a86e67ba1b3b2707ed8cc.perform(ra_action_invoke_db6a6695924a86e67ba1b3b2707ed8cc.java:175)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3020)
at com.pegarules.generated.activity.ra_action_childinvoke_d9147708819cca9d197101bb02c3066f.step4_circum0(ra_action_childinvoke_d9147708819cca9d197101bb02c3066f.java:447)
at com.pegarules.generated.activity.ra_action_childinvoke_d9147708819cca9d197101bb02c3066f.perform(ra_action_childinvoke_d9147708819cca9d197101bb02c3066f.java:129)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3020)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:617)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(ThreadRunner.java:545)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(PRThreadImpl.java:581)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(QueueProcessor.java:253)
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(QueueProcessor.java:316)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:837)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1079)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:814)
at com.pega.pegarules.session.internal.async.BatchRequestorTask.run(BatchRequestorTask.java:586)
at com.pega.pegarules.session.internal.async.Agent.runBatchTask(Agent.java:706)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(AsyncServant.java:193)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.invoke(AsyncServant.java:148)
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)
at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:349)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:390)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingException(PRBootstrap.java:412)
at com.pega.pegarules.internal.etier.ejb.EngineBeanBoot.invokeEngine(EngineBeanBoot.java:168)
at com.pega.pegarules.internal.etier.interfaces.EJSLocalStatelessEngineBMT_f2439d86.invokeEngine(Unknown Source)
at com.pega.pegarules.session.internal.engineinterface.etier.mdb.PRAsync.processRequest(PRAsync.java:151)
at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.AsyncTask.run(AsyncTask.java:60)
at com.pega.pegarules.session.internal.engineinterface.etier.asynchbeans.RunnableWrapper.run(RunnableWrapper.java:67)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:270)
at java.security.AccessController.doPrivileged(AccessController.java:384)
at javax.security.auth.Subject.doAs(Subject.java:495)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:131)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:89)
at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:337)
at java.security.AccessController.doPrivileged(AccessController.java:413)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:779)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:222)
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:159)
at java.lang.Thread.run(Thread.java:767)
Caused by:
java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
at com.pegarules.generated.activity.ra_action_pyinvokerestconnector_410497452ae304b355cff4d17daace5e.step5_circum0(ra_action_pyinvokerestconnector_410497452ae304b355cff4d17daace5e.java:871)
... 45 more


Steps to Reproduce



1. Make both services use Run_In_Parallel and use a connect_wait step.
2. On invoking the service, there is a service issue.


Root Cause



A defect in Pegasystems’ code or rules

Resolution



Perform the following local-change:

Create following 'Property-Set' step before the 'Connect-Rest' step. Properties Value should match the type of REST method(GET, POST, and so on).





Also it is recommended to refer all the values within the connect-rest outbound mapping with respect to Connect-Rest step page.
Suggest Edit

Published March 28, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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