Question
Verizon
US
Last activity: 6 Jul 2016 11:56 EDT
Intermittent "rule with a bad defined-on class" error shows up on Connect-SOAP operation on tracer in Pega 7.1.8 Version, Are there any changes required to fix this error . As per PDN the issue was resolved with 7.1.8
Intermittent "rule with a bad defined-on class" error shows up on Connect-SOAP operation on tracer in Pega 7.1.8 Version, Are there any changes required to fix this error . As per PDN the issue was resolved with 7.1.8
Message was edited by: Lochan to add Category
Pegasystems Inc.
IN
Hi Anuj, Good morning!
- SR-A16032 is a similar issue raised on Pega 7.1.7.
- The SR is 'Resolved-MaintLevel' with resolution note as "This issue is resolved in update release 7.1.9"
- also please copy the PDN link where it says the issue is resolved in 7.1.8.
Thank you!
psahukaru
Verizon
US
Hi Phani,
Please find the URL below
SA-17989
SUMMARY
Intermittently, an error saying " Attempting to access a rule with a bad defined-on class: ___ is seen during soap-connect operations.
ERROR MESSAGES
Attempting to access a rule with a bad defined-on class: .
STEPS TO REPRODUCE
An alert is generated if a soap-connect operation takes more than 1 second and the issue occurs.
ROOT CAUSE
The message-reporting logic in the alert layer was missing the pxObjClass of a Rule-Message, which caused the error.
RESOLUTION
This issue has been resolved in the Pega 7.1.8 platform.
Pegasystems Inc.
IN
also could you please confirm the behavior with SA article - https://collaborate.pega.com/question/required-information-swift-net-ei-framework
Verizon
US
It's the same issue as mentioned on article https://collaborate.pega.com/question/required-information-swift-net-ei-framework
Pegasystems Inc.
US
Upon reviewing the associated SR with this post, I see that the SR has been withdrawn. I will be closing this discussion. If this occurs again, please re-open this post Anuj.