[ 
https://issues.apache.org/jira/browse/GEODE-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Owen Nichols updated GEODE-8251:
--------------------------------
    Fix Version/s: 1.14.0

> 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)

Reply via email to