You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org> on 2009/12/29 19:19:00 UTC

[jira] Assigned: (QPID-2096) ExchangeRegistration shoud NOT automatically add durable Exchanges to messageStore

     [ https://issues.apache.org/jira/browse/QPID-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robbie Gemmell reassigned QPID-2096:
------------------------------------

    Assignee: Andrew Stitcher  (was: Robbie Gemmell)

> ExchangeRegistration shoud NOT automatically add durable Exchanges to messageStore
> ----------------------------------------------------------------------------------
>
>                 Key: QPID-2096
>                 URL: https://issues.apache.org/jira/browse/QPID-2096
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M4, 0.5, 0.6
>            Reporter: Martin Ritchie
>            Assignee: Andrew Stitcher
>            Priority: Blocker
>             Fix For: 0.6
>
>         Attachments: QPID-2096_trunk.patch
>
>
> Summary:
> DefaultExchangeRegistry.registerExchange() has a side effect of calling messageStore.createExchange.
> This behaviour is unexpected as DefaultQueueRegistry does not do the same for queues.
> The problem that this has is that on MessageStore recovery the recovered exchanges will be registered. Which after the MessageStore has been recovered will cause  createExchange to be called. The problem here is that the createExchange interface is not designed to cope with duplicates. Something that Derby highlights as it throws primary key constraint violation error.
> The solution is to decouple register and create as has been done with queues. This has not previously been seen as a) the Derby test profile is not run as often and b) the configuration used did not have an additional durable exchange defined.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org