You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dave Barnes (Jira)" <ji...@apache.org> on 2020/09/10 15:53:06 UTC
[jira] [Closed] (GEODE-8251) exception creating
domain.Configuration stops locator startup after rolling upgrade
[ https://issues.apache.org/jira/browse/GEODE-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dave Barnes closed GEODE-8251.
------------------------------
> 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
> Fix For: 1.13.0, 1.14.0
>
>
> 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)