[
https://issues.apache.org/jira/browse/QPID-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085168#comment-14085168
]
Kim van der Riet commented on QPID-5948:
----------------------------------------
I agree that this is a minimalistic fix for just one manifestation of what is
probably a broad class of issue - that of durability dependency. I don't think
this is a simple issue to fix, and needs to be handled in multiple places,
including qmf tools. While I have not tested other scenarios, I'm sure that
there are other ways to create issues such as this, for example:
Create durable exchange
Create durable topic that uses durable exchange
Delete durable exchange
This creates a "dangling" durability dependency. If caught, would you prevent
the deletion until the dependent topic is also deleted, or do you delete both
(after a warning)?
I do agree that it would be nice to create the exchange on the fly in such a
case.
> [linearstore] Broker restart failure with durable topic using non-durable
> exchange
> ----------------------------------------------------------------------------------
>
> Key: QPID-5948
> URL: https://issues.apache.org/jira/browse/QPID-5948
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> If a durable topic is created which uses a non-durable exchange, then the
> recovery of the broker fails with "Exchange not found" error message.
> Although this is a configuration error, and can probably be reproduced in a
> number of ways, the fact that the broker will fail to start is a potentially
> serious problem.
> Steps to Reproduce:
> 0. Start broker with amqp and linearstore modules
> 1. qpid-config add exchange fanout test.ex
> 2. qpid-config add topic test.topic --argument exchange=test.ex --argument
> durable=True
> 3. Restart broker
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
