You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2016/06/20 13:54:05 UTC
[jira] [Created] (ARTEMIS-583) Suprious queue created along with
topic
Lionel Cons created ARTEMIS-583:
-----------------------------------
Summary: Suprious queue created along with topic
Key: ARTEMIS-583
URL: https://issues.apache.org/jira/browse/ARTEMIS-583
Project: ActiveMQ Artemis
Issue Type: Bug
Reporter: Lionel Cons
This is probably a consequence of ARTEMIS-412.
When using STOMP to send a message to a non-existing topic (here {{jms.topic.test}}), the matching Address object is created:
{code}
"org.apache.activemq.artemis:brokerName=\"artemis\",module=Core,name=\"jms.topic.test\",serviceType=Address,type=Broker" : {
"Address" : "jms.topic.test",
"AddressSize" : 0,
"BindingNames" : [
"jms.topic.test"
],
"NumberOfBytesPerPage" : 1048576,
"NumberOfMessages" : 0,
"NumberOfPages" : 0,
"Paging" : false,
"QueueNames" : [
"jms.topic.test"
],
"Roles" : [
[
"administrators",
true,
true,
true,
true,
true,
true,
true
]
],
"RolesAsJSON" : "[{\"createDurableQueue\":true,\"createNonDurableQueue\":true,\"name\":\"administrators\",\"deleteNonDurableQueue\":true,\"consume\":true,\"send\":true,\"deleteDurableQueue\":true,\"manage\":true}]"
},
{code}
So far, so good.
However, I also see an eponymous Queue object being created, with a weird Filter.
{code}
"org.apache.activemq.artemis:address=\"jms.topic.test\",brokerName=\"artemis\",module=Core,name=\"jms.topic.test\",serviceType=Queue,type=Broker" : {
"Address" : "jms.topic.test",
"ConsumerCount" : 0,
"DeadLetterAddress" : "jms.queue.DLQ",
"DeliveringCount" : 0,
"Durable" : true,
"ExpiryAddress" : "jms.queue.ExpiryQueue",
"Filter" : "__AMQX=-1",
"FirstMessageAsJSON" : "[{}]",
"FirstMessageTimestamp" : null,
"ID" : 6,
"MessageCount" : 0,
"MessagesAcknowledged" : 0,
"MessagesAdded" : 0,
"Name" : "jms.topic.test",
"Paused" : false,
"ScheduledCount" : 0,
"Temporary" : false
},
{code}
I don't see why this would be needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)