. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 62.2. JDBC Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients, potentially on different physical broker connections. • MQTT subscription state is now persisted. • Significantly improved the Paging JDBC Persistence. • Converted much of the documentation from MarkDown to AsciiDoc. See ARTEMIS-4383 for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 61.2. JDBC Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients, potentially on different physical broker connections. • MQTT subscription state is now persisted. • Significantly improved the Paging JDBC Persistence. • Converted much of the documentation from MarkDown to AsciiDoc. See ARTEMIS-4383 for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 61.2. JDBC Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients, potentially on different physical broker connections. • MQTT subscription state is now persisted. • Significantly improved the Paging JDBC Persistence. • Converted much of the documentation from MarkDown to AsciiDoc. See ARTEMIS-4383 for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 61.2. JDBC Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients, potentially on different physical broker connections. • MQTT subscription state is now persisted. • Significantly improved the Paging JDBC Persistence. • Converted much of the documentation from MarkDown to AsciiDoc. See ARTEMIS-4383 for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 62.2. JDBC Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients, potentially on different physical broker connections. • MQTT subscription state is now persisted. • Significantly improved the Paging JDBC Persistence. • Converted much of the documentation from MarkDown to AsciiDoc. See ARTEMIS-4383 for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 62.2. JDBC Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients, potentially on different physical broker connections. • MQTT subscription state is now persisted. • Significantly improved the Paging JDBC Persistence. • Converted much of the documentation from MarkDown to AsciiDoc. See ARTEMIS-4383 for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 62.2. JDBC Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients, potentially on different physical broker connections. • MQTT subscription state is now persisted. • Significantly improved the Paging JDBC Persistence. • Converted much of the documentation from MarkDown to AsciiDoc. See ARTEMIS-4383 for

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 62.2. JDBC Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . performance, something not achievable when using a relational database for persistence (although JDBC is still an option if necessary). Apache ActiveMQ Artemis clients, potentially on different physical broker connections. • MQTT subscription state is now persisted. • Significantly improved the Paging JDBC Persistence. • Converted much of the documentation from MarkDown to AsciiDoc. See ARTEMIS-4383 for

management.xml use: 2. If you're using JDBC persistence then due to the changes in ARTEMIS-3679 you'll need to update your database. The column command-line option to transfer messages. Performance improvements for the wildcard address manager. JDBC datasource property values can now be masked. Lots of usability improvements to the Hawtio 2 based implementation that supports replication Consumer window size support for individual STOMP clients Improved JDBC connection management New web console based on Hawtio 2 Performance optimizations (i.e. caching)

management.xml use: 2. If you're using JDBC persistence then due to the changes in ARTEMIS- 3679 you'll need to update your database. The column command-line option to transfer messages. Performance improvements for the wildcard address manager. JDBC datasource property values can now be masked. Lots of usability improvements to the Hawtio 2 based implementation that supports replication Consumer window size support for individual STOMP clients Improved JDBC connection management New web console based on Hawtio 2 Performance optimizations (i.e. caching)