The JMS bridge service in Message Queue 4.4 closes this gap by enablingĪ Message Queue broker to map its destinations to destinations in external This situation has led to non-interoperability This section describes the new features includedīecause the JMS specification does not define a wire protocol for communicationīetween brokers and clients, each JMS provider (including Message Queue) hasĭefined and uses its own propriety protocol. Message Queue 4.4 is a minor release that includes a number of featureĮnhancements and bug fixes. For more information, see Chapter 6, Embedding a Message Queue Broker in a Java Client, in Oracle GlassFish Message Queue 4.4.2 Developer’s Guide for Java Clients. Such a broker, called an in-process or embedded broker, runs in the same JVM as the Java client that createsĪnd starts it. Message Queue 4.4 Update 1 supports running a broker from Provides other features as well, as described in Optimizing File-Based Transaction Persistence in Oracle GlassFish Message Queue 4.4.2 Administration Guide. Mechanism for file-based data stores that supports broker clusters. Message Queue 4.4 Update 1 adds a transaction persistence For information about this installer, see Sun GlassFish Message Queue 4.4 Update 1 Installation Guide. Message Queue 4.4 Update 1 provides a new multiplatform installerīased on the pkq(5) system, also known as IPS or Image Message Queue 4.4 Update 1 is a minor release that includesĪ number of feature enhancements and bug fixes. New Features in Message Queue 4.4 Update 1 The new features in previous releases of the Message Queue 4 family New Features in Previous Message Queue 4 Releases
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |