Support Article
System throwing BADCLASSDEF error when it encounters an alert
SA-32565
Summary
BADCLASSDEF error occurred when it encounters any alert message. User is facing this issue when trying to connect to an external system.
Error Messages
Message: Attempting to access a rule with a bad defined-on-class.
Steps to Reproduce
Perform a SOAP integration call, which exceeds one second.
Root Cause
Within the LogHelper.java module, the doAlert method does not have pyClassName key when it opens the Rule-Message instance for the alert string.
Resolution
Apply HFix-28362.
Published February 10, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.