Bug 698254 - Fix bug in Cluster::timerDrop - calling wrong function
Summary: Fix bug in Cluster::timerDrop - calling wrong function
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: beta
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 2.2
: ---
Assignee: Alan Conway
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks: 716266
TreeView+ depends on / blocked
 
Reported: 2011-04-20 14:18 UTC by Alan Conway
Modified: 2013-02-24 14:39 UTC (History)
4 users (show)

Fixed In Version: qpid-cpp-server-0.14
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 716266 (view as bug list)
Environment:
Last Closed: 2012-12-10 22:26:54 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Alan Conway 2011-04-20 14:18:30 UTC 
Description of problem: clustered broker loops sending "TimerDrop" messages

Version-Release number of selected component (if applicable): 1.3

How reproducible:

No know reproducer, seen in logs from bug 684783. By inspection of the code the problem and the fix are obvious and trivial.
Comment 1 Alan Conway 2011-04-20 14:24:35 UTC 
Fixed upstream r1089953
Comment 3 Frantisek Reznicek 2011-07-08 07:08:34 UTC 
One clarification needed for QA needed.
What exactly is the token in bug 684783's qpidd log files which indicates usage of wrong function? (egrep -i 'timer|drop|timerdrop' did not find anything related for me)
Code inspection is obvious and will be done.
Note You need to log in before you can comment on or make changes to this bug.