Andy Gustafson created ARTEMIS-4371:
---------------------------------------

             Summary: Rolling upgrade causes messages to not be forwarded 
between nodes in cluster
                 Key: ARTEMIS-4371
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4371
             Project: ActiveMQ Artemis
          Issue Type: Bug
    Affects Versions: 2.28.0, 2.27.0, 2.26.0
            Reporter: Andy Gustafson
         Attachments: artemisbugconfig.tar.gz

I've found what appears to me to be a bug in forwarding messages between 
brokers in a symmetric cluster while doing a rolling upgrade. From my brief 
testing this problem starts on version 2.26. I have not tested with a starting 
version other than 2.19.1.

 

*How to reproduce*

I've attached a basic configuration in the tar file. Due to size limits of Jira 
I wasn't able to include the Artemis releases.

Download the attached tar.gz with the broker configs and extract in /opt. 
Download/extract artemis 2.19.1 and 2.26.0 to the /opt/artemisbug directory.

*From the /opt/artemisbug directory*

Start broker1
{code:java}
broker1/bin/artemis run{code}
Start broker2
{code:java}
broker2/bin/artemis run{code}
Create a producer on broker1 
{code:java}
./apache-artemis-2.19.1/bin/artemis producer --url=tcp://localhost:61618 
--clientID=123 --destination=queue://test --message-count=10000000 
--non-persistent --sleep=2{code}
Create consumer on broker2
{code:java}
./apache-artemis-2.19.1/bin/artemis consumer --url=tcp://localhost:61619 
--clientID=321 --destination=queue://test --message-count=10000000{code}
Stop broker2

upgrade broker2 (script included for convenience)
{code:java}
./broker2/etc/cutover26.sh{code}
Start broker2
{code:java}
broker2/bin/artemis run{code}
Restart consumer on broker2
{code:java}
./apache-artemis-2.19.1/bin/artemis consumer --url=tcp://localhost:61619 
--clientID=321 --destination=queue://test --message-count=10000000{code}
 

At this point you should see no messages are being consumed even even though 
broker2 is a member of the cluster and there is a producer on broker1. No 
errors appear to be logged server side either.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to