. . . . . . . . . . . . . . . . . . . . . . . . 36 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 10. Using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 59.11. Memory usage from Paged Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

. . . . . . . . . . . . . . . . . . . . . . . . 36 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 10. Using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 58.11. Memory usage from Paged Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . messages there are --> However, the MQTT session meta-data is still present in memory and needs to be cleaned up as well. The URL parameter defaultMqttSessionExpiryInterval can be configured

. . . . . . . . . . . . . . . . . . . . . . . . 36 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 10. Using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 58.11. Memory usage from Paged Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . messages there are --> However, the MQTT session meta-data is still present in memory and needs to be cleaned up as well. The URL parameter defaultMqttSessionExpiryInterval can be configured

. . . . . . . . . . . . . . . . . . . . . . . . 36 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 10. Using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361 58.11. Memory usage from Paged Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . messages there are --> However, the MQTT session meta-data is still present in memory and needs to be cleaned up as well. The URL parameter defaultMqttSessionExpiryInterval can be configured

--global-max-size Maximum amount of memory which message data may consume (Default: Undefined, half of the system's memory) --home Directory where Apache ActiveMQ Artemis runs in a maximum of 1GiB of RAM. To increase the memory settings change the -Xms and -Xmx memory settings as you would for any Java program. If you wish to add any more JVM ------- [INFO] Total time: 7.840 s [INFO] Finished at: 2015-09-01T17:30:27-04:00 [INFO] Final Memory: 42M/508M [INFO] ------------------------------------------------------------------------ List

. . . . . . . . . . . . . . . . . . . . . . . . 37 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. Using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 59.11. Memory usage from Paged Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

. . . . . . . . . . . . . . . . . . . . . . . . 37 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. Using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 59.11. Memory usage from Paged Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

. . . . . . . . . . . . . . . . . . . . . . . . 37 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. Using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 59.11. Memory usage from Paged Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

. . . . . . . . . . . . . . . . . . . . . . . . 37 9.4. Virtual Topic Consumer Destination Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 10. Using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 59.11. Memory usage from Paged Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

--global-max-size Maximum amount of memory which message data may consume (Default: Undefined, half of the system's memory) --home Directory where Apache ActiveMQ Artemis runs in a maximum of 1GiB of RAM. To increase the memory settings change the -Xms and -Xmx memory settings as you would for any Java program. If you wish to add any more JVM true;suppressInternalManageme ntObjects=false Virtual Topic Consumer Destination Translation For existing OpenWire consumers of virtual topic destinations it is possible to configure a mapping