Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1444
@clebertsuconic
> The burst cannot complete in less than the timeout.. otherwise the timed
buffer is not timing...
A burst can complete in less than a timeout (reading the callback calls in
the test) but a new one can be accepted only when the timeout will be expired:
that's what a sanity test should verify IMHO.
Logging the different states of the TimedBuffer in the old and the new
version help to understand this little difference.
Reverting it would make it a step back from the correctness point of view
IMHO and features equality between NIO/MAPPED/ASYNCIO, because now (after the
last change you suggested me) it is really timing with the correct timeout...
@mtaylor @michaelandrepearce have worked around these code paths too,
wdyt?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
