1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 1.33 1.34 Table of Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture address. An Apache ActiveMQ Artemis address can be configured with two different routing types. Table 1. Routing Types If you want your messages routed to... Use this routing type... A single queue 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

1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 1.33 1.34 Table of Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture address. An Apache ActiveMQ Artemis address can be configured with two different routing types. Table 1. Routing Types If you want your messages routed to... Use this routing type... A single queue message body. AMQP 63 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

Table of Contents 1. General Project Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Why use Apache ActiveMQ 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 activemq

19 1.19.1 1.19.2 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 Table of Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture have to stop any broker that is 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 [--jdbc-bindings-table-name ] [--jdbc-connection-url ] [--jdbc-driver-class-name ] [--jdbc-large-message-table-name ]

17 1.18 1.19 1.19.1 1.19.2 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 Table of Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture have to stop any broker that is 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 [--jdbc-bindings-table-name ] [--jdbc-connection-url ] [--jdbc-driver-class-name ] [--jdbc-large-message-table-name ]

17 1.18 1.19 1.19.1 1.19.2 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 Table of Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture stop any broker that is accessing 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 [--jdbc-bindings-table-name ] [--jdbc-connection-url ] [--jdbc-driver-class-name ] [--jdbc-large-message-table-name ]

17 1.18 1.19 1.19.1 1.19.2 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 Table of Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture have to stop any broker that is 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 [--jdbc-bindings-table-name ] [--jdbc-connection-url ] [--jdbc-driver-class-name ] [--jdbc-large-message-table-name ]

17 1.18 1.19 1.19.1 1.19.2 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 Table of Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture have to stop any broker that is 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 [--jdbc-bindings-table-name ] [--jdbc-connection-url ] [--jdbc-driver-class-name ] [--jdbc-large-message-table-name ]

1.17 1.18 1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 Table of Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture have to stop any broker that is 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 [--jdbc-bindings-table-name ] [--jdbc-connection-url ] [--jdbc-driver-class-name ] [--jdbc-large-message-table-name ]

1.19 1.20 1.21 1.22 1.23 1.24 1.25 1.26 1.27 1.28 1.29 1.30 1.31 1.32 1.33 1.34 Table of Contents Introduction Legal Notice Preface Project Info Versions Messaging Concepts Architecture [--jdbc-bindings-table-name ] [--jdbc-connection-url ] [--jdbc-driver-class-name ] [--jdbc-large-message-table-name ] [--jdbc-message-table-name ] [--jdbc-network-timeout ] [--jdbc-node-manager-table-name ]