You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2011/04/20 16:33:05 UTC
[jira] [Created] (QPID-3221) Fix bug in Cluster::timerDrop -
calling wrong function
Fix bug in Cluster::timerDrop - calling wrong function
------------------------------------------------------
Key: QPID-3221
URL: https://issues.apache.org/jira/browse/QPID-3221
Project: Qpid
Issue Type: Bug
Components: C++ Clustering
Affects Versions: 0.10
Reporter: Alan Conway
Assignee: Alan Conway
Fix For: 0.10
Fix obvious bug in Cluster::timerDrop, it calls the wrong function.
On one occassion this has been seen to cause a cluster broker to go into an infinite loop sending itself timer-drop messages.
There's no know way to reproduce but by inspection of the code the problem and the fix are obvious and trivial.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Commented] (QPID-3221) Fix bug in Cluster::timerDrop -
calling wrong function
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13022153#comment-13022153 ]
Alan Conway commented on QPID-3221:
-----------------------------------
Fixed on trunk r1089953
> Fix bug in Cluster::timerDrop - calling wrong function
> ------------------------------------------------------
>
> Key: QPID-3221
> URL: https://issues.apache.org/jira/browse/QPID-3221
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Affects Versions: 0.10
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.10
>
>
> Fix obvious bug in Cluster::timerDrop, it calls the wrong function.
> On one occassion this has been seen to cause a cluster broker to go into an infinite loop sending itself timer-drop messages.
> There's no know way to reproduce but by inspection of the code the problem and the fix are obvious and trivial.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] [Resolved] (QPID-3221) Fix bug in Cluster::timerDrop -
calling wrong function
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway resolved QPID-3221.
-------------------------------
Resolution: Fixed
> Fix bug in Cluster::timerDrop - calling wrong function
> ------------------------------------------------------
>
> Key: QPID-3221
> URL: https://issues.apache.org/jira/browse/QPID-3221
> Project: Qpid
> Issue Type: Bug
> Components: C++ Clustering
> Affects Versions: 0.10
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 0.10
>
>
> Fix obvious bug in Cluster::timerDrop, it calls the wrong function.
> On one occassion this has been seen to cause a cluster broker to go into an infinite loop sending itself timer-drop messages.
> There's no know way to reproduce but by inspection of the code the problem and the fix are obvious and trivial.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org