. . . . . . . . . . . . . . . . . . . . . . . . 36 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 10. Using to be set to a power of 2, i.e.: 2, 16, 128 and so on. 9.4. Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping The security implementations of ActiveMQ "Classic" and Artemis don’t match perfectly so some translation must occur to achieve near equivalent functionality. Here is an example of the plugin’s configuration:

. . . . . . . . . . . . . . . . . . . . . . . . 36 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 10. Using to be set to a power of 2, i.e.: 2, 16, 128 and so on. 9.4. Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping The security implementations of ActiveMQ "Classic" and Artemis don’t match perfectly so some translation must occur to achieve near equivalent functionality. Here is an example of the plugin’s configuration:

. . . . . . . . . . . . . . . . . . . . . . . . 36 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 10. Using to be set to a power of 2, i.e.: 2, 16, 128 and so on. 9.4. Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping The security implementations of ActiveMQ "Classic" and Artemis don’t match perfectly so some translation must occur to achieve near equivalent functionality. Here is an example of the plugin’s configuration:

. . . . . . . . . . . . . . . . . . . . . . . . 36 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 10. Using to be set to a power of 2, i.e.: 2, 16, 128 and so on. 9.4. Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping The security implementations of ActiveMQ "Classic" and Artemis don’t match perfectly so some translation must occur to achieve near equivalent functionality. Here is an example of the plugin’s configuration:

possible. The security implementations of ActiveMQ 5.x and Artemis don't match perfectly so some translation must occur to achieve near equivalent functionality. Security 234 Here is an example of the createNonDurableQueue , deleteNonDurableQueue Security 236 As mentioned, there are a few places where a translation was performed to achieve some equivalence.: This mapping doesn't include the Artemis manage tAdvisory=true;suppressInternalManagementObjects=false Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping

. . . . . . . . . . . . . . . . . . . . . . . . 37 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. Using to be set to a power of 2, i.e.: 2, 16, 128 and so on. 9.4. Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping The security implementations of ActiveMQ "Classic" and Artemis don’t match perfectly so some translation must occur to achieve near equivalent functionality. Here is an example of the plugin’s configuration:

. . . . . . . . . . . . . . . . . . . . . . . . 37 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. Using to be set to a power of 2, i.e.: 2, 16, 128 and so on. 9.4. Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping The security implementations of ActiveMQ "Classic" and Artemis don’t match perfectly so some translation must occur to achieve near equivalent functionality. Here is an example of the plugin’s configuration:

. . . . . . . . . . . . . . . . . . . . . . . . 37 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. Using to be set to a power of 2, i.e.: 2, 16, 128 and so on. 9.4. Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping The security implementations of ActiveMQ "Classic" and Artemis don’t match perfectly so some translation must occur to achieve near equivalent functionality. Here is an example of the plugin’s configuration:

. . . . . . . . . . . . . . . . . . . . . . . . 37 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. Using to be set to a power of 2, i.e.: 2, 16, 128 and so on. 9.4. Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping The security implementations of ActiveMQ "Classic" and Artemis don’t match perfectly so some translation must occur to achieve near equivalent functionality. Here is an example of the plugin’s configuration:

true;suppressInternalManageme ntObjects=false Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping possible. The security implementations of ActiveMQ 5.x and Artemis don't match perfectly so some translation must occur to achieve near equivalent functionality. Here is an example of the plugin's configuration: createNonDurableQueue , deleteNonDurableQueue As mentioned, there are a few places where a translation was performed to achieve some equivalence.: This mapping doesn't include the Artemis manage