[
https://issues.apache.org/jira/browse/AMQ-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809335#comment-13809335
]
Claus Ibsen commented on AMQ-4354:
----------------------------------
Yes I am with Hiram, I think when the broker startup then its services such as
the datastores and whatnot, should ensure their JMX stats are "consistent'. eg
such as in your use-case, then the pending and enqueded would be set to the
same value.
And so forth.
Doing a full JMX persistent of state, seems like a general problem and outside
the scope.
And maybe doing this better "consistency" check on startup would also prevent
any of those, why is this counter negative we have had reported in the past.
> Persist JMX statistics so they survive a restart
> ------------------------------------------------
>
> Key: AMQ-4354
> URL: https://issues.apache.org/jira/browse/AMQ-4354
> Project: ActiveMQ
> Issue Type: New Feature
> Components: JMX
> Affects Versions: 5.8.0
> Environment: All
> Reporter: Matt Pavlovich
>
> It would be really handy if JMX statistics survived a restart.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
