You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/07/20 00:22:48 UTC

[jira] [Commented] (AMQ-4296) Unit tests fail intermittently when using LevelDB adapter

    [ https://issues.apache.org/jira/browse/AMQ-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714161#comment-13714161 ] 

Timothy Bish commented on AMQ-4296:
-----------------------------------

QueueBrowsingLevelDBTest is failing because the LevelDB store isn't using the Message incrementReferenceCount and decrementReferenceCount methods as KahaDB does so first three messages get added to the cursors batch list befire the memory usage exceeds the set value.  In the KahaDB versions of the test the usage exceeds the set value on send of the third message so it's not added to the Cursor's batch list and its usage drops after the store finishes its write so we can then page in one page worth of messages after the first two messages are sent to the browser.  
                
> Unit tests fail intermittently when using LevelDB adapter
> ---------------------------------------------------------
>
>                 Key: AMQ-4296
>                 URL: https://issues.apache.org/jira/browse/AMQ-4296
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Test Cases
>    Affects Versions: 5.8.0
>            Reporter: Timothy Bish
>            Priority: Minor
>             Fix For: 5.9.0
>
>         Attachments: AMQ-4415B.patch
>
>
> A couple of the unit tests that have be modified to run with LevelDB as the persistence adapter fail intermittently.
> AMQ2870Test
> AMQ2584Test#testSize
> DuranleSubscriptionOfflineTest#testConsumeOnlyMatchedMessages
> LevelDBXARecoveryBrokerTest#testTopicPersistentPreparedAcksAvailableAfterRestartAndRollback

--
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