Question
Cognizant
NL
Last activity: 8 Nov 2019 8:53 EST
Sub Strategy not getting called when called from Strategy after upgrate to 8.1.1
we have a strategy from which we are calling another strategy .the sub strategy is getting called on another page.We upgraded from 7.3.1 to 8.1.1 .Below is the log message.Any one faced similar issues?
com.pega.decision.strategy.api.exec.ComponentExecutionException: Strategy component: [XXYYYYYYModel_ModelV1_1Model].[Normalization TESTTDA] failed to execute. Details: null at com.pega.decision.strategy.impl.exec.SequenceComponentExecutor.execute(SequenceComponentExecutor.java:139) ~[strategy-8.1.1-247.jar:?] at com.pega.decision.strategy.impl.exec.StrategyExecutor.executeComponent(StrategyExecutor.java:135) ~[strategy-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.vm.PRPCNativeCallsImpl.executeLegacyComponent(PRPCNativeCallsImpl.java:119) ~[strategy-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAInterpreter.visit(SSAInterpreter.java:206) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAVisitor.visit(SSAVisitor.java:49) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAInterpreter.evaluateSSA(SSAInterpreter.java:766) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAInterpreter.visit(SSAInterpreter.java:329) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAVisitor.visit(SSAVisitor.java:77) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAInterpreter.evaluateSSA(SSAInterpreter.java:766) ~[decision-logic-compiler-8.1.1-247.jar:?]
we have a strategy from which we are calling another strategy .the sub strategy is getting called on another page.We upgraded from 7.3.1 to 8.1.1 .Below is the log message.Any one faced similar issues?
com.pega.decision.strategy.api.exec.ComponentExecutionException: Strategy component: [XXYYYYYYModel_ModelV1_1Model].[Normalization TESTTDA] failed to execute. Details: null at com.pega.decision.strategy.impl.exec.SequenceComponentExecutor.execute(SequenceComponentExecutor.java:139) ~[strategy-8.1.1-247.jar:?] at com.pega.decision.strategy.impl.exec.StrategyExecutor.executeComponent(StrategyExecutor.java:135) ~[strategy-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.vm.PRPCNativeCallsImpl.executeLegacyComponent(PRPCNativeCallsImpl.java:119) ~[strategy-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAInterpreter.visit(SSAInterpreter.java:206) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAVisitor.visit(SSAVisitor.java:49) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAInterpreter.evaluateSSA(SSAInterpreter.java:766) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAInterpreter.visit(SSAInterpreter.java:329) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAVisitor.visit(SSAVisitor.java:77) ~[decision-logic-compiler-8.1.1-247.jar:?] at com.pega.decision.strategy.ssa.SSAInterpreter.evaluateSSA(SSAInterpreter.java:766) ~[decision-logic-compiler-8.1.1-247.jar:?]
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
AU
Is it happening with all the strategies which have sub strategies or only selected?
Can you please attach the complete PegaRULES logs from that day and node?
Have you tried this with latest Pega patch release: https://collaborate.pega.com/discussion/pega-813-patch-release-available
HSBC
IN
Hi Ashutosh,
We are facing similar issue on 8.1.4, as we could see the nearly exact stack trace as in this post. Will the latest patch release 8.1.7 will help in fixing our issue?
Thanks,
Habeeb Baig
HSBC
IN
Was this issue resolved for you with the patch release? we are on 8.1.4 but still we could see this issue with the Decisioning engine as "decision-logic-compiler-8.1.4-565.jar:?"
HSBC
IN
Updated: 8 Nov 2019 8:53 EST
Pegasystems Inc.
IN
Hi Habeeb,
How are you? :)
For issues addressed in patch release, please refer this page: Resolved Issues
In case you are unable to find the required information, please create a new post. That would give more visibility for your query. Also make sure you add the complete details of your use case. It might help!
Thank you.