You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ken Giusti (JIRA)" <qp...@incubator.apache.org> on 2010/09/17 15:11:35 UTC
[jira] Created: (QPID-2862) QMF: python console should abort any
pending transactions when the broker is deleted.
QMF: python console should abort any pending transactions when the broker is deleted.
-------------------------------------------------------------------------------------
Key: QPID-2862
URL: https://issues.apache.org/jira/browse/QPID-2862
Project: Qpid
Issue Type: Improvement
Components: Qpid Managment Framework
Reporter: Ken Giusti
Assignee: Ken Giusti
Priority: Minor
In the current implementation, should the broker be deleted via delBroker, any pending transactions (getObjects(), method calls, etc) involving that broker remain in-flight until they time out. I think a better approach would be to abort these transactions by raising a "broker deleted" exception.
Also, I believe the same argument can be made in the case of an unexpected broker disconnect that occurs when managed connections are in use. I'd propose that the console should not only abort any pending transactions, but also delete all agents accessed via that broker.
Opinions?
--
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-2862) QMF: python console should abort any
pending transactions when the broker is deleted.
Posted by "Ken Giusti (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Giusti closed QPID-2862.
----------------------------
Fix Version/s: 0.7
Resolution: Fixed
Fixed: pending method calls and object queries will terminate immediately when the broker connection is lost/deleted.
> QMF: python console should abort any pending transactions when the broker is deleted.
> -------------------------------------------------------------------------------------
>
> Key: QPID-2862
> URL: https://issues.apache.org/jira/browse/QPID-2862
> Project: Qpid
> Issue Type: Improvement
> Components: Qpid Managment Framework
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Minor
> Fix For: 0.7
>
>
> In the current implementation, should the broker be deleted via delBroker, any pending transactions (getObjects(), method calls, etc) involving that broker remain in-flight until they time out. I think a better approach would be to abort these transactions by raising a "broker deleted" exception.
> Also, I believe the same argument can be made in the case of an unexpected broker disconnect that occurs when managed connections are in use. I'd propose that the console should not only abort any pending transactions, but also delete all agents accessed via that broker.
> Opinions?
--
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