message body. AMQP 64 A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings

on the message body. A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings

message body. AMQP 74 A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings

message body. AMQP 69 A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings

message body. AMQP 69 A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings

message body. AMQP 71 A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings

message body. AMQP 73 A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings

message body. AMQP 66 A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings

message body. AMQP 67 A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings

message body. AMQP 74 A compatibility setting allows aligning the naming convention of AMQP queues (JMS Durable and Shared Subscriptions) with CORE. For backwards compatibility reasons, you need to explicitly in terms of bytes. ActiveMQ Artemis supports the activemq.prefetchSize header for backwards compatibility but the value will be interpreted as bytes just like consumer-window-size would be. If both number of database vendors (older versions may work but mileage may vary): 1. PostgreSQL 9.4.x 2. MySQL 5.7.x 3. Apache Derby 10.11.1.1 The JDBC store uses a JDBC connection to store messages and bindings