activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1588) Clustering not working with auto-created queues
Date Mon, 08 Jan 2018 18:23:00 GMT


Justin Bertram commented on ARTEMIS-1588:

I ran your test (as well as creating one of my own) and it appears to me like the consumer
is able to receive the message without issue.  Your test-case logged this:

bq. Message received. JmsBytesMessage { org.apache.qpid.jms.provider.amqp.message.AmqpJmsBytesMessageFacade@7468f63b

The exception is thrown in response to an internal notification message regarding the closing
of the consumer.  I believe this is due to a race condition between the auto-delete logic
(which deletes the auto-created queue when there are no more messages and no more consumers)
and some cluster management logic.  If you like, you can avoid this exception by setting {{auto-delete-queues}}
to {{false}} in your address-setting.  In any case there is no functional impact as far as
I can see.

If you want to keep this JIRA open please rename it to something like "Stack-trace logged
when auto-deleting clustered queue."  I believe the current title is misleading.

> Clustering not working with auto-created queues
> -----------------------------------------------
>                 Key: ARTEMIS-1588
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.4.0
>            Reporter: Johan Stenberg
>         Attachments:, pom.xml
> When a client sends a message to an auto-created queue on one broker instance, the message
is not forwarded to other broker instances of the same cluster, thus clients subscribed to
the other members will not receive the message. Instead a "java.lang.IllegalStateException:
Cannot find binding for queues.myQueueeaac327b-f3a0-11e7-8158-54524514640f" is logged.
> I am attaching a test class with two tests where two broker instances are started in
a cluster. Each instance has one client connected. When the test queue is pre-created, the
published message is forwarded to the other instance as expected. However, when the test queue
is auto-created the client connected to the second broker does not receive the message.

This message was sent by Atlassian JIRA

View raw message