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

Simon Chalmers updated ARTEMIS-1928:
------------------------------------
    Description: 
 

Steps to produce, using a producing application (running AMQPNetLite) 
connecting to node1 of the cluster:
 * Create queue1, publish 199 messages to it
 * Create queue2, publish 1 message to it

Running a consuming application (AMQPNetLite) connecting to node2 of the 
cluster:
 * On node1 of the cluster, queue1 & queue2 now have 0 messages in it
 * On node2 of the cluster, queue1 has 200 messages in it and queue2 has 2 
messages in it (i.e. an additional message in each queue, even though the 
consuming application is not publishing any messages).
 * The consuming application connected to node2 of the cluster does not consume 
any messages off either queue1 or queue2 from node2 (of the cluster).

In artemis.log on node2 of the cluster, the following appears:

2018-06-13 02:41:00,604 WARN  [org.apache.activemq.artemis.core.server] 
AMQ222151: removing consumer which did not handle a message, 
consumer=ServerConsumerImpl

Full log @ [https://pastebin.com/N0Jdr0Ha] 

  was:
 

Steps to produce, using a producing application (running AMQPNetLite) 
connecting to node1 of the cluster:
 * Create queue1, publish 199 messages to it
 * Create queue2, publish 1 message to it

Running a consuming application (AMQPNetLite) connecting to node2 of the 
cluster:
 * On node1 of the cluster, queue1 & queue2 now have 0 messages in it
 * On node2 of the cluster, queue1 has 200 messages in it and queue2 has 2 
messages in it (i.e. an additional message in each queue, even though the 
consuming application is not publishing any messages).
 * The consuming application connected to node2 of the cluster does not consume 
any messages off either queue1 or queue2 from node2 (of the cluster).

In artemis.log on node2 of the cluster, the following error appears:

2018-06-13 02:41:00,604 WARN  [org.apache.activemq.artemis.core.server] 
AMQ222151: removing consumer which did not handle a message, 
consumer=ServerConsumerImpl

Full log @ [https://pastebin.com/N0Jdr0Ha] 


> Messages in queues on other nodes in a cluster are not consumable
> -----------------------------------------------------------------
>
>                 Key: ARTEMIS-1928
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1928
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP, Broker
>    Affects Versions: 2.6.1
>         Environment: * Broker Version: 2.6.1
>  * Client: AMQPNetLite v2.1.2
>  * Host OS: Linux node 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 
> (2018-05-07) x86_64 GNU/Linux
>  * Host Platform: AWS EC2
>  * broker.xml from node1 attached as node1-broker.xml
>  * broker.xml from node2 attaches as node2-broker.xml
>            Reporter: Simon Chalmers
>            Priority: Major
>         Attachments: node1-broker.xml, node2-broker.xml
>
>
>  
> Steps to produce, using a producing application (running AMQPNetLite) 
> connecting to node1 of the cluster:
>  * Create queue1, publish 199 messages to it
>  * Create queue2, publish 1 message to it
> Running a consuming application (AMQPNetLite) connecting to node2 of the 
> cluster:
>  * On node1 of the cluster, queue1 & queue2 now have 0 messages in it
>  * On node2 of the cluster, queue1 has 200 messages in it and queue2 has 2 
> messages in it (i.e. an additional message in each queue, even though the 
> consuming application is not publishing any messages).
>  * The consuming application connected to node2 of the cluster does not 
> consume any messages off either queue1 or queue2 from node2 (of the cluster).
> In artemis.log on node2 of the cluster, the following appears:
> 2018-06-13 02:41:00,604 WARN  [org.apache.activemq.artemis.core.server] 
> AMQ222151: removing consumer which did not handle a message, 
> consumer=ServerConsumerImpl
> Full log @ [https://pastebin.com/N0Jdr0Ha] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to