activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-1966) Validate failing asserts w.r.t inFlight statistics in MasterSlaveTempQueueMemoryTest
Date Fri, 07 Dec 2012 23:23:21 GMT

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

Timothy Bish closed AMQ-1966.
-----------------------------

    Resolution: Won't Fix

Test doesn't exist anymore, so not a problem.
                
> Validate failing asserts w.r.t inFlight statistics in MasterSlaveTempQueueMemoryTest
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-1966
>                 URL: https://issues.apache.org/jira/browse/AMQ-1966
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Test Cases
>    Affects Versions: 5.2.0
>            Reporter: Gary Tully
>             Fix For: NEEDS_REVIEWED
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message