[
https://issues.apache.org/jira/browse/QPID-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772297#action_12772297
]
Steve Huston commented on QPID-2170:
------------------------------------
It looks like after the exchanges, queues, bindings set up, a message is set
with routing key "key1" and that trips the exception. Does that make sense from
your test program? Can you attach your test program here?
> Declaring durable bindings with SQL persistence provider loaded causes broker
> to close connection
> --------------------------------------------------------------------------------------------------
>
> 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
> 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:[email protected]
