Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-3763

Use configurable time margin for checking offset between database server and broker

Rank to TopRank to BottomBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 2.21.0
    • 2.27.0
    • Configuration
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            marmueller Marlon Müller
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 5h 10m
                5h 10m

                Slack

                  Issue deployment