the changes in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle) trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last getMessagesAdded() management methods and store the returned values along with the time they were retrieved. A time-series database is a great tool for this job. This is exactly what tools like Prometheus

trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last getMessagesAdded() management methods and store the returned values along with the time they were retrieved. A time-series database is a great tool for this job. This is exactly what tools like Prometheus course, one can skip all the tools and just do some simple math to calculate rates based on the last time the counts were retrieved. iii. Use the broker's message counters. Message counters are the broker's

trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last getMessagesAdded() management methods and store the returned values along with the time they were retrieved. A time-series database is a great tool for this job. This is exactly what tools like Prometheus course, one can skip all the tools and just do some simple math to calculate rates based on the last time the counts were retrieved. iii. Use the broker's message counters. Message counters are the broker's

Fixes AMQP Large Message over Bridges were broken Rollback of massive transactions would take a long time to process Improvements to auto-create and auto-delete queues. 2.27.0 Full release notes Highlights: the changes in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle) trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last

Fixes AMQP Large Message over Bridges were broken Rollback of massive transactions would take a long time to process Improvements to auto-create and auto-delete queues. 2.27.0 Full release notes Highlights: the changes in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle) trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last

Fixes AMQP Large Message over Bridges were broken Rollback of massive transactions would take a long time to process Improvements to auto-create and auto-delete queues. 2.27.0 Full release notes Highlights: the changes in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle) trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last

to the changes in ARTEMIS-3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle) trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last getMessagesAdded() management methods and store the returned values along with the time they were retrieved. A time-series database is a great tool for this job. This is exactly what tools like Prometheus

the changes in ARTEMIS- 3679 you'll need to update your database. The column HOLDER_EXPIRATION_TIME on the NODE_MANAGER_STORE changed from a TIMESTAMP to a BIGINT (or NUMBER(19) on Oracle) trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last getMessagesAdded() management methods and store the returned values along with the time they were retrieved. A time-series database is a great tool for this job. This is exactly what tools like Prometheus

trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last getMessagesAdded() management methods and store the returned values along with the time they were retrieved. A time-series database is a great tool for this job. This is exactly what tools like Prometheus course, one can skip all the tools and just do some simple math to calculate rates based on the last time the counts were retrieved. iii. Use the broker's message counters. Message counters are the broker's

trusted by a remote user as it only returns the number of message added to the queue since the last time it was called. The problem here is that the user calling it doesn't know when it was invoked last getMessagesAdded() management methods and store the returned values along with the time they were retrieved. A time-series database is a great tool for this job. This is exactly what tools like Prometheus course, one can skip all the tools and just do some simple math to calculate rates based on the last time the counts were retrieved. iii. Use the broker's message counters. Message counters are the broker's