# Versions

This chapter provides the information for each release:

- A link to the full release notes which includes all issues resolved in the release.
- A brief list of "highlights."
- 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.5.0

Full release notes.

Highlights:

- Exclusive consumers.
- Equivalent ActiveMQ 5.x Virtual Topic naming abilities.
- SSL Certificate revocation list.
- Last-value queue support for OpenWire.
- Support masked passwords in bootstrap.xm and login.config
- Configurable broker plugin implementation for logging various broker events (i.e. `LoggingActiveMQServerPlugin`).
- Option to use OpenSSL provider for Netty via the `sslProvider` URL parameter.
- Enable splitting of broker.xml into multiple files.
- Enhanced message count and size metrics for queues.

#### 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:

- JMX configuration via XML rather than having to use system properties via command line or start script.
- Configuration of max frame payload length for STOMP web-socket.
- Ability to configure HA using JDBC persistence.
- Implement role-based access control for management objects.

#### 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:

- Web admin console!
- Critical Analysis and deadlock detection on broker
- Support Netty native kqueue on Mac.
- Last-value queue for AMQP

#### 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:

- Scheduled messages with the STOMP protocol.
- Support for JNDIReferenceFactory and JNDIStorable.
- Ability to delete queues and addresses when broker.xml changes.
- Client authentication via Kerberos TLS Cipher Suites (RFC 2712).

## 2.1.0

Full release notes.

Highlights:

- Broker plugin support.
- Support Netty native epoll on Linux.
- Ability to configure arbitrary security role mappings.
- AMQP performance improvements.

## 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 ""