The following additional enhancements are included in Message Queue 4.3:
The installed directory structure for Message Queue on the Windows platform has been modified from previous versions to match that of the AIX platform. This directory structure will be adopted as well by the Solaris and Linux platforms in the future, to facilitate multiple installations on single computer and automatic update of Message Queue through Sun Connection, a Sun-hosted service that helps you track, organize, and maintain Sun hardware and software (see Installer Support for Sun Connection Registration).
The following new properties are available for configuring a broker:
Table 1–6 Broker Routing and Delivery Properties
Property |
Type |
Default Value |
Description |
---|---|---|---|
imq.transaction.producer.maxNumMsgs |
Integer |
1000 |
The maximum number of messages that a producer can process in a single transaction. It is recommended that the value be less than 5000 to prevent the exhausting of resources. |
imq.transaction.consumer.maxNumMsgs |
Integer |
100 |
The maximum number of messages that a consumer can process in a single transaction. It is recommended that the value be less than 1000 to prevent the exhausting of resources. |
imq.persist.jdbc.connection.limit |
Integer |
5 |
The maximum number of connections that can be opened to the database. |
A new attribute and composite data keys have been added to the JMX API as follows:
A NextMessageID attribute has been added to the Destination Monitor MBean to provide the JMS message ID of the next message to be delivered to a consumer.
A NextMessageID key for composite date has been added to the Consumer Manager Monitor MBean to provide the JMS message ID of the next message to be delivered to the consumer.
A NumMsgsPending key for composite date has been added to the Consumer Manager Monitor MBean to provide the number of messages that have been dispatched to the consumer.
For more information see Chapter 3, Message Queue MBean Reference, in Sun Java System Message Queue 4.3 Developer’s Guide for JMX Clients.
The command for listing durable subscriptions:
list dur [-d topicName]
has been enhanced to make specification of the topic name optional. If the topic is not specified, the command lists all durable subscriptions for all topics (including those with wildcard naming conventions)