[QPID-4717] QMF issue on exchange: update timestamp doesn't seem to be getting updated

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.21
• Fix Version/s: 0.22
• Component/s: C++ Broker
• Assignee: Ted Ross
• Reporter: Fraser Adams
• Created: 05/Apr/13 16:45
• Updated: 29/Jul/13 18:53
• Resolved: 05/Apr/13 17:48

Description

I've just noticed an issue with QMF2 statistics on trunk (0.23).

I'm pretty sure it didn't exist in 0.20 and below, but not sure about what's gone off to the 0.22 branch.

The issue is that exchange object update timestamps are not being updated. The objects in question definitely have statistics updates as I'm seeing changes to msgReceives and msgRoutes but each exchange now has an _update_ts that isn't getting updated when the statistics change.

This only seems to be affecting exchange objects, queue and connection objects still seem to be OK.

I noticed this when I pointed the GUI at qpidd 0.23 and tried to look at the graph for qmf.default.direct msgReceives, the graph wasn't updating despite the msgReceives value updating (the graph uses the actual timestamp to derive its x index).

I also tried adding console.log to display exchange._update_ts and I'm getting the same value each object update.

Any idea what might have changed?

I personally think this is a 0.22 blocker. It certainly prevents graphs of exchange statistics being displayed properly.