| Skip Navigation Links | |
| Exit Print View | |
|
Oracle GlassFish Server Message Queue 4.5 Release Notes |
Release Notes Revision History
Message Queue 4.5 Supported Platforms and Components
Bugs Fixed in Message Queue 4.5
Features to be Deprecated in a Future Release
Issues Related to the Next Major Release of Message Queue
Version Anomalies in the Installer
Administration/Configuration Issues
Documentation Updates in Message Queue 4.5
Accessibility of Code Examples in Documentation
Accessibility of Links to External Web Sites in Documentation
Deaf/Hard of Hearing Access to Oracle Support Services
New Features in Previous Message Queue 4 Releases
New Features in Message Queue 4.4.2
New Features in Message Queue 4.4 Update 1
Transaction Log Support for Clusters
New Features in Message Queue 4.4
New Universal Message Service (UMS) Functions
Audit Logging Feature Reinstated
New Features in Message Queue 4.3
Universal Message Service (UMS)
New Directory Structure on Windows Platform
JMX Administration API Enhancements
Listing Durable Subscriptions for Wildcard Subscribers
New Features in Message Queue 4.2
Multiple Destinations for a Publisher or Subscriber
Schema Validation of XML Payload Messages
C-API Support for Distributed Transactions
Installer Support for Sun Connection Registration
New Features in Message Queue 4.1
High-Availability Broker Clusters
Persistent Data Store Format Change
Broker Environment Configuration
Java ES Monitoring Framework Support
Enhanced Transaction Management
Fixed Ports for C Client Connections
New Features in Message Queue 4.0
Support for JMX Administration API
Connection Event Notification API
Broker Administration Enhancements
Displaying Information About a JDBC-Based Data Store
Persistent Data Store Format Changes
Bugs Fixed in Previous Message Queue 4 Releases
Bugs Fixed in Message Queue 4.4.2
Bugs Fixed in Message Queue 4.4 Update 1
Bugs Fixed in Message Queue 4.4
Bugs Fixed in Message Queue 4.3
Bugs Fixed in Message Queue 4.2
Message Queue 4.5 is an incremental release that includes a number of feature enhancements and bug fixes. Two of the most important features in this release relate to broker clusters, and another relates to consumer event notifications for Java clients:
This release introduces a new type of conventional cluster, the conventional cluster of peer brokers. Unlike a conventional cluster with a master broker, a conventional cluster of peer brokers maintains the cluster configuration change record in a shared JDBC data store instead of in the master broker. Thus, brokers can access cluster configuration information whether any other brokers in the cluster are running or not. For more information about conventional clusters of peer brokers, see Chapter 4, Broker Clusters, in Oracle GlassFish Server Message Queue 4.5 Technical Overview. For information about configuring and managing conventional clusters of peer brokers, see Chapter 10, Configuring and Managing Broker Clusters, in Oracle GlassFish Server Message Queue 4.5 Administration Guide.
Previously, to change the master broker in a conventional cluster from one broker to another, you had to stop all brokers, manually migrate the cluster configuration change record from the old master broker to the new one, and then start all brokers. This release provides the ability to change the master broker dynamically without stopping the cluster or performing manual migration tasks. For more information, see Changing the Master Broker in a Conventional Cluster with Master Broker in Oracle GlassFish Server Message Queue 4.5 Administration Guide.
This release introduces consumer event notifications for Java clients, which allow a Java client to listen for the existence of consumers on a destination. Thus, for example, a producer client can start or stop producing messages to a given destination based on the existence of consumers on the destination. For more information, see Consumer Event Notification in Oracle GlassFish Server Message Queue 4.5 Developer’s Guide for Java Clients.
|