Integration 52. Intercepting Operations 53. Protocols and Interoperability 54. Tools 55. Maven Plugin 56. Troubleshooting and Performance Tuning 57. Configuration Reference ActiveMQ Artemis Documentation embedded in your own project, or instantiated in any dependency injection framework such as Spring or Google Guice. Each Apache ActiveMQ Artemis server has its own ultra high performance persistent journal convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the

Integration 51. Intercepting Operations 52. Protocols and Interoperability 53. Tools 54. Maven Plugin 55. Troubleshooting and Performance Tuning 56. Configuration Reference ActiveMQ Artemis Documentation embedded in your own project, or instantiated in any dependency injection framework such as Spring or Google Guice. Each Apache ActiveMQ Artemis server has its own ultra high performance persistent journal convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the

Integration 51. Intercepting Operations 52. Protocols and Interoperability 53. Tools 54. Maven Plugin 55. Troubleshooting and Performance Tuning 56. Configuration Reference ActiveMQ Artemis Documentation embedded in your own project, or instantiated in any dependency injection framework such as Spring or Google Guice. Each Apache ActiveMQ Artemis server has its own ultra high performance persistent journal convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the

Intercepting Operations Protocols and Interoperability Tools 2 1.58 1.59 1.60 1.61 Maven Plugin Unit Testing Troubleshooting and Performance Tuning Configuration Reference 3 Apache ActiveMQ embedded in your own project, or instantiated in any dependency injection framework such as Spring or Google Guice. Each Apache ActiveMQ Artemis server has its own ultra high performance persistent journal convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the

Intercepting Operations Protocols and Interoperability Tools 2 1.58 1.59 1.60 1.61 Maven Plugin Unit Testing Troubleshooting and Performance Tuning Configuration Reference 3 Apache ActiveMQ embedded in your own project, or instantiated in any dependency injection framework such as Spring or Google Guice. Each Apache ActiveMQ Artemis server has its own ultra high performance persistent journal convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the

Integration CDI Integration Intercepting Operations Protocols and Interoperability Tools Maven Plugin 2 1.58 1.59 1.60 Unit Testing Troubleshooting and Performance Tuning Configuration Reference embedded in your own project, or instantiated in any dependency injection framework such as Spring or Google Guice. Each Apache ActiveMQ Artemis server has its own ultra high performance persistent journal convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the

Integration VertX Integration Intercepting Operations Protocols and Interoperability Tools Maven Plugin Troubleshooting and Performance Tuning 2 1.58 Configuration Reference 3 Apache ActiveMQ Artemis embedded in your own project, or instantiated in any dependency injection framework such as Spring or Google Guice. Each Apache ActiveMQ Artemis server has its own ultra high performance persistent journal convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the

Intercepting Operations Protocols and Interoperability Tools 2 1.58 1.59 1.60 1.61 Maven Plugin Unit Testing Troubleshooting and Performance Tuning Configuration Reference 3 Apache ActiveMQ embedded in your own project, or instantiated in any dependency injection framework such as Spring or Google Guice. Each Apache ActiveMQ Artemis server has its own ultra high performance persistent journal convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the

Integration CDI Integration Intercepting Operations Protocols and Interoperability Tools Maven Plugin Unit Testing Troubleshooting and Performance Tuning Configuration Reference 2 Apache ActiveMQ embedded in your own project, or instantiated in any dependency injection framework such as Spring or Google Guice. Each Apache ActiveMQ Artemis server has its own ultra high performance persistent journal convention, all JMS queues map to core queues where the core queue name has the string jms.queue. prepended to it. E.g. the JMS queue with the name "orders.europe" would map to the core queue with the

Intercepting Operations Protocols and Interoperability 2 1.58 1.59 1.60 1.61 1.62 1.63 Tools Maven Plugin Unit Testing Troubleshooting and Performance Tuning Configuration Reference Updating Artemis different: sudo route add 224.0.0.0 127.0.0.1 -netmask 240.0.0.0 All the examples use the Maven plugin, which can be useful for running your test servers as well. This is the common output when running maven-enforcer-plugin:1.4:enforce (enforce-java) @ queue --- [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ queue --- [INFO] [INFO] --- maven-resources-plugin:2.6:resources