@LivyaJ02 I believe an advisory email was sent out to our clients advising them that users who have encountered issues with the testing and rollout of the hotfix should engage Global Client Support.
You may wish to log two separate tickets via the MSP:
- one ticket for the initial decision made to apply A22 and the subsequent testing efforts on custom rules created that utilize Java reflection or other Java Injection methods as described in Configuring Java Injection Check. It is possible that you may not need to install the hotfix and our support team can help evaluate if all that is needed is a modification to your SOAP connector code.
- one ticket for correcting the subsequent rollback problems you have encountered. We have seen instances where issues arise, if users have already committed the hotfix, look to either restore the system from backup or utilize the 'patchdate' parameter in the prbootstrap file to specify an engine code date earlier than when the A22 hotfix was applied.
Our Platform Service Engineering team dealing with the above support tickets will be able to advise your on your particular scenario.
Please could I ask that you log a support Incident, and provide the INC number in this thread so that we can help you track its progress?
Posted: 1 year ago
Posted: 27 Apr 2022 8:22 EDT
Livya Paul (LivyaJ02)
Software Developments Engineer
We have received the below workaround from engineering. Could you please try this before making DB restore?
Can you try the below workaround:
Roll back all the Hotfixes. Bring up a single node with "identification/cluster/protocol" value="standalone". Install Hotfixes other than security ones. Bring up whole Cluster by removing setting "identification/cluster/protocol" value= “standalone”
We added the above configuration setting in prconfig.XML file under <env name> section and then restarted the server.