Question
Mindtree
IN
Last activity: 6 Apr 2018 19:26 EDT
Rules Upgrade - Failed with NoClassDefError - DirectStreamEnvironmentAdapter
As part of Upgrade process, we are upgrading from PRPC6.1 to PRPC 7.2.2, we ran the migrate rules and this was successful. Our current 6.1 environment, system name has been updated to "Pega_DEV4_ENV". We updated the setupDatabase.properties file with the current system name, that is changed "pega" (that is default in media file properties) to "Pega_DEV4_ENV". Now we ran the upgrade, the upgrade is failing with error:
NoClassDefFoundError - com.pega.pegarules.data.internal.clipboard.directstream.DirectStreamEnvironmentAdapter error. I did some research for this issue on PDN and found following links:
Link1: https://collaborate.pega.com/discussion/pzupgraderulemessages-rule-not-found-exception
This says this might be a bun and could be fixed with next ML release.
Link 2: htts://pdn.pega.com/support-articles/rulenotfound-pega-landing-system-upgrade-during-upgrade-717
This says update the system name to fix this issue. I wanted to confirm what the system name should be when I run the rules upgrade. Should it be current system name for PRPC 6.1 environment (Pega_DEV4_ENV) or should remain "pega" which comes OOTB with the media file.
My understanding was that we need to update system name to "Pega_DEV4_ENV".
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Mindtree
IN
We got the upgrade working. Solution was to delete the application specific system name and requestors from cloned pr_data_admin table before running rules upgrade.
Mindtree
IN
Thanks Dhev. We re-ran the upgrade script by resetting the system name (post database restore to previous state). The system name this time was "pega". We are still getting the same error. I am attaching our stack trace below:
Thanks Dhev. We re-ran the upgrade script by resetting the system name (post database restore to previous state). The system name this time was "pega". We are still getting the same error. I am attaching our stack trace below:
[updateActiveUserCount] Property definition for property pyActiveUserCount doesn't exist and hence not updating the active user
[java] 2017-03-02 09:38:52,659 [ <<masked>>] [ STANDARD] [ ] (l.access.ConnectionManagerImpl) INFO - Connection to pegarules left at shutdown
[java] 2017-03-02 09:38:52,682 [ <<masked>>] [ STANDARD] [ ] (l.access.ConnectionManagerImpl) INFO - Connection to pegadata left at shutdown
[java] 2017-03-02 09:38:52,685 [ <<masked>>] [ STANDARD] [ ] (external.util.NodeShutdownUtil) INFO - Cluster shutdown completed
[java] Mar 02, 2017 9:38:52 AM com.pega.pegarules.internal.bootstrap.PRBootstrap
[java] SEVERE: Problem during method invocation (main)
[java] com.pega.pegarules.pub.generator.RuleNotFoundException: pyVTable-RuleNotFound-NoMatches RULE-OBJ-ACTIVITY PZUPGRADERULEMESSAGES Pega-Landing-System-Upgrade 1 The 1 rules named 'PZUPGRADERULEMESSAGES' defined in the rulebase are:
[java] 1 related to applies-to class 'Pega-Landing-System-Upgrade', but were defined in rulesets which are not in your rulesetlist: 'Pega-LP-SystemSettings:07-10-17'.ok
[java]
[java]
[java] Current RulesetList:
[java] Pega-ProcessCommander:06-01,
[java] Pega-LP-ProcessAndRules:06-01,
[java] Pega-LP-Integration:06-01,
[java] Pega-LP-SystemSettings:06-01,
[java] Pega-LP-Reports:06-01,
[java] Pega-LP-UserInterface:06-01,
[java] Pega-LP-OrgAndSecurity:06-01,
[java] Pega-LP-DataModel:06-01,
[java] Pega-LP-Application:06-01,
[java] Pega-LP:06-01,
[java] Pega-UpdateManager:06-01,
[java] Pega-Feedback:06-01,
[java] Pega-AutoTest:06-01,
[java] Pega-AppDefinition:06-01,
[java] Pega-ImportExport:06-01,
[java] Pega-LocalizationTools:06-01,
[java] Pega-RuleRefactoring:06-01,
[java] Pega-ProcessArchitect:06-01,
[java] Pega-IntegrationArchitect:06-01,
[java] Pega-SystemArchitect:06-01,
[java] Pega-Desktop:06-01,
[java] Pega-EndUserUI:06-01,
[java] Pega-EventProcessing:06-01,
[java] Pega-Reporting:06-01,
[java] Pega-UIDesign:06-01,
[java] Pega-Gadgets:06-01,
[java] Pega-UIEngine:06-01,
[java] Pega-ProcessEngine:06-01,
[java] Pega-SearchEngine:06-01,
[java] Pega-IntegrationEngine:06-01,
[java] Pega-RulesEngine:06-01,
[java] Pega-Engine:06-01,
[java] Pega-ProCom:06-01,
[java] Pega-IntSvcs:06-01,
[java] Pega-WB:06-01,
[java] Pega-RULES:06-01
[java]
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.throwDetailedRuleNotFoundException(VirtualTableResolver.java:717)
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveToContainer(VirtualTableResolver.java:402)
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveRule(VirtualTableResolver.java:153)
[java] at com.pega.pegarules.generation.internal.vtable.VirtualTableImpl.resolveRule(VirtualTableImpl.java:311)
[java] at com.pega.pegarules.generation.internal.PRGenProviderImpl.get(PRGenProviderImpl.java:498)
[java] at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3536)
[java] at com.pega.pegarules.deploy.internal.util.UpgradeRuleMessages.main(UpgradeRuleMessages.java:79)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
[java] at java.lang.reflect.Method.invoke(Method.java:620)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:273)
[java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)
[java]
[java] Mar 02, 2017 9:38:52 AM com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega
[java] SEVERE: Problem during method invocation (main)
[java] com.pega.pegarules.pub.generator.RuleNotFoundException: pyVTable-RuleNotFound-NoMatches RULE-OBJ-ACTIVITY PZUPGRADERULEMESSAGES Pega-Landing-System-Upgrade 1 The 1 rules named 'PZUPGRADERULEMESSAGES' defined in the rulebase are:
[java] 1 related to applies-to class 'Pega-Landing-System-Upgrade', but were defined in rulesets which are not in your rulesetlist: 'Pega-LP-SystemSettings:07-10-17'.
[java]
[java]
[java] Current RulesetList:
[java] Pega-ProcessCommander:06-01,
[java] Pega-LP-ProcessAndRules:06-01,
[java] Pega-LP-Integration:06-01,
[java] Pega-LP-SystemSettings:06-01,
[java] Pega-LP-Reports:06-01,
[java] Pega-LP-UserInterface:06-01,
[java] Pega-LP-OrgAndSecurity:06-01,
[java] Pega-LP-DataModel:06-01,
[java] Pega-LP-Application:06-01,
[java] Pega-LP:06-01,
[java] Pega-UpdateManager:06-01,
[java] Pega-Feedback:06-01,
[java] Pega-AutoTest:06-01,
[java] Pega-AppDefinition:06-01,
[java] Pega-ImportExport:06-01,
[java] Pega-LocalizationTools:06-01,
[java] Pega-RuleRefactoring:06-01,
[java] Pega-ProcessArchitect:06-01,
[java] Pega-IntegrationArchitect:06-01,
[java] Pega-SystemArchitect:06-01,
[java] Pega-Desktop:06-01,
[java] Pega-EndUserUI:06-01,
[java] Pega-EventProcessing:06-01,
[java] Pega-Reporting:06-01,
[java] Pega-UIDesign:06-01,
[java] Pega-Gadgets:06-01,
[java] Pega-UIEngine:06-01,
[java] Pega-ProcessEngine:06-01,
[java] Pega-SearchEngine:06-01,
[java] Pega-IntegrationEngine:06-01,
[java] Pega-RulesEngine:06-01,
[java] Pega-Engine:06-01,
[java] Pega-ProCom:06-01,
[java] Pega-IntSvcs:06-01,
[java] Pega-WB:06-01,
[java] Pega-RULES:06-01
[java]
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.throwDetailedRuleNotFoundException(VirtualTableResolver.java:717)
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveToContainer(VirtualTableResolver.java:402)
[java] at com.pega.pegarules.generation.internal.vtable.ruleres.VirtualTableResolver.resolveRule(VirtualTableResolver.java:153)
[java] at com.pega.pegarules.generation.internal.vtable.VirtualTableImpl.resolveRule(VirtualTableImpl.java:311)
[java] at com.pega.pegarules.generation.internal.PRGenProviderImpl.get(PRGenProviderImpl.java:498)
[java] at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3536)
[java] at com.pega.pegarules.deploy.internal.util.UpgradeRuleMessages.main(UpgradeRuleMessages.java:79)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
[java] at java.lang.reflect.Method.invoke(Method.java:620)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:370)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:411)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:273)
[java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)
[java]
[java] Exception in thread "<<masked>>" java.lang.RuntimeException: Problem during method invocation (main)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:279)
[java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)
[java] Caused by: com.pega.pegarules.pub.generator.RuleNotFoundException: pyVTable-RuleNotFound-NoMatches RULE-OBJ-ACTIVITY PZUPGRADERULEMESSAGES Pega-Landing-System-Upgrade 1 The 1 rules named 'PZUPGRADERULEMESSAGES' defined in the rulebase are:
[java] 1 related to applies-to class 'Pega-Landing-System-Upgrade', but were defined in rulesets which are not in your rulesetlist: 'Pega-LP-SystemSettings:07-10-17'.
[java]
[java]
[java] Current RulesetList:
[java] Pega-ProcessCommander:06-01,
...
LTIMindtree
IN
We are also facing the same issue while running upgrade script for rules in case of upgrading from Pega6.1SP2 to Pega7.2.2.
A quick response would be greatly appreciated.
Accepted Solution
Mindtree
IN
We got the upgrade working. Solution was to delete the application specific system name and requestors from cloned pr_data_admin table before running rules upgrade.