Bug 698254

Summary:	Fix bug in Cluster::timerDrop - calling wrong function
Product:	Red Hat Enterprise MRG	Reporter:	Alan Conway <aconway>
Component:	qpid-cpp	Assignee:	Alan Conway <aconway>
Status:	CLOSED CURRENTRELEASE	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	beta	CC:	freznice, iboverma, jross, tross
Target Milestone:	2.2
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	qpid-cpp-server-0.14	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	716266 (view as bug list)		Environment:
Last Closed:	2012-12-10 22:26:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	716266

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.