[
https://issues.apache.org/jira/browse/QPID-5647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall resolved QPID-5647.
------------------------------
Resolution: Fixed
Fix Version/s: 0.29
Retested again today, the issue is now resolved. I suspect this would have
been the work of QPID-5710 as this cleanly separated queue creation from
recovery.
> [Java Broker] Spurious DLQ is created when DLQ are enabled at Broker (or
> Virtualhost) level
> --------------------------------------------------------------------------------------------
>
> Key: QPID-5647
> URL: https://issues.apache.org/jira/browse/QPID-5647
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.28, 0.29
> Reporter: Keith Wall
> Fix For: 0.29
>
>
> If I turn on DLQs at Broker level, then create a new durable queue (my
> queue), the system automatically creates the DLQ and DLE (myqueue_DLQ and
> myqueue_DLE respectively). If I then restart the Broker, I find that the not
> only do I have the queues/exchanges described above, the system also creates
> a additional DLQ called myqueue_DLQ_DLQ.
> The output from the logs on restart:
> {noformat}
> 2014-03-27 13:55:33,427 INFO [Broker-Configuration-Thread]
> (exchange.created) - [Broker] EXH-1001 : Create : Durable Type: headers Name:
> amq.match
> 2014-03-27 13:55:33,430 INFO [Broker-Configuration-Thread]
> (exchange.created) - [Broker] EXH-1001 : Create : Durable Type: topic Name:
> amq.topic
> 2014-03-27 13:55:33,433 INFO [Broker-Configuration-Thread]
> (exchange.created) - [Broker] EXH-1001 : Create : Durable Type: direct Name:
> amq.direct
> 2014-03-27 13:55:33,434 INFO [Broker-Configuration-Thread]
> (exchange.created) - [Broker] EXH-1001 : Create : Durable Type: fanout Name:
> amq.fanout
> 2014-03-27 13:55:33,435 INFO [Broker-Configuration-Thread]
> (messagestore.recovery_start) - [Broker] [vh(/default)/ms(DerbyMessageStore)]
> MST-1004 : Recovery Start
> 2014-03-27 13:55:33,552 INFO [Broker-Configuration-Thread]
> (exchange.created) - [Broker] EXH-1001 : Create : Durable Type: fanout Name:
> myqueue_DLE
> 2014-03-27 13:55:33,582 INFO [Broker-Configuration-Thread] (queue.created) -
> [Broker] [vh(/default)/qu(myqueue_DLQ)] QUE-1001 : Create : Durable
> 2014-03-27 13:55:33,582 INFO [Broker-Configuration-Thread]
> (exchange.created) - [Broker] EXH-1001 : Create : Durable Type: fanout Name:
> myqueue_DLQ_DLE
> 2014-03-27 13:55:33,583 INFO [Broker-Configuration-Thread] (queue.created) -
> [Broker] [vh(/default)/qu(myqueue_DLQ_DLQ)] QUE-1001 : Create : Durable
> 2014-03-27 13:55:33,586 INFO [Broker-Configuration-Thread] (binding.created)
> - [Broker]
> [vh(/default)/ex(fanout/myqueue_DLQ_DLE)/qu(myqueue_DLQ_DLQ)/rk(dlq)]
> BND-1001 : Create
> 2014-03-27 13:55:33,588 INFO [Broker-Configuration-Thread] (binding.created)
> - [Broker] [vh(/default)/ex(fanout/myqueue_DLE)/qu(myqueue_DLQ)/rk(dlq)]
> BND-1001 : Create
> 2014-03-27 13:55:33,589 INFO [Broker-Configuration-Thread] (queue.created) -
> [Broker] [vh(/default)/qu(myqueue)] QUE-1001 : Create : Durable
> 2014-03-27 13:55:33,591 INFO [Broker-Configuration-Thread]
> (configstore.recovery_complete) - [Broker]
> [vh(/default)/ms(DerbyMessageStore)] CFG-1005 : Recovery Complete
> 2014-03-27 13:55:33,643 INFO [Broker-Configuration-Thread]
> (transactionlog.recovery_start) - [Broker]
> [vh(/default)/ms(DerbyMessageStore)] TXN-1004 : Recovery Start
> 2014-03-27 13:55:33,665 INFO [Broker-Configuration-Thread]
> (transactionlog.recovery_complete) - [Broker]
> [vh(/default)/ms(DerbyMessageStore)] TXN-1006 : Recovery Complete
> 2014-03-27 13:55:33,666 INFO [Broker-Configuration-Thread]
> (messagestore.recovery_complete) - [Broker]
> [vh(/default)/ms(DerbyMessageStore)] MST-1006 : Recovery Complete
> {noformat}
> This is a regression introduced by QPID-5625 (rev. 1576826).
> It appears that the system is no longer persisting x-qpid-dlq-enabled=false,
> on the DLQ, so the global setting means that on restart the system create
> another.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
