Versions

This chapter provides the following information for each release:

  • A link to the full release notes which includes all issues resolved in the release.
  • A brief list of "highlights" when applicable.
  • If necessary, specific steps required when upgrading from the previous version.
    • Note: If the upgrade spans multiple versions then the steps from each version need to be followed in order.
    • Note: Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions outlined here.

2.11.0

Full release notes.

Highlights:

2.10.0

Full release notes.

This was mainly a bug-fix release with a notable dependency change impacting version upgrade.

Upgrading from 2.9.0

Due to the WildFly dependency upgrade the broker start scripts/configuration need to be adjusted after upgrading.

On *nix

Locate this statement in bin/artemis:

WILDFLY_COMMON="$ARTEMIS_HOME/lib/wildfly-common-1.5.1.Final.jar"

This needs to be replaced with this:

WILDFLY_COMMON="$ARTEMIS_HOME/lib/wildfly-common-1.5.2.Final.jar"
On Windows

Locate this part of JAVA_ARGS in etc/artemis.profile.cmd respectively bin/artemis-service.xml:

%ARTEMIS_HOME%\lib\wildfly-common-1.5.1.Final.jar

This needs to be replaced with this:

%ARTEMIS_HOME%\lib\wildfly-common-1.5.2.Final.jar

2.9.0

Full release notes.

This was a light release. It included a handful of bug fixes, a few improvements, and one major new feature.

Highlights:

2.8.1

Full release notes.

This was mainly a bug-fix release with a notable dependency change impacting version upgrade.

Upgrading from 2.8.0

Due to the dependency upgrade made on ARTEMIS-2319 the broker start scripts need to be adjusted after upgrading.

On *nix

Locate this if statement in bin/artemis:

if [ -z "$LOG_MANAGER" ] ; then
 # this is the one found when the server was created
 LOG_MANAGER="$ARTEMIS_HOME/lib/jboss-logmanager-2.0.3.Final.jar"
fi

This needs to be replaced with this block:

if [ -z "$LOG_MANAGER" ] ; then
 # this is the one found when the server was created
 LOG_MANAGER="$ARTEMIS_HOME/lib/jboss-logmanager-2.1.10.Final.jar"
fi

WILDFLY_COMMON=`ls $ARTEMIS_HOME/lib/wildfly-common*jar 2>/dev/null`
if [ -z "$WILDFLY_COMMON" ] ; then
 # this is the one found when the server was created
 WILDFLY_COMMON="$ARTEMIS_HOME/lib/wildfly-common-1.5.1.Final.jar"
fi

Notice that the jboss-logmanager version has changed and there is also a new wildfly-common library.

Not much further down there is this line:

-Xbootclasspath/a:"$LOG_MANAGER" \

This line should be changed to be:

-Xbootclasspath/a:"$LOG_MANAGER:$WILDFLY_COMMON" \
On Windows

Locate this part of JAVA_ARGS in etc/artemis.profile.cmd respectively bin/artemis-service.xml:

-Xbootclasspath/a:%ARTEMIS_HOME%\lib\jboss-logmanager-2.1.10.Final.jar

This needs to be replaced with this:

-Xbootclasspath/a:%ARTEMIS_HOME%\lib\jboss-logmanager-2.1.10.Final.jar;%ARTEMIS_HOME%\lib\wildfly-common-1.5.1.Final.jar

2.8.0

Full release notes.

Highlights:

2.7.0

Full release notes.

Highlights:

2.6.4

Full release notes.

This was mainly a bug-fix release with a few improvements a couple notable new features:

Highlights:

  • Added the ability to set the text message content on the producer CLI command.
  • Support reload logging configuration at runtime.

2.6.3

Full release notes.

This was mainly a bug-fix release with a few improvements but no substantial new features.

2.6.2

Full release notes.

This was a bug-fix release with no substantial new features or improvements.

2.6.1

Full release notes.

This was a bug-fix release with no substantial new features or improvements.

2.6.0

Full release notes.

Highlights:

2.5.0

Full release notes.

Highlights:

Upgrading from 2.4.0

  1. Due to changes from ARTEMIS-1644 any acceptor that needs to be compatible with HornetQ and/or Artemis 1.x clients needs to have anycastPrefix=jms.queue.;multicastPrefix=jms.topic. in the acceptor url. This prefix used to be configured automatically behind the scenes when the broker detected these old types of clients, but that broke certain use-cases with no possible work-around. See ARTEMIS-1644 for more details.

2.4.0

Full release notes.

Highlights:

Upgrading from 2.3.0

  1. Create <ARTEMIS_INSTANCE>/etc/management.xml. At the very least, the file must contain this:
    <management-context xmlns="http://activemq.org/schema"/>
    This configures role based authorisation for JMX. Read more in the Management documentation.

  2. If configured, remove the Jolokia war file from the web element in <ARTEMIS_INSTANCE>/etc/bootstrap.xml:

    <app url="jolokia" war="jolokia.war"/>

    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:

    <app url="console" war="console.war"/>

    Note: the Jolokia REST interface URL will now be at http://<host>:<port>/console/jolokia

2.3.0

Full release notes.

Highlights:

Upgrading from 2.2.0

  1. If you desire to deploy the web console then add the following to the web element in <ARTEMIS_INSTANCE>/etc/bootstrap.xml:
    <app url="console" war="console.war"/>

2.2.0

Full release notes.

Highlights:

2.1.0

Full release notes.

Highlights:

2.0.0

Full release notes.

Highlights:

  • Huge update involving a significant refactoring of the addressing model yielding the following benefits:
    • Simpler and more flexible XML configuration.
    • Support for additional messaging use-cases.
    • Eliminates confusing JMS-specific queue naming conventions (i.e. "jms.queue." & "jms.topic." prefixes).
  • Pure encoding of messages so protocols like AMQP don't need to convert messages to "core" format unless absolutely necessary.
  • "MAPPED" journal type for increased performance in certain use-cases.

1.5.6

Full release notes.

Highlights:

  • Bug fixes.

1.5.5

Full release notes.

Highlights:

  • Bug fixes.

1.5.4

Full release notes.

Highlights:

  • Support Oracle12C for JDBC persistence.
  • Bug fixes.

1.5.3

Full release notes.

Highlights:

  • Support "byte notation" (e.g. "K", "KB", "Gb", etc.) in broker XML configuration.
  • CLI command to recalculate disk sync times.
  • Bug fixes.

1.5.2

Full release notes.

Highlights:

  • Support for paging using JDBC.
  • Bug fixes.

1.5.1

Full release notes.

Highlights:

  • Support outgoing connections for AMQP.
  • Bug fixes.

1.5.0

Full release notes.

Highlights:

  • AMQP performance improvements.
  • JUnit rule implementation so messaging resources like brokers can be easily configured in tests.
  • Basic CDI integration.
  • Store user's password in hash form by default.

1.4.0

Full release notes.

Highlights:

  • "Global" limit for disk usage.
  • Detect and reload certain XML configuration changes at runtime.
  • MQTT interceptors.
  • Support adding/deleting queues via CLI.
  • New "browse" security permission for clients who only wish to look at messages.
  • Option to populate JMSXUserID.
  • "Dual authentication" support to authenticate SSL-based and non-SSL-based clients differently.

1.3.0

Full release notes.

Highlights:

  • Better support of OpenWire features (e.g. reconnect, producer flow-control, optimized acknowledgements)
  • SSL keystore reload at runtime.
  • Initial support for JDBC persistence.
  • Support scheduled messages on last-value queue.

1.2.0

Full release notes.

Highlights:

  • Improvements around performance
  • OSGi support.
  • Support functionality equivalent to all 5.x JAAS login modules including:
    • Properties file
    • LDAP
    • SSL certificate
    • "Guest"

1.1.0

Full release notes.

Highlights:

  • MQTT support.
  • The examples now use the CLI programmatically to create, start, stop, etc. servers reflecting real cases used in production.
  • CLI improvements. There are new tools to compact the journal and additional improvements to the user experience.
  • Configurable resource limits.
  • Ability to disable 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
    • AMQP 1.0 support
    • URL based connections
    • Auto-create addresses/queues
    • Jolokia integration

results matching ""

    No results matching ""