You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2018/04/30 16:17:00 UTC

[jira] [Commented] (ARTEMIS-1605) RBAC back compatibility Issue in upgrading broker from 2.3

    [ https://issues.apache.org/jira/browse/ARTEMIS-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458710#comment-16458710 ] 

clebert suconic commented on ARTEMIS-1605:
------------------------------------------

Blocker status is not meant to reflect your priority (how important is for you). it's about clasification if a release can or can't be done without a fix.

> 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
>    Affects Versions: 2.5.0
>            Reporter: Michael Andre Pearce
>            Priority: Major
>
> 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
(v7.6.3#76005)