[
https://issues.apache.org/jira/browse/GEODE-9289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17386531#comment-17386531
]
ASF subversion and git services commented on GEODE-9289:
--------------------------------------------------------
Commit 4e70bfcb1949b8399cf20a72d21ac556d0835cf2 in geode's branch
refs/heads/develop from Nabarun Nag
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=4e70bfc ]
GEODE-9289: Configuration class modified into VersionedDataSerializable
* This was suppose to be a part of the initial commit for GEODE-9289
* However we had to wait for a revert in the deployement data structure
in GEODE-9377
* This commit is already a part of the previous releases of Apache Geode
> Configuration Class cannot be deserialized in old locators
> ----------------------------------------------------------
>
> Key: GEODE-9289
> URL: https://issues.apache.org/jira/browse/GEODE-9289
> Project: Geode
> Issue Type: Bug
> Components: serialization
> Reporter: Nabarun Nag
> Priority: Major
> Labels: blocks-1.15.0, pull-request-available
> Fix For: 1.12.3, 1.13.3, 1.14.0
>
>
> * 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
