franz1981 commented on PR #4017: URL: https://github.com/apache/activemq-artemis/pull/4017#issuecomment-1097669161
hi @MM53 this looks similar to `maxAllowableDiffFromDBTime` in Classic ActiveMQ (see https://activemq.apache.org/pluggable-storage-lockers for more info): I agree that it could be useful, but dangerous as well, because if the difference specified exceed few milliseconds it can mask other problems (ie distance between broker and DBMS, lack of CPU time on both, misaligned clocks etc etc) that would prevent the feature to work as expected, anyway. > But the query causing the problem ("SELECT CURRENT_TIMESTAMP FROM ...") was not changed you should check the query that's actually used by your driver; I don't remember by heart if it's the right one TBH. In short, in order to have aligned clocks, the machines need to use NTP or other (better) mechanisms to be sure that broker <-> BDMS time is correctly aligned. JDBC is not meant to be used with machines too distant -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
