You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "James Birdsall (JIRA)" <qp...@incubator.apache.org> on 2009/10/29 02:42:59 UTC
[jira] Created: (QPID-2170) Declaring durable bindings with SQL
persistence provider loaded causes broker to close connection
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
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
[jira] Commented: (QPID-2170) Declaring durable bindings with SQL
persistence provider loaded causes broker to close connection
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772134#action_12772134 ]
Steve Huston commented on QPID-2170:
------------------------------------
I believe this was fixed in r831476. But I don't have the test program to repeat it. Please retest with an updated trunk and let me know how it looks now.
> 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:dev-subscribe@qpid.apache.org
[jira] Closed: (QPID-2170) Enqueuing a durable message with SQL
persistence provider loaded throws 501 exception
Posted by "James Birdsall (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Birdsall closed QPID-2170.
--------------------------------
Confirmed, this works OK now.
> 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
[jira] Resolved: (QPID-2170) Enqueuing a durable message with SQL
persistence provider loaded throws 501 exception
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ 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
[jira] Updated: (QPID-2170) Declaring durable bindings with SQL
persistence provider loaded causes broker to close connection
Posted by "James Birdsall (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Birdsall updated QPID-2170:
---------------------------------
Attachment: issue3-server-disconnect.txt
Trace on the server up to the disconnect is attached.
> 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:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-2170) Declaring durable bindings with SQL
persistence provider loaded causes broker to close connection
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ 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:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-2170) Enqueuing a durable message with SQL
persistence provider loaded throws 501 exception
Posted by "Steve Huston (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Huston updated QPID-2170:
-------------------------------
Assignee: Steve Huston
Summary: Enqueuing a durable message with SQL persistence provider loaded throws 501 exception (was: Declaring durable bindings with SQL persistence provider loaded causes broker to close connection )
> 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
[jira] Commented: (QPID-2170) Declaring durable bindings with SQL
persistence provider loaded causes broker to close connection
Posted by "James Birdsall (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772209#action_12772209 ]
James Birdsall commented on QPID-2170:
--------------------------------------
Still seeing this problem, doesn't seem to have been affected by the fix.
> 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:dev-subscribe@qpid.apache.org