[
https://issues.apache.org/jira/browse/GEODE-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140673#comment-17140673
]
ASF subversion and git services commented on GEODE-8251:
--------------------------------------------------------
Commit 856380f3c5c5646facc2488ad2cd76602374b1eb in geode's branch
refs/heads/support/1.13 from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=856380f ]
GEODE-8251: make sure Configuration can be deserialized post 1.12. (#5257)
Co-authoried-by: Alberto Gomez <alberto.go...@est.tech>
> exception creating domain.Configuration stops locator startup after rolling
> upgrade
> -----------------------------------------------------------------------------------
>
> Key: GEODE-8251
> URL: https://issues.apache.org/jira/browse/GEODE-8251
> Project: Geode
> Issue Type: Bug
> Components: configuration
> Affects Versions: 1.13.0
> Reporter: Bill Burcham
> Assignee: Jinmei Liao
> Priority: Major
> Labels: GeodeOperationAPI
>
> As reported on the dev@geode mailing list
> https://markmail.org/message/qfnnj2s2x7dzbnzx and shown in the
> {{testRollingUpgradeOfGeodeWithGfs}} test in PR:
> https://github.com/apache/geode/pull/5224, if custom Jars are deployed, the
> locator doesn't start after a rolling upgrade and we see:
> {code}
> org.apache.geode.SerializationException: Could not
> create an instance of
> org.apache.geode.management.internal.configuration.domain.Configuration
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
