You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Steven Shaw (JIRA)" <qp...@incubator.apache.org> on 2006/11/28 18:41:20 UTC
[jira] Created: (QPID-134) Revisit fail over
Revisit fail over
-----------------
Key: QPID-134
URL: http://issues.apache.org/jira/browse/QPID-134
Project: Qpid
Issue Type: Bug
Reporter: Steven Shaw
In reorganising the .NET Qpid.Messaging API the issue of fail over was neglected. Fail over needs to be revisited.
* record and replay necessary commands.
* Review new API methods for fail over requirements.
i.e. lock on mutex for non-blocking methods, FailoverSupport (for blocking methods)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (QPID-134) Revisit fail over
Posted by "Steven Shaw (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-134?page=all ]
Steven Shaw resolved QPID-134.
------------------------------
Resolution: Fixed
Except for perhaps the closing of sessions and consumers. If there's a problem there, we'll find it in the Java client too.
> Revisit fail over
> -----------------
>
> Key: QPID-134
> URL: http://issues.apache.org/jira/browse/QPID-134
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client
> Reporter: Steven Shaw
> Assigned To: Steven Shaw
>
> In reorganising the .NET Qpid.Messaging API the issue of fail over was neglected. Fail over needs to be revisited.
> * record and replay necessary commands.
> * Review new API methods for fail over requirements.
> i.e. lock on mutex for non-blocking methods, FailoverSupport (for blocking methods)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (QPID-134) Revisit fail over
Posted by "Steven Shaw (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-134?page=all ]
Steven Shaw reassigned QPID-134:
--------------------------------
Assignee: Steven Shaw
> Revisit fail over
> -----------------
>
> Key: QPID-134
> URL: http://issues.apache.org/jira/browse/QPID-134
> Project: Qpid
> Issue Type: Bug
> Reporter: Steven Shaw
> Assigned To: Steven Shaw
>
> In reorganising the .NET Qpid.Messaging API the issue of fail over was neglected. Fail over needs to be revisited.
> * record and replay necessary commands.
> * Review new API methods for fail over requirements.
> i.e. lock on mutex for non-blocking methods, FailoverSupport (for blocking methods)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (QPID-134) Revisit fail over
Posted by "Steven Shaw (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-134?page=all ]
Steven Shaw updated QPID-134:
-----------------------------
Component/s: Dot Net Client
> Revisit fail over
> -----------------
>
> Key: QPID-134
> URL: http://issues.apache.org/jira/browse/QPID-134
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client
> Reporter: Steven Shaw
> Assigned To: Steven Shaw
>
> In reorganising the .NET Qpid.Messaging API the issue of fail over was neglected. Fail over needs to be revisited.
> * record and replay necessary commands.
> * Review new API methods for fail over requirements.
> i.e. lock on mutex for non-blocking methods, FailoverSupport (for blocking methods)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira