[
https://issues.apache.org/jira/browse/GEODE-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136148#comment-17136148
]
Jinmei Liao commented on GEODE-8251:
------------------------------------
This needs to be fixed before releasing 1.13.
we have this problem because we have problem deserializing the Deployment
object, which is now saved inside the Configuration object. The Deployment
object changes slightly between 1.12 and 1.13.
> 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
>
> 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)
