Issue Description:
After the SRM upgrade that included Java 17, previously stored report files serialized using older Java versions fail during deserialization. This occurs due to incompatibilities introduced by changes in Java’s serialization/deserialization mechanisms as part of the Java upgrade.
When deserialization fails, the system’s existing error-handling logic incorrectly treats these reports as invalid or corrupted, which triggers automatic cleanup. As a result, reports created prior to the upgrade are unintentionally deleted when accessed, leading to unexpected data loss.
Summary:
Java serialization incompatibility introduced during the Java 17 upgrade has impacted the pre-stored reports on SRM environment. The solution identified below addresses the deserialization incompatibility and ensures that previously stored reports remain accessible and available after the upgrade.
Resolution:
Hotfix has been created to resolve the issue observed.This hotfix needs to be applied post SRM upgrade to 6.1.0.0 version.
Steps to apply Hotfix: