[
https://issues.apache.org/jira/browse/QPID-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625543#comment-13625543
]
Justin Ross commented on QPID-4717:
-----------------------------------
Tested by Fraser. Approved for 0.22.
> QMF issue on exchange: update timestamp doesn't seem to be getting updated
> --------------------------------------------------------------------------
>
> Key: QPID-4717
> URL: https://issues.apache.org/jira/browse/QPID-4717
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.21
> Reporter: Fraser Adams
> Assignee: Ted Ross
> Priority: Blocker
> Fix For: 0.23
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
