dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability for admin objects in the JCA resource adapter to facilitate deployment into 3rd-party Java EE application servers Ability to prevent an acceptor from automatically starting Upgrading from older versions This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add:

0 码力 | 458 页 | 5.91 MB | 1 年前

3

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability 256 by default. 2.17.0 Full release notes. curl --user admin:admin --header "Content-Type: application/json" --reques Versions 11 Highlights: Message-level authorization similar to ActiveMQ 5.x for admin objects in the JCA resource adapter to facilitate deployment into 3rd-party Java EE application servers Ability to prevent an acceptor from automatically starting Upgrading from older versions

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability broker and acceptor names for your environment. curl --user admin:admin --header "Content-Type: application/json" --reques Versions 10 3. The "rate" metric for queues was removed from the web console for admin objects in the JCA resource adapter to facilitate deployment into 3rd-party Java EE application servers Ability to prevent an acceptor from automatically starting Upgrading from older versions

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability artifacts for Jakarta EE 8 & 9 respectively. 2.16.0 curl --user admin:admin --header "Content-Type: application/json" --reques Versions 12 Full release notes. Highlights: Configurable namespace for temporary for admin objects in the JCA resource adapter to facilitate deployment into 3rd-party Java EE application servers Ability to prevent an acceptor from automatically starting Upgrading from older versions

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability the web console, will have their return data curl --user admin:admin --header "Content-Type: application/json" --reques Versions 10 truncated by default. This is done to avoid adverse conditions with for admin objects in the JCA resource adapter to facilitate deployment into 3rd-party Java EE application servers Ability to prevent an acceptor from automatically starting Upgrading from older versions

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability the web console, will have their return data curl --user admin:admin --header "Content-Type: application/json" --reques Versions 10 truncated by default. This is done to avoid adverse conditions with for admin objects in the JCA resource adapter to facilitate deployment into 3rd-party Java EE application servers Ability to prevent an acceptor from automatically starting Upgrading from older versions

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability for admin objects in the JCA resource adapter to facilitate deployment into 3rd-party Java EE application servers Ability to prevent an acceptor from automatically starting Upgrading from older versions This is no longer required as the Jolokia REST interface is now integrated into the console web application. If the following is absent and you desire to deploy the web console then add: Versions 17

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability SLF4J- supporting logging implementation configured appropriately for their needs. See client application logging for more information plus an example around using Log4J 2. The broker distribution now queues will be based on the validated user rather than just the username submitted by the client application. This will impact use-cases like the following: i. When login.config is configured with the

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability SLF4J- supporting logging implementation configured appropriately for their needs. See client application logging for more information plus an example around using Log4J 2. The broker distribution now queues will be based on the validated user rather than just the username submitted by the client application. This will impact use-cases like the following: i. When login.config is configured with the

dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite Java EE application server, or run it embedded inside your own product. It's up to you. Seamless high availability SLF4J- supporting logging implementation configured appropriately for their needs. See client application logging for more information plus an example around using Log4J 2. The broker distribution now queues will be based on the validated user rather than just the username submitted by the client application. This will impact use-cases like the following: Versions 13 i. When login.config is configured