Github user franz1981 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1638
@clebertsuconic
> Instead of changing the semantic of flush, lets just avoid the bug...
this PR should be closed IMO.
I'm not sure about it TBH: help to understand why we can't check if `flush`
is being called for within the event loop?
It is a wrong use of it as you said and we can check/validate it with ease
(or at least we could log it as a warning/error) and without any perf impact. ---
