[jira] Updated: (AMQ-1966) Validate failing asserts w.r.t inFlight statistics in MasterSlaveTempQueueMemoryTest

["Rob Davies (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies updated AMQ-1966:
----------------------------

    Fix Version/s: 5.4.0

> Validate failing asserts w.r.t inFlight statistics in MasterSlaveTempQueueMemoryTest
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-1966
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1966
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Test Cases
>    Affects Versions: 5.2.0
>            Reporter: Gary Tully
>             Fix For: 5.4.0
>
>
> activemq/trunk/activemq-core/src/test/java/org/apache/activemq/advisory/MasterSlaveTempQueueMemoryTest.java
> There are a few REVISITS in the test w.r.t asserts that should be valid. The slave should be an exact mirror of the master. 
> The questions posed in the comments need to be addressed.
> {code}
>         // REVISIT the following two are not dependable at the moment, off by a small number
>         // for some reason? The work for a COUNT < ~500
>         //
>         //assertEquals("inflight match", rb.getDestinationStatistics().getInflight().getCount(), masterRb.getDestinationStatistics().getInflight().getCount());
>         //assertEquals("enqueues match", rb.getDestinationStatistics().getEnqueues().getCount(), masterRb.getDestinationStatistics().getEnqueues().getCount());
> {code}
> {code}
>         // master does not always reach expected total, should be assertEquals.., why?
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.