Hi Samuel-

The ActiveMQ command line has a couple of tools to that can give you those 
numbers..

Table of queue (aka destination) stats:
./bin/activemq dstat 

List of broker metrics:
./bin/activemq bstat

Thanks,
Matt Pavlovich

> On Oct 18, 2024, at 3:04 AM, Samuel VISCAPI <samuel.visc...@xelians.fr> wrote:
> 
> Dear François and Matt,
> 
> Thanks for your input, really appreciated.
> 
> I believe I’ll try option 2 (Naturally drain the 5.13.x broker so it is 
> empty, and simply start the 5.17.x broker to handle new messages).
> 
> How can I make sure the broker is empty via the command line ?
> 
> « ./activemq list » does tell me about a broker at URL 
> service:jmx:rmi://127.0.0.1/[…] but I can’t browse its contents with « 
> ./activemq browse », looks like the –amqurl option is incompatible with that 
> kind of URL.
> 
> What am I doing wrong ?
> 
> Best regards,
> 
> Samuel
> 
> On 2024/10/11 14:22:39 Francois Papon wrote:
>> Hi,
>> 
>> You also need to be careful of the activemq.xml configuration, some config 
>> can need updates.
>> 
>> Regards,
>> 
>> François
>> fpa...@apache.org
>> francois.pa...@openobject.fr
>> 
>> Le 11/10/2024 à 15:57, Matt Pavlovich a écrit :
>>> Hello Samuel-
>>> 
>>> Upgrades are fairly straightforward. You can generally copy the same 
>>> configuration file from 5.13.x to 5.17.x without much headache to verify 
>>> the functionality is the same. If you have an advanced configuration or use 
>>> case, you may need to seek an expert for assistance.
>>> 
>>> For the cutover, a couple of options:
>>> 
>>> 1. Turn both on and forward all messages from the 5.13.x to the 5.17.x 
>>> using a static network connector to do store-and-forward.
>>> 
>>> 2. Naturally drain the 5.13.x broker so it is empty, and simply start the 
>>> 5.17.x broker to handle new messages
>>> 
>>> 3. Copy kahadb data over from 5.13.x to 5.17.x
>>> 
>>> #1 and #2 are generally the better options. #3 can get tricky if you do 
>>> advanced stuff like scheduling, etc.
>>> 
>>> Thanks,
>>> Matt Pavlovich
>>> 
>>>> On Oct 11, 2024, at 3:46 AM, SAMUEL VISCAPI<sa...@atos.net.INVALID> wrote:
>>>> 
>>>> Dear all,
>>>> 
>>>> I have to upgrade ActiveMQ classic for one of our customers.
>>>> 
>>>> The current version is 5.13.1 and I need to upgrade it to 5.17.6.
>>>> 
>>>> I couldn’t find any documentation regarding the upgrade process on the 
>>>> official website.
>>>> 
>>>> Are there any steps I should be aware of before upgrading ActiveMQ classic 
>>>> ?
>>>> 
>>>> Best regards,
>>>> 
>>>> Samuel
>>>> Ce message et toutes les pièces jointes (ci-après le "message") sont 
>>>> établis à l’intention exclusive des destinataires désignés. Il contient 
>>>> des informations confidentielles et pouvant être protégé par le secret 
>>>> professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
>>>> immédiatement l'expéditeur et de détruire le message. Toute utilisation de 
>>>> ce message non conforme à sa destination, toute diffusion ou toute 
>>>> publication, totale ou partielle, est interdite, sauf autorisation 
>>>> expresse de l’émetteur. L'internet ne garantissant pas l'intégrité de ce 
>>>> message lors de son acheminement, Atos (et ses filiales) décline(nt) toute 
>>>> responsabilité au titre de son contenu. Bien que ce message ait fait 
>>>> l’objet d’un traitement anti-virus lors de son envoi, l’émetteur ne peut 
>>>> garantir l’absence totale de logiciels malveillants dans son contenu et ne 
>>>> pourrait être tenu pour responsable des dommages engendrés par la 
>>>> transmission de l’un d’eux.
>>>> 
>>>> This message and any attachments (the "message") are intended solely for 
>>>> the addressee(s). It contains confidential information, that may be 
>>>> privileged. If you receive this message in error, please notify the sender 
>>>> immediately and delete the message. Any use of the message in violation of 
>>>> its purpose, any dissemination or disclosure, either wholly or partially 
>>>> is strictly prohibited, unless it has been explicitly authorized by the 
>>>> sender. As its integrity cannot be secured on the internet, Atos and its 
>>>> subsidiaries decline any liability for the content of this message. 
>>>> Although the sender endeavors to maintain a computer virus-free network, 
>>>> the sender does not warrant that this transmission is virus-free and will 
>>>> not be liable for any damages resulting from any virus transmitted.
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:users-unsubscr...@activemq.apache.org
>>> For additional commands, e-mail:users-h...@activemq.apache.org
>>> For further information, visit:https://activemq.apache.org/contact
>>> 
>>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@activemq.apache.org
For additional commands, e-mail: users-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact


Reply via email to