[GEODE-9289] Configuration Class cannot be deserialized in old locators

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.12.3, 1.13.3, 1.14.0, 1.15.0
• Component/s: serialization
• Labels: blocks-1.15.0​ pull-request-available
• Assignee: Nabarun Nag
• Reporter: Nabarun Nag
• Created: 19/May/21 18:20
• Updated: 24/Feb/22 20:08
• Resolved: 23/Jul/21 22:38

Description

• Locators post version 1.12.0 when send out the Configuration to old version locators
• Old locators are not able to interpret the null jarNames sent by the new locators
• This causes a lot of NPEs in the old locators
• This clears out the jarNames in the configuration and if a server joins the cluster and requests the cluster configuration from the oldest locator, then it does not the jars deployed in the cluster.

Issue Links

• is related to: GEODE-9377 Revert deploymentName on Deployment configuration object.
• links to: GitHub Pull Request #6495
• links to: GitHub Pull Request #6562
• links to: GitHub Pull Request #6563
• links to: GitHub Pull Request #6564
• links to: GitHub Pull Request #6565
• links to: GitHub Pull Request #6592
• links to: GitHub Pull Request #6593
• links to: GitHub Pull Request #6594
• links to: GitHub Pull Request #6709