[ 
https://issues.apache.org/jira/browse/ARTEMIS-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565048#comment-16565048
 ] 

Paweł Puterla edited comment on ARTEMIS-1592 at 8/1/18 9:36 AM:
----------------------------------------------------------------

The problem is not all queues are deleted.

I mean all JMS queues get deleted but address and core queue sometimes is left 
not deleted.

(note -> I am using wildcard addressing scheme! maybe that's the issue? eg 
address like jms.queue.myqueues.#)

 

I understand this is not precise description - I run on this problem and worked 
around it (by implementing custom  reaper and disabling auto-delete). Currently 
my resources are busy so I can't go back to this.

 

Personally I shall wait for artemis 2.x to be included in WF distribution and 
then retest it.


was (Author: pputerla):
The problem is not all queues are deleted.

I mean all JMS queues get deleted but address and core queue is left.

I understand this is not precise description - I run on this problem and worked 
around it (by implementing custom  reaper and disabling auto-delete). Currently 
my resources are busy so I can't go back to this.

 

Personally I shall wait for artemis 2.x to be included in WF distribution and 
then retest it.

> Clustered broker throws "java.lang.IllegalStateException: Cannot find binding 
> for [Queue]" for auto-deleted queues
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1592
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1592
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.4.0, 2.5.0, 2.6.0
>         Environment: Artemis 2.6.0, JDK8 64bit, Windows 7
>            Reporter: Johan Stenberg
>            Priority: Minor
>         Attachments: ArtemisTest.java
>
>
> When a clustered, auto-created queue is auto-deleted (i.e. when the 
> consumer-count and message-count reach 0) this stack-trace can be logged:
> {noformat}
> ERROR: AMQ224037: cluster connection Failed to handle message
> java.lang.IllegalStateException: Cannot find binding for 
> queues.myQueueb4b3a157-f51c-11e7-b013-54524514640f
>       at 
> org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doConsumerClosed(ClusterConnectionImpl.java:1360)
>       at 
> org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.handleNotificationMessage(ClusterConnectionImpl.java:1046)
>       at 
> org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:1016)
>       at 
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1003)
>       at 
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:50)
>       at 
> org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1126)
>       at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
>       at 
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
>       at 
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
>       at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>       at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>       at java.lang.Thread.run(Thread.java:748)
> {noformat}
> There is no functional impact associated with this message.



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

Reply via email to