server-side message load-balancing. 1.0.0 Full release notes. Highlights: First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a message to only one of the ANYCAST queues

load-balancing. 1.0.0 Full release notes. Highlights: Versions 15 First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a message to only one of the ANYCAST queues

load-balancing. 1.0.0 Versions 14 Full release notes. Highlights: First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a Address Model 51 message to only one

load-balancing. 1.0.0 Full release notes. Versions 11 Highlights: First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a message to only one of the ANYCAST queues

server-side message load-balancing. 1.0.0 Full release notes. Highlights: First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a Address Model 55 message to only one

server-side message load-balancing. 1.0.0 Full release notes. Highlights: First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a Address Model 55 message to only one

server-side message load-balancing. 1.0.0 Full release notes. Highlights: First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a message to only one of the ANYCAST queues

load-balancing. 1.0.0 Full release notes. Highlights: Address Federation 19 First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a message to only one of the ANYCAST queues

load-balancing. 1.0.0 Versions 19 Full release notes. Highlights: First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a message to only one of the ANYCAST queues

server-side message load-balancing. 1.0.0 Full release notes. Highlights: First release of the donated code-base as ActiveMQ Artemis! Lots of features for parity with ActiveMQ 5.x including: OpenWire support the client code, use both the address name and the queue name when requesting a connection from the broker. Remember to use two colons, :: , to separate the names, as in the example Java code below. String the example below, the acceptor is configured to use anycast:// for the anycastPrefix . Client code can specify anycast://foo/ if the client needs to send a message to only one of the ANYCAST queues