Issues Fixed in RC1

• DISPATCH-10 - Add link-cost for route computation
• DISPATCH-194 - Move libqpid-dispatch.so out of /lib
• DISPATCH-201 - Initial release of management console
• DISPATCH-208 - Closest semantics forwards improperly in multi-router network
• DISPATCH-222 - For Dispatch 0.6 release move up the minimum required version of qpid proton to 0.12.0
• DISPATCH-238 - Need more documentation for qdstat output
• DISPATCH-242 - Add options to qdstat to display autoLinks and linkRoutes
• DISPATCH-261 - Bind error on one port causes bind error on other ports
• DISPATCH-272 - Re-enable the connection cross-section popup
• DISPATCH-273 - The entity view is missing information for some entities
• DISPATCH-275 - Prevent javascript alert errors when navigating to console from a bookmark
• DISPATCH-278 - Deleting amqp listener using qdmanage crashes the router
  DISPATCH-279 - Policy crash when application name is null 
• DISPATCH-281 - Hostname not sent in open frame on connectors
• DISPATCH-282 - Prevent topology updates when adding a new router node
• DISPATCH-283 - Start the overview page with the Router tree node expanded
• DISPATCH-284 - The management schema no longer exposes a way to associate links with their connections
• DISPATCH-285 - qdmanage returns an empty list when you QUERY for certain entities
• DISPATCH-286 - Prefix delimiters: allow slashes as well as periods
• DISPATCH-287 - Policy does not allow configuration for unspecified Open hostname
• DISPATCH-288 - Driver - Wakeup pipe was seen to block on read, deadlocking the driver.
• DISPATCH-289 - Unit tests failing on Solaris
• DISPATCH-292 - some router.link attributes should be graphable
• DISPATCH-293 - The $ character can't be used inside a prefix for linkRoute
• DISPATCH-294 - Crash in the core-thread due to an address referencing a link on a closed connection
• DISPATCH-295 - Router aborted on assertion failed after socker closing by client
• DISPATCH-298 - router spinning on shutdown (in qdr_del_connection_ref)
• DISPATCH-299 - After policy rejects a connection queued Begin causes a crash
• DISPATCH-300 - Deprecate the ContainerEntity and move its attributes to RouterEntity
• DISPATCH-302 - Allow substitutable command line arguments when spawning console proxy
• DISPATCH-303 - Block all remote access to the "console" entity
• DISPATCH-304 - Console PNG images not showing up in documentation
• DISPATCH-305 - Don't tie inter-router flow credit to unsettled deliveries

Issues Fixed in Beta2

• DISPATCH-237 - Dispatch Router overwrites delivery tag for link-routed deliveries
• DISPATCH-245 - Various Bugs found by Coverity
• DISPATCH-254 - Router crash after several management requests
• DISPATCH-258 - Policy compile error - possible use of uninitialized variable
• DISPATCH-260 - Blank user names should use 'anonymous' instead
• DISPATCH-262 - oslo.messaging RPC fanout crashes qdrouterd
• DISPATCH-263 - Router crash when requesting log
• DISPATCH-264 - printf formats for 64-bit quantities need to be 64/32-bit safe
• DISPATCH-266 - memory leak allocating user_id fields
• DISPATCH-268 - Delivery from waypoint queue can stall when messages are released
• DISPATCH-271 - Handle single router (Console)
• DISPATCH-277 - Improve defaults for router configuration

Introduction

Apache Qpid Dispatch Router has undergone a significant update in internal architecture as of release 0.6.0.  The architectural change was necessary because the original architecture did not provide sufficient structure on which to implement some of the more advanced and desirable features.  Version 0.6.0 contains the following highlights:

• End-to-End Flow Control - Message producers attached to the Router are now subject to flow control across the router network.  If there are no available consumers for the sender's deliveries, the Router shall not issue credit.
• External Containers for terminating link-routes and for hosting waypoints (i.e. Brokers hosting queues and topics, etc.) can now be reached by listeners as well as connectors and can be identified either by the listener/connector or by the AMQP container-id of the attached process.
• Improved Link-Route Configuration - Link routes can now be controlled independently for receiving and sending links.  They can also be configured with a connector/listener/container-id that does not yet exist (i.e. no ordering constraints on configuring link-routes and their related containers).
• AutoLinks replace Waypoints - The Waypoint feature has been redesigned with simpler configuration and improved behavior.  This feature is now controlled using the newly introduced autoLink feature.  AutoLinks are manageable links whose lifecycle is controlled by the router as opposed to most other links whose lifecycles are controlled by the connected devices.
• Dynamic Control of connectors, listeners, linkRoutes, and autoLinks is now fully supported.  The Router can be provisioned dynamically using the AMQP management protocol and available tools.
• Forwarding Semantics Simplified - The old fanout and bias configuration for fixedAddress has been replaced by a single configuration for distribution.  Distribution values are:
  • Multicast - Each messages delivered once to each attached subscriber for an address.
  • Closest - Each message is delivered to only the closest attached subscriber.  This provides location affinity (i.e. use the service in my region if available).
  • Balanced - Messages are delivered to the attached subscriber with the fewest outstanding/unsettled deliveries.  This mechanism favors faster consumers over slower ones and will work well in situations where message-processing time is highly variable.
• Access Control - A new access control and resource usage limiting feature has been introduced in this version.
• x.509 Identity - Improved flexibility in identifying users via x.509 certificates is provided.  This identity can then be used to index into the access control policies.
• AMQP Heartbeats are now configurable in listeners and connectors.
• Protocol Family is now accessible in listeners and connectors to provide better control over the use of IPv4 and IPv6.
• Many Bugs Fixed

Backward Compatibility

Configuration files from earlier versions can be used in 0.6.0 with the following exceptions:

• fixedAddress for address "/" is no longer supported.  The default distribution is "balanced".
• fixedAddress entries for which there are phases are no longer supported.  This has been replaced by the boolean waypoint attribute in the address entity.
• waypoint entries are no longer supported.  This has been replaced by autoLink.
• Address prefixes: Addresses may be identified by prefix in address and linkRoute.  The prefix now has a delimiter of '.' (period).