activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "metatech (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-4490) JDBCMessageStore fails to retrieve message after 200 messages when cache is disabled
Date Wed, 15 May 2013 10:11:16 GMT

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

metatech commented on AMQ-4490:
-------------------------------

Problem cannot be reproduced on 5.6, closing this ticket.
                
> JDBCMessageStore fails to retrieve message after 200 messages when cache is disabled
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-4490
>                 URL: https://issues.apache.org/jira/browse/AMQ-4490
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.5.1
>         Environment: ServiceMix 4.4.2
>            Reporter: metatech
>
> When trying to reproduce bug AMQ-4489, we found that the JDBCMessageStore fails to retrieve
all messages from the store when useCache="false".
> The existing unit test "JDBCMessagePriorityTest" reproduces it (see below).
> A similar problem occurs when MemoryLimit on the queue is used (which forces the messages
to be written to and later read from the JDBC message store).
> Can you please have a look ?
> -------------------------------------------------------------------------------
> Test set: org.apache.activemq.store.jdbc.JDBCMessagePriorityTest
> -------------------------------------------------------------------------------
> Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 12.94 sec <<<
FAILURE!
> testQueues {useCache=false}(org.apache.activemq.store.jdbc.JDBCMessagePriorityTest) 
Time elapsed: 6.656 sec  <<< FAILURE!
> junit.framework.AssertionFailedError: Message 200 was null
>  

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