activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1326) testTimeOnTimedBuffer incorrect timeout count
Date Mon, 07 Aug 2017 14:59:00 GMT


ASF GitHub Bot commented on ARTEMIS-1326:

Github user clebertsuconic commented on the issue:
    the point of the TimedBuffer is to limit the writes you can send to storage at a limit....
you write once.. flush... next time you write it must be in the configured timing...
    the only reason why the flush could be flushed before time is if the buffer is full, and
that is currently contemplated... anything else will be sending more writes (and possibly
flushes) than what the device is capable of handling....
    again.. if Mapped works differently, then don't use TimedBuffer.. but you can't change
this semantic here.

> testTimeOnTimedBuffer incorrect timeout count
> ---------------------------------------------
>                 Key: ARTEMIS-1326
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
> The test isn't evaluating the timeout expiration while writing in batches into the TimedBuffer

This message was sent by Atlassian JIRA

View raw message