You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2014/03/28 09:49:16 UTC
[jira] [Updated] (QPID-5650) [Java Broker]
DurableConfigurationStoreUpgrader relies on the action of the
AMQQueueFactory to reunite queue with its dead letter exchange
[ https://issues.apache.org/jira/browse/QPID-5650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall updated QPID-5650:
-----------------------------
Description:
Currently, when upgrading a configuration store v4 store, if the store contains a queue that has a DLQ and associated DLE (*), it is the action of the AMQQueueFactory that is used to reunite the queue with its alternate exchange. This is rather a poor division of responsibilities and makes that the code in the factory to be rather more complicated than it ought.
The DurableConfigurationStoreUpgraders should be changed to that if they encounter an appropriately named exchange (i.e. one with standard _DLE suffix), they take the responsibility of producing ConfiguredObjectRecord for the queue with the alternateExchange attribute properly populated.
(*) The test BDBStoreUpgrade#xtestRecoveryOfQueueWithDLQ uses such a store
was:
Currently, when upgrading a configuration store v4 store, if the store contains a queue that has a DLQ and associated DLE (*), it is the action of the AMQQueueFactory that is used to reunite the queue with its alternate exchange. This is rather a poor division of responsibilities and makes that the code in the factory to be rather more complicated than it ought.
The DurableConfigurationStoreUpgraders should be changed to that if they encounter an appropriately named exchange (i.e. one with standard _DLE suffix), they take the responsibility of producing ConfiguredObjectRecord for the queue with the alternateExchange attribute properly populated.
> [Java Broker] DurableConfigurationStoreUpgrader relies on the action of the AMQQueueFactory to reunite queue with its dead letter exchange
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-5650
> URL: https://issues.apache.org/jira/browse/QPID-5650
> Project: Qpid
> Issue Type: Improvement
> Reporter: Keith Wall
>
> Currently, when upgrading a configuration store v4 store, if the store contains a queue that has a DLQ and associated DLE (*), it is the action of the AMQQueueFactory that is used to reunite the queue with its alternate exchange. This is rather a poor division of responsibilities and makes that the code in the factory to be rather more complicated than it ought.
> The DurableConfigurationStoreUpgraders should be changed to that if they encounter an appropriately named exchange (i.e. one with standard _DLE suffix), they take the responsibility of producing ConfiguredObjectRecord for the queue with the alternateExchange attribute properly populated.
> (*) The test BDBStoreUpgrade#xtestRecoveryOfQueueWithDLQ uses such a store
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org