you're using JDBC persistence then due 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 accessing that table and either drop it or execute the proper ALTER TABLE statement for your database. If you drop the table then it will be automatically recreated when broker restarts and repopulated 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 do. That data can then

you're using JDBC persistence then due 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 accessing that table and either drop it or execute the proper ALTER TABLE statement for your database. If you drop the table then it will be automatically recreated when broker restarts and repopulated 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 do. That data can then

you're using JDBC persistence then due 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 accessing that table and either drop it or execute the proper ALTER TABLE statement for your database. If you drop the table then it will be automatically recreated when broker restarts and repopulated 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 do. That data can then

you're using JDBC persistence then due 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 accessing that table and either drop it or execute the proper ALTER TABLE statement for your database. If you drop the table then it will be automatically recreated when broker restarts and repopulated 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 do. That data can then

fulfills the order, sends order information to the warehouse system and then updates the order database with the order details. Once it’s done that it acknowledges the message to tell the server that has been processed and can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACID properties. 3.2.2 allows outrageous persistence message performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients

fulfills the order, sends order information to the warehouse system and then updates the order database with the order details. Once it’s done that it acknowledges the message to tell the server that has been processed and can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACID properties. 3.2.2 allows outrageous persistence message performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients

fulfills the order, sends order information to the warehouse system and then updates the order database with the order details. Once it’s done that it acknowledges the message to tell the server that has been processed and can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACID properties. 3.2.2 allows outrageous persistence message performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients

fulfills the order, sends order information to the warehouse system and then updates the order database with the order details. Once it’s done that it acknowledges the message to tell the server that has been processed and can be forgotten about. Often the send to the warehouse system, update in database and acknowledgement will be completed in a single transaction to ensure ACID properties. 3.2.2 allows outrageous persistence message performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients

you're using JDBC persistence then due 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 that table and either drop it or execute the Versions 11 proper ALTER TABLE statement for your database. If you drop the table then it will be automatically recreated when broker restarts and repopulated 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 do. That data can then

you're using JDBC persistence then due 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 accessing that table and either drop it or execute the proper ALTER TABLE statement for your database. If you drop the table then it will be automatically recreated when broker restarts and repopulated 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 do. That data can then