[
https://issues.apache.org/jira/browse/ARTEMIS-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198714#comment-16198714
]
ASF GitHub Bot commented on ARTEMIS-1447:
-----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/1576
I'm not sure about it: it's similar to the TimedBuffer flusher thread.
It (they) needs to not being slowed down by anything in order to work as
expected and I've put
several checks that will be triggered otherwise.
If we have already something similar that I can reuse I will do it for
sure.
The only reason why we don't use Scheduled Executor at the Timedbuffer is
because we use NanoSeconds intervals.. what's not good for the Executor.
You already create a ScheduledExecutor... if you need your own executor,
still use the component which encapsulates that.. if you can reuse one from the
pool.. (It seems you can).. you can just pass in the argument.
> JDBC NodeManager to support JDBC HA Shared Store
> ------------------------------------------------
>
> Key: ARTEMIS-1447
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1447
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: Francesco Nigro
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
