You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2020/11/20 16:17:00 UTC

[jira] [Resolved] (ARTEMIS-2999) Documentation insufficient for updates of existing Artemis installation

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

Justin Bertram resolved ARTEMIS-2999.
-------------------------------------
    Resolution: Fixed

> Documentation insufficient for updates of existing Artemis installation
> -----------------------------------------------------------------------
>
>                 Key: ARTEMIS-2999
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2999
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.16.0
>            Reporter: arne anka
>            Priority: Minor
>
> Apparently the only bit of information regarding updates of an existing Artemis installation is the "Versions" section of the user manual.
> But even with 2.16.0 it ends with 2.14 and the instructions for 2.14 are less than helpful:
> "Make sure the existing queues have their parameters set according to the {{broker.xml}} values before upgrading."
>  
>  * What parameters exactly?
>  * How exactly _DO_ I update? Unpack the new archive and copy $INSTANCE over?
>  * $INSTANCE/bin/ scripts are generated during instance creation – are they still valid? Do I need to change anything?
> Since the documentation in general is little user friendly for users that do not work full time with Artemis, I had a hard time setting up Artemis initially with the existing documentation (and judging from my research back then I am far from being alone), and I certainly don't want to jeopardize it now due to a lack of useful directions.
> Would it be possible to revisit this and documentation in general keeping in mind that also users outside of the Artemis community may want to use this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)