...

It lists major features only.

...

Release

...

v7.

...

0

(Scheduled for release Q3 2016Q4 2017)

Qpid Broker for Java

...

1. Support for configured object queries using JMS selector style expressions – allows an operator to better understand a Broker's operation (e.g. show me queue depths for all queues on this virtualhost).
2. Web Management Console extension to allow queries to be edited/saved/retrieved and simple dashboards (comprising one or more saved queries)
3. Ability to persist user-preferences at the Broker and Virtualhost level (for replication within a HA group)

...

1. Support for LDAP Groups (QPID-7116)
2. Allow ACLs to be applied at Virtualhost level (for replication within a HA group)
3. Caching of authentication results to reduce load on back end authentication providers (such as an LDAP Open Directory)

...

1. Implement UIs for End to End Encryption (QPID-7037/QPID-7036), OAuth2 ( QPID-7112 / QPID-7111 ) and Virtual Host Aliases (QPID-7110)
2. Improve UI performance when monitoring large deployments.

1. Targets Java 1.8
2. Mature the existing AMQP 1.0 layer (QPID-7531)
3. JMS v2.0 support
   1. Shared Subscriptions (QPID-7569/QPID-7540/QPID-3953)
   2. Delivery Delay (QPID-7568)
   3. Maximum Delivery Count/Dead-lettering (QPID-7603)
   4. Consumer Priority for AMQP 1.0 (Broker support already in place, but Qpid JMS Client lacks the ability to allow properties to be set on link established). (deferred for future release)
   5. Arrival Time Filtering for AMQP 1.0 (QPID-7604) (deferred for future release)
   6. Producer Flow Control (QPID-7529)
   7. Client ID validation (QPID-7605)
   8. System test suite refactored to operate against both Qpid JMS Client and Legacy Client.
      1. There will need to be provision for some tests to be JMS 2.0 only.  How will this be handled (separate module?)
4. Mature the message conversation layer between protocols (QPID-7434)
   1. Fidelity with application headers (need rules around handling of long names, names containing illegal characters or values outside the domain permitted)
   2. Fidelity application payloads including structured payloads (lists/maps etc)
   3. Reply-to conversion supporting request/response across protocol (QPID-7602)
5. VH-centric REST API and VH-centric web management console (the former included, the latter deferred for future release) 
6. Simple REST API compatibility layer (deferred)
7. 'Queue runner' removal - not user facing -  simplifies threading model behind message delivery to queues within the Broker.
8. Model change to remove the requirement for multi-parents (QPID-6028) - not user facing - simplifies the object model underpinning the Broker.
   
   

...

Release v7.1

(Scheduled for release Q3/4 2017)

Qpid Broker for Java

• Replacement for the BDB JE based store with a store offering similar performance characteristics.
• ACL provider replacement
  
  

...

Minor Releases

Release v6.0.7

Not yet planned

Release v6.1.2

Not yet planned.

...

Release v6.2

Qpid Broker for Java

1. Extension to allow easy deployment of Brokers in 'common configurations profiles'
   1. This will allow a user to define one or more common configuration profiles used at deployment time to ensure that many Brokers are deployed in the same way to the same standard
   2. It is envisaged that this feature will be used to define 'hardened profiles' such as an "LDAP with TLS transport for messaging/management".
   3. This might involve some kind of manual configuration interrogation during first run ('give me your path to TLS cert' etc) and options  to integrate with systems such as Puppet.
2. Access Control
   1. New access control provider whose rules are associated with the configured objects themselves.
   2. UI fo the new access control provider.
   3. Define at a metalevel how permissions 'role-up' for instance a user with permission to consume and publish to queue might be consider to automatically have the move message permission,
   4. Define how permissions inherit 
3. Make user identity unique (QPID-7092)
4. Gracefully close TLS connections (QPID-6991)
5. Improve verification of the recipient's certificate used for Message Encryption (QPID-7309)
6. Impose absolute time limit on the WMC session 

Release v7.x

(2017)

Qpid Broker for Java

1. HTTP/AMQP on a single port for both secure and plain connections
2. Make the web management console a separately deployable .war
3. Virtualhost centric web management view
4. High performance message store support encryption at rest
5. Ability to Federate Java Brokers
6. REST API compatibility layer (QPID-6948)

7. Configured object creation tidy-up.

8. Message chunking / AMQP message segment capable store (QPID-6766)
9. Web Management Refresh (Angular??)
10. Embeddable Broker / Remove start-scripts.
    
    1. Better maven integration integration test support
11. Source tree: split Java Broker from Legacy AMQP 0-8..0-10 Client
12. Refactoring: Queue Runner Elimination

AMQP 0-8..0-10 Java Client

None

Minor Releases

Release v6.0.1

(Delivered Feb 2016 )

Java Broker

Defect fix release and minor enhancements to aid compatibility. 

Release v6.0.2

(Delivered Apr 2016)

Java Broker

Defect fix release

Release v6.0.3

(Delivered May 2016)

Release v6.0.4

(Delivered Jul 2016)

Release v6.0.5

(Delivery date not yet know)

JiraserverASF JIRAcolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionmaximumIssues20jqlQueryproject = 'Qpid' and fixVersion in ('qpid-java-6.0.5') and (resolution not in ('Invalid') or resolution is null) serverId5aa69414-a9e9-3523-82ec-879b028fb15b