[ https://issues.apache.org/jira/browse/ARTEMIS-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16325209#comment-16325209 ]
Michael Andre Pearce commented on ARTEMIS-1605: ----------------------------------------------- [~andytaylor] could you look at this possibly? Two options i can think of are: 1) Not cause the error, if a management.xml is needed even blank its auto created. 2) In the error provide a more specific exception, with a link to documentation about it and how to manually create one, to provide same behaviour as previous if upgrading. > RBAC back compatibility Issue in upgrading broker from 2.3 > ---------------------------------------------------------- > > Key: ARTEMIS-1605 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1605 > Project: ActiveMQ Artemis > Issue Type: Bug > Reporter: Michael Andre Pearce > Priority: Blocker > > On taking an older 2.3 broker and taking master i have noticed a simply > upgrade by repointing the artemis home, the server won't start. > ./bin/artemis run > Invalid configuration URI, can't find file: management.xml > Configuration should be specified as 'scheme:location'. Default configuration > is 'xml:${ARTEMIS_INSTANCE}/etc/bootstrap.xml' > This seems due to changes in ARTEMIS-1463 that create a new management.xml > and expect this but unfortunately is not back compatible, e.g. no handling if > not present. -- This message was sent by Atlassian JIRA (v6.4.14#64029)