You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Steve Huston (JIRA)" <qp...@incubator.apache.org> on 2009/11/03 01:58:59 UTC

[jira] Resolved: (QPID-2170) Enqueuing a durable message with SQL persistence provider loaded throws 501 exception

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

Steve Huston resolved QPID-2170.
--------------------------------

    Resolution: Fixed

I believe this is now fixed. I can run part of the python persistence tests, which send messages. Other parts fail, but that is another issue, which I'll track separately.

Please update source from trunk and retry your scenario as well.

> Enqueuing a durable message with SQL persistence provider loaded throws 501 exception
> -------------------------------------------------------------------------------------
>
>                 Key: QPID-2170
>                 URL: https://issues.apache.org/jira/browse/QPID-2170
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.6
>         Environment: Windows Server 2008
>            Reporter: James Birdsall
>            Assignee: Steve Huston
>             Fix For: 0.6
>
>         Attachments: issue3-server-disconnect.txt
>
>
> This is related to Qpid-2168, but happens when the QpidStore database already exists at broker startup.
> In this scenario, there are three durable exchanges ("E1", "E2", "E3") and three durable queues ("Q1", "Q2", "Q3") already declared. The smoke test tries to declare three durable bindings, between like-numbered exchanges and queues, with routing keys of the form keyN, where N is the same digit. It gets through declaring all three bindings with any failures, but immediately after that the connection is closed. This operation works without the SQL persistence provider loaded.

-- 
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