Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 52B71200D66 for ; Thu, 14 Dec 2017 15:48:34 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5032F160C01; Thu, 14 Dec 2017 14:48:34 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 986E4160C28 for ; Thu, 14 Dec 2017 15:48:30 +0100 (CET) Received: (qmail 39338 invoked by uid 500); 14 Dec 2017 14:48:29 -0000 Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list commits@activemq.apache.org Received: (qmail 38654 invoked by uid 99); 14 Dec 2017 14:48:28 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Dec 2017 14:48:28 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 6DE36F182A; Thu, 14 Dec 2017 14:48:27 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: dkulp@apache.org To: commits@activemq.apache.org Date: Thu, 14 Dec 2017 14:49:04 -0000 Message-Id: <6078f17a394e4e6d92a7888d5472f383@git.apache.org> In-Reply-To: <486425295cc046379393e9541a42f86e@git.apache.org> References: <486425295cc046379393e9541a42f86e@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [40/51] [abbrv] [partial] activemq-web git commit: Add body.storage type archived-at: Thu, 14 Dec 2017 14:48:34 -0000 http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/activemq-590-release.xml ---------------------------------------------------------------------- diff --git a/activemq-590-release.xml b/activemq-590-release.xml index 4e7e845..5ae6dd6 100644 --- a/activemq-590-release.xml +++ b/activemq-590-release.xml @@ -1,34 +1,9 @@ -
-

- - -

Apache ActiveMQ 5.9.0 resolves more than 200 issues, mostly bug fixes and improvements. It has the following new features:

  • Replicated LevelDB Store for shared nothing Master/Slave.
  • Runtime Configuration
  • Generic JMS XA connection pool in activemq-jms-pool module (has no ActiveMQ dependency)
  • MQTT over WebSockets support
  • broker Apache Camel component
  • Broker auto-restart upon losing master status
  • AMQP Hardening
  • LevelDB Hardening
There are some changes in 5.9 that may require user interventi on - -
  1. Schema change to JDBC Persistence Adapter. XID column type change.
-
  • If you use XA transactions you need to ensure there are no XA transactions pending completion before you upgrade. Some mode detail in AMQ-4628

Getting the Binary Distributions

Description

Download Link

PGP Signature file of download

Windows Distribution

apache-activemq-5.9.0-bin.zip

apache-activemq-5.9.0-bin.zip.asc

Unix/Linux/Cygwin Distribution

apache-activemq-5.9.0-bin.tar.gz

apache-activemq-5.9.0-bin.tar.gz.asc

Verify the Integrity of Downloads

It is essential that you verify the integrity of the download ed files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:

  1. Download the KEYS
  2. Download the asc signature file for the relevant distribution
  3. Verify the signatures using the following commands, depending on your use of PGP or GPG:

    - -

    or

    - -

    or

    - -

(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).

Alternatively, you can verify the MD5 signature on the files. A Unix program called md5 or md5sum is included in most Linux and Unix distributions. It is also available as part of GNU Textutils. Windows users can utilize any of the following md5 programs:

Getting the Binaries using Maven 2

To use this release in y our maven project, the proper dependency configuration that you should use in your Maven POM is:

- -
- - -

Getting the Source Code

Source Distributions

Description

Download Link

PGP Signature file of download

Source Release

activemq-parent-5.9.0-source-release.zip

activemq-parent-5.9.0-source-release.zip.asc

SVN Tag Checkout

- -

Changelog

For a more detailed view of new features and bug fixes, see the release notes

Also see the previous ActiveMQ 5.8.0 Release

+

Getting the Source Code

Source Distributions

Description

Download Link

PGP Signature file of download

Source Release

activemq-parent-5.9.0-source-release.zip

activemq-parent-5.9.0-source-release.zip.asc

SVN Tag Checkout

https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.9.0 +

Changelog

For a more detailed view of new features and bug fixes, see the release notes

Also see the previous

http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/activemq-591-release.xml ---------------------------------------------------------------------- diff --git a/activemq-591-release.xml b/activemq-591-release.xml index 8b86959..611bf97 100644 --- a/activemq-591-release.xml +++ b/activemq-591-release.xml @@ -1,34 +1,9 @@ -
-

- - -

Apache ActiveMQ 5.9.1 resolves more than 120 issues, mostly bug fixes and improvements. It has the following new features:

  • Replicated LevelDB Store for shared nothing Master/Slave.
  • Runtime Configuration
  • Generic JMS XA connection pool in activemq-jms-pool module (has no ActiveMQ dependency)
  • MQTT over WebSockets support
  • broker Apache Camel component
  • Broker auto-restart upon losing master status
  • AMQP Hardening
  • LevelDB Hardening
There are some changes in 5.9 that may require user interventi on - -
  1. Schema change to JDBC Persistence Adapter. XID column type change.
-
  • If you use XA transactions you need to ensure there are no XA transactions pending completion before you upgrade. Some mode detail in AMQ-4628

Note that the Hawtio console was removed in this release.

 

Getting the Binary Distributions

Description

Download Link

PGP Signature file of download

Windows Distribution

apache-activemq-5.9.1-bin.zip

apache-activemq-5.9.1-bin.zip.asc

Unix/Linux/Cygwin Distribution

apache-activemq-5.9.1-bin.tar.gz

apache-activemq-5.9.1-bin.tar.gz.asc

Verify the Integrity of Downloads

It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures. The PGP signatures can be verified using PGP or GPG. Begin by following these steps:

  1. Download the KEYS
  2. Download the asc signature file for the relevant distribution
  3. Verify the signatures using the following commands, depending on your use of PGP or GPG:

    - -

    or

    - -

    or

    - -

(Where <version> is replaced with the actual version, e.g., 5.1.0, 5.2.0, etc.).

Alternatively, you can verify the MD5 signature on the files. A Unix program called md5 or md5sum is included in most Linux and Unix distributions. It is also available as part of GNU Textutils. Windows users can utilize any of the following md5 programs:

Getting the Binaries using Maven 2

To use this release in y our maven project, the proper dependency configuration that you should use in your Maven POM is:

- -
- - -

Getting the Source Code

Source Distributions

Description

Download Link

PGP Signature file of download

Source Release

activemq-parent-5.9.1-source-release.zip

activemq-parent-5.9.1- source-release.zip.asc

SVN Tag Checkout

- -

Changelog

For a more detailed view of new features and bug fixes, see the release notes

Also see the previous ActiveMQ 5.8.0 Release

+

Getting the Source Code

Source Distributions

Description

Download Link

PGP Signature file of download

Source Release

activemq-parent-5.9.1-source-release.zip

activemq-parent-5.9.1-source-release.zip.asc

SVN Tag Checkout

https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=tag;h=refs/tags/activemq-5.9.1 +

Changelog

For a more detailed view of new features and bug fixes, see the release notes

Also see the previous

http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/activemq-artemis-roadmap.xml ---------------------------------------------------------------------- diff --git a/activemq-artemis-roadmap.xml b/activemq-artemis-roadmap.xml index b1c8735..f2e618f 100644 --- a/activemq-artemis-roadmap.xml +++ b/activemq-artemis-roadmap.xml @@ -1,58 +1,2 @@ -

The goal of this page is to identify the outstanding issues that must be addressed by Artemis in order to achieve some level of feature parity with ActiveMQ 5.x. The overall objective for working toward feature parity between ActiveMQ 5.x and Artemis is for Artemis to eventually become ActiveMQ 6.x. This page exists so that we can work together as a group to achieve this goal.

Work in Progress

This page is a work in progress and will be updated frequently.

Using this page

Feature items can be listed, with links to JIRA tickets for longer c onversation and hashing out specific feature details

Features/Scenarios

This section should be used to identify all the ActiveMQ 5.x features that Artemis needs. This should include all Artemis features that we can identify, including those from ActiveMQ that Artemis has already implemented. This will help us to more clearly track everything that Artemis needs.

 

Advisory Support

  • Support for broker state change advisories (master -> slave, slave -> master)
  • Support for connection advisories (connect, disconnect, unclean disconnect, authn fail, authz fail)
  • Support for consumer advisories (new consumer, closed, slow consumer)
  • Support for producer advisories (new producer, closed, fast producer, message size exceeded, memoryLimit reached, storage limit reached)
  • Support for destination advis ories (new dest, deleted)

Broker Clustering

  • Support full-duplex broker-to-broker cluster connections [ - - ARTEMIS-838 - - - Support full duplex cluster-connections - - Open - -]

ActiveMQ 5.x Client Compatibility

  • Full support of Openwire (TODO: specifically, which versions)

Destination Interceptors

  • Virtual Topic equivalent support [ - - ARTEMIS-550 - - - Add support for virtual topic consumers - - Open - -]

Destination Features

  • Destination Policy: Garbage collection and advisory support for that activity [ - - ARTEMIS-1148 - - - Artemis ServerPlugin support for Address changes - - Open - -]
  • Exclusive consumer support [ - - ARTEMIS-854 - - - Create basic exclusive consumer support within the broker - - Open - -]
  • Exclusive consumer features: consumersBeforeDispatchStarts, timeBeforeDispatchStarts [ - - ARTEMIS-856 - - - Support advanced exclusive consumer config options - - Open - -]

Plugin Support

  • Destination Policies (there is a slew of functionality in ActiveMQ 5.x dest policies that should be detailed out)

Storage Backend

  • Support for multiple shared persistence stores similar to multi-kahadb (allow for storage across multiple disk volumes.. ie.  queue://ORDER.> on /mnt/order queue://BILLING.> on /mnt/billing, etc) [ - - ARTEMIS-839 - - - Support multiple backend data stores - - Open - -]

Migration

This section should help to answer the end user question, 'How do I migrate from ActiveMQ 5.x to Artemis?'. This should include the identification of any tools that can help make this easier, as well as documenting information and procedures specific to migrating.

 

 

Wishlist

Protocol features

  • Exclusive consumer support across all protocols STOMP, MQTT, AMQP, etc. [ - - ARTEMIS-855 - - - Support exclusive consumer over non-JMS protocols - - Open - -]

KahaDB Migration Tool

  • Support exporting messages from KahaDB format to Artemis

Over-the-wire migration tool

  • Support a tool for migrating messages from ActiveMQ 5.x brokers to Artemis-based brokers (for non-standard backends)
    • Goal: preserve messageId
+

The goal of this page is to identify the outstanding issues that must be addressed by Artemis in order to achieve some level of feature parity with ActiveMQ 5.x. The overall objective for working toward feature parity between ActiveMQ 5.x and Artemis is for Artemis to eventually become ActiveMQ 6.x. This page exists so that we can work together as a group to achieve this goal.

Work in ProgressThis page is a work in progress and will be updated frequently.

Using this page

Feature items can be listed, with links to JIRA tickets for longer conversation and hashing out specific feature details

Features/Sc enarios

This section should be used to identify all the ActiveMQ 5.x features that Artemis needs. This should include all Artemis features that we can identify, including those from ActiveMQ that Artemis has already implemented. This will help us to more clearly track everything that Artemis needs.

 

Advisory Support

  • Support for broker state change advisories (master -> slave, slave -> master)
  • Support for connection advisories (connect, disconnect, unclean disconnect, authn fail, authz fail)
  • Support for consumer advisories (new consumer, closed, slow consumer)
  • Support for producer advisories (new producer, closed, fast producer, message size exceeded, memoryLimit reached, storage limit reached)
  • Support for destination advisories (new dest, deleted)

Broker Clustering

  • Support full-duplex broker-to-broker cluster connections [ASF JIRA5aa69414-a9e9-3523-82ec-879b028fb15bARTEMIS-838]

ActiveMQ 5.x Client Compatibility

  • Full support of Openwire (TODO: specifically, which versions)

Destination Interceptors

  • Virtual Topic equivalent support [ASF JIRA5aa69414-a9e9-3523-82ec-879b028fb15bARTEMIS-550]

Destination Features

  • Destination Policy: Garbage collection and advisory support for that activity [ASF JIRA5aa69414-a9e9-3523-82ec-879b028fb15bARTEMIS-1148]
  • Exclusive consumer support [ASF JIRA5aa69414-a9e9-3523-82ec-879b028fb15bARTEMIS-854]
  • Exclusive consumer features: consumersBeforeDispatchStarts, timeBeforeDispatchStarts [ASF JIRA5aa69414-a9e9-3523-82ec-879b028fb15bARTEMIS-856]

Plugin Support

  • Destination P olicies (there is a slew of functionality in ActiveMQ 5.x dest policies that should be detailed out)

Storage Backend

  • Support for multiple shared persistence stores similar to multi-kahadb (allow for storage across multiple disk volumes.. ie.  queue://ORDER.> on /mnt/order queue://BILLING.> on /mnt/billing, etc) [ASF JIRA5aa69414-a9e9-3523-82ec-879b028fb15bARTEMIS-839]

Migration

This section should help to answer the end user question, 'How do I migrate from ActiveMQ 5.x to Artemis?'. This should include the identification of any tools that can help make this easier, as well as documenting information and procedures specific to migrating.

 

 

Wish list

Protocol features

  • Exclusive consumer support across all protocols STOMP, MQTT, AMQP, etc. [ASF JIRA5aa69414-a9e9-3523-82ec-879b028fb15bARTEMIS-855]

KahaDB Migration Tool

  • Support exporting messages from KahaDB format to Artemis

Over-the-wire migration tool

  • Support a tool for migrating messages from ActiveMQ 5.x brokers to Artemis-based brokers (for non-standard backends)
    • Goal: preserve messageId
http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/activemq-c-clients.xml ---------------------------------------------------------------------- diff --git a/activemq-c-clients.xml b/activemq-c-clients.xml index 9e54bc3..c8e897f 100644 --- a/activemq-c-clients.xml +++ b/activemq-c-clients.xml @@ -1,4 +1,5 @@ -

ActiveMQ C++ Integration

+

ActiveMQ C++ Integration

-

CMS is an easy-to-use JMS 1.1-like API. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.

+

CMS is an easy-to-use JMS 1.1-like API. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.

+
http://git-wip-us.apache.org/repos/asf/activemq-web/blob/7a7d976c/activemq-c-development.xml ---------------------------------------------------------------------- diff --git a/activemq-c-development.xml b/activemq-c-development.xml index 9aa399e..fb86781 100644 --- a/activemq-c-development.xml +++ b/activemq-c-development.xml @@ -1,16 +1,16 @@ -

ActiveMQ CPP Development Page

+

ActiveMQ CPP Development Page

This page documents current and planned development of ActiveMQ CPP.  The table below lists development tasks and their current status

-

Development Activeity

Status

Openwire Support

in-progress

+

Development Activeity

Status

Openwire Support

in-progress

-

 Openwire Support

+

 Openwire Support

This task adds support for the OpenWire protocol to ActiveMQ CPP.  The tasks involves the addition of new code, the activities are listed below, as well as who is working on them and what the status of each is.

-

Task Description

Assigned to

Status

Task Info

Openwire Command / Marshallers generation scripts

Tim Bish

In-Progress

Loo se Marshalling works, Tight still not working

WireFormat Negotiation Framework

Tim Bish

Completed

Mimic the DotNet version?

Primitives Map

Nate Mittler

Completed

Needs more testing for memory leaks and performance.

Primitive Map Marshalling

Tim Bish

Completed

Needs more testing, for leaks etc.  Add nested maps, lists.

BaseDataStreamMarshallers Port

Tim Bish

In-Progress

Done, but serious unit testing is needed

BooleanStream Port

Tim Bish

Completed

Done

OpenWire Connector Framework Classes

Tim / Nate

Completed

Needs lots of testing

DataInputStreams / DataOutputStreams

Tim Bish

Completed

Done

+

Task Description

Assigned to

Status

Task Info

Openwire Command / Marshallers generation scripts

Tim Bish

In-Progress

Loose Marshalling works, Tight still not working

WireFormat Negotiation Framework

Tim Bish

Completed

Mimic the DotNet version?

Primitives Map

Nate Mittler

Completed

Needs more testing for memory leaks and performance.

Primitive Map Marshalling

Tim Bish

Completed

Needs more testing, for leaks etc.  Add nested maps, lists.

BaseDataStreamMarshallers Port

Tim Bish

In-Progress

Done, but serious unit testing is needed

BooleanStream Port

Tim Bish

Completed

Done

OpenWire Connector Framework Classes

Tim / Nate

Completed

Needs lots of testing

DataInputStreams / DataOutputStreams

Tim Bish

Completed

Done

-

Outstanding Issues

+

Outstanding Issues

This section document issues that are outstanding...TDB