You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Marlon Müller (Jira)" <ji...@apache.org> on 2022/04/06 15:12:00 UTC

[jira] [Created] (ARTEMIS-3763) Use configurable time margin for checking offset between database server and broker

Marlon Müller created ARTEMIS-3763:
--------------------------------------

             Summary: Use configurable time margin for checking offset between database server and broker
                 Key: ARTEMIS-3763
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3763
             Project: ActiveMQ Artemis
          Issue Type: Improvement
          Components: Configuration
    Affects Versions: 2.21.0
            Reporter: Marlon Müller


When using JDBC persistence artemis checks for time differences between the broker and the database. Currently this check requests the time of the database and compares it to the system time before and after sending this query by removing the milliseconds and verifying that the database time is between the start and the end time. 
This leads to somehow random warnings in the log depending on the current milliseconds when this check is performed. 
For example if the time on your artemis server is 00:00:01.000 before the check and the time on the database is 00:00:00.999 it will log a warning although there is only 1 millisecond difference. On the other hand if your artemis server time is 00:00:01.000 after sending the query and the database time is 00:00:01.999 there will be no warning although the time is 999 milliseconds after the end time.
Therefore it would be better to use a consistent margin for the database time during this check. To avoid problems in setups where the system times are not well synchronized, this time margin should be configurable to allow the user to fine tune it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)