Skip to Content
0
Former Member
Apr 17, 2018 at 02:19 PM

Promotion Engine mvnVersion did not match to the KieModule and container version

368 Views

Hi Experts,

I hope you are well. We found that the previous issue I raised was because of too much containers where being used and it has reached the memory threshold. Now we have another issue and I think this one is pretty much OOTB since we only touched the actions and conditions as part of our customization.

We've experienced this issue in production environment where the mvnVersion somehow did not match the current version. When the promotion evaluation tries to look for that current mvnVersion it can't find it and it tries to fall back to the old version which is way too far from the current mvnVersion. I found out that during the publishing of mvnversion 1.0.243, the container version and module version somehow did not update to 1.0.243 instead it remained to 1.0.242. Do you know if this is a known issue with promotion engine? We’re using the 6.2.15 version of hybris commerce.

Logs during promotion evaluation:

[DefaultPlatformRuleEngineService] KieContainer with releaseId [hybris-rules:promotions:1.0.243] was not found. Trying to look up for closest matching version... [DefaultPlatformRuleEngineService] Found KieContainer with releaseId [hybris-rules:promotions:1.0.102] --------- (I’m not sure why this has jumped way too far from the current version. This has caused the other promotions published on the later versions to not work.)

Logs during the publishing of mvnVersion 1.0.243

[RuleEngine-module-swapping-0] [DefaultRuleEngineBootstrap] The new module with deployedMvnVersion [1.0.243] was activated successfully
[RuleEngine-module-swapping-0] [DefaultRuleEngineBootstrap] Swapping to a new created container [hybris-rules:promotions:1.0.242] -------(I think this one should be 1.0.243) [RuleEngine-module-swapping-0] [DefaultPlatformRuleEngineService] Notifying other nodes about Kie Container swap completed for module [hybris-rules:promotions:1.0.242] and version [1.0.242] -------(I think this one should be 1.0.243) [RuleEngine-module-swapping-0] [DefaultPlatformRuleEngineService] Swapping to a newly created container [hybris-rules:promotions:1.0.242] is finished successfully [RuleEngine-module-swapping-0] [ModuleSwapCompletedListener] Received event [RuleEngineModuleSwapCompletedEvent{rulesModuleName='hybris-rules:promotions:1.0.242', previousRulesModuleVersion='1.0.242', rulesModuleVersion='1.0.242', failed=false, failureReason='null'}]. Dispatching it to backoffice notification framework (Notice that it did not remove the old Kie module)

Logs during the publishing of mvnVersion 1.0.242 I think this one is the right way

[RuleEngine-module-swapping-0] [DefaultRuleEngineBootstrap] The new module with deployedMvnVersion [1.0.242] was activated successfully
[RuleEngine-module-swapping-0] [DefaultRuleEngineBootstrap] Swapping to a new created container [hybris-rules:promotions:1.0.242] [RuleEngine-module-swapping-0] [DefaultPlatformRuleEngineService] Notifying other nodes about Kie Container swap completed for module [hybris-rules:promotions:1.0.242] and version [1.0.242] [RuleEngine-module-swapping-0] [DefaultPlatformRuleEngineService] Swapping to a newly created container [hybris-rules:promotions:1.0.242] is finished successfully [RuleEngine-module-swapping-0] [ModuleSwapCompletedListener] Received event [RuleEngineModuleSwapCompletedEvent{rulesModuleName='hybris-rules:promotions:1.0.242', previousRulesModuleVersion='1.0.241', rulesModuleVersion='1.0.242', failed=false, failureReason='null'}]. Dispatching it to backoffice notification framework [RuleEngine-module-swapping-0] [DefaultRuleEngineKieModuleSwapper] Removing old Kie module [hybris-rules:promotions:1.0.241]

Looking forward to your response.

Cheers, Dom