[jboss-jira] [JBoss JIRA] (WFLY-7405) Message counters doesn't work correctly without server reload after enabling statistics

[Jeff Mesnil (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-7405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil moved JBEAP-6700 to WFLY-7405:
------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-7405  (was: JBEAP-6700)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: JMS
                           (was: JMS)
                           (was: User Experience)
    Affects Version/s: 10.1.0.Final
                           (was: 7.1.0.DR7)


> Message counters doesn't work correctly without server reload after enabling statistics
> ---------------------------------------------------------------------------------------
>
>                 Key: WFLY-7405
>                 URL: https://issues.jboss.org/browse/WFLY-7405
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 10.1.0.Final
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>            Priority: Minor
>
> Server is started with queue deployed. Attribute {{statistics-enabled}} is then set to true in messaging server. This operation doesn't require reload. Start sending messages and look at outputs of operation {{list-message-counter-as-json}} or {{list-message-counter-as-html}} at queue you are using to send messages. ({{message-counter-sample-period}} is set to 10s by default, so give it some time).
> {code:title=list-message-counter-as-json output}
> [standalone at localhost:9990 jms-queue=q] :list-message-counter-as-json
> {
>     "outcome" => "success",
>     "result" => "{\"destinationName\":\"q\",\"destinationSubscription\":null,\"destinationDurable\":true,\"count\":0,\"countDelta\":0,\"messageCount\":47064,\"messageCountDelta\":809,\"lastAddTimestamp\":\"1/1/70 1:00:00 AM\",\"updateTimestamp\":\"1/1/70 1:00:00 AM\"}"
> }
> {code}
> Only attributes {{messageCount}}, {{messageCountDelta}} contain updated values . Other attributes are either null, 0 or default timestamp.
> Output of {{list-message-counter-history-as-json}} is also not correctly updated
> {code:title=list-message-counter-history-as-json output}
> [standalone at localhost:9990 jms-queue=q] :list-message-counter-history-as-json
> {
>     "outcome" => "success",
>     "result" => "{\"dayCounters\":[{\"date\":\"10/27/16\",\"counters\":[-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,0,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1]}]}"
> }
> {code}
> After server {{reload}}, output of operations updates and starts working as expected.
> {code:title=Output after reload}
> [standalone at localhost:9990 jms-queue=q] :list-message-counter-history-as-json
> {
>     "outcome" => "success",
>     "result" => "{\"dayCounters\":[{\"date\":\"10/27/16\",\"counters\":[-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,60015,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1]}]}"
> }
> [standalone at localhost:9990 jms-queue=q] :list-message-counter-as-json
> {
>     "outcome" => "success",
>     "result" => "{\"destinationName\":\"q\",\"destinationSubscription\":null,\"destinationDurable\":true,\"count\":60015,\"countDelta\":60015,\"messageCount\":60015,\"messageCountDelta\":60015,\"lastAddTimestamp\":\"10/27/16 11:34:39 AM\",\"updateTimestamp\":\"10/27/16 11:35:29 AM\"}"
> }
> {code}
> Values are also correctly updated when new messages are sent now.
> As administrator, I would like to be able to turn on/off statistics also without server reload. Although it is possible with messaging subsystem, it is not working correctly until reload.



--
This message was sent by Atlassian JIRA
(v7.2.2#72004)