Sun Java System Message Queue 3.7 UR1 Release Notes

Bugs Fixed in This Release

Bugs Fixed in This Release describes the bugs fixed in Message Queue 3.7 UR1.

Table 1–4 Fixed Bugs in Message Queue 3.7 UR1

Bug Number 

Description  

6193884 

Message Queue outputs garbage message to syslog in locales that require non-ASCII characters to display messages. 

6251450 

ConcurrentModificationException on connectList during cluster shutdown.

6252763 

java.nio.BufferOverflowException in java.nio.HeapByteBuffer.putLong/Int.

6260076 

First message published after startup is slow with Oracle storage.  

6260814 

Selector processing on JMSXUserID always evaluates to false.

6264003 

The queue browser shows messages that are part of transactions that have not been committed. 

6271876 

Connection Flow Control does not work properly when closing a consumer with unconsumed messages. 

6284769 

The QueueBrowser leaks memory even when a new browser is created and closed for each enumeration. 

6294767 

Message Queue broker needs to set SO_REUSEADDR on the network sockets it opens.

6304043 

The broker does not validate that a clientID is not null for shared nondurable subscriptions.

6307056 

The txn log is a performance bottleneck.  

6320138 

Message Queue C API lacks ability to determine the name of a queue from a reply-to header.  

6320325 

The broker sometimes picks up JDK 1.4 before JDK 1.5 on Solaris even if both versions are installed.  

6321117 

Multi-broker cluster initialization throws java.lang.NullPointerException.

6330053 

The jms client runtime throws java.lang.NoClassDefFoundError when committing a transaction from the subscriber.

6340250 

Support MESSAGE type in C-API.

6351293 

Add Support for Derby database.  

6381693 

The JMSRedelivered flag is set to false for messages redelivered to a remote consumer after the consumer's broker restarts.

6388049 

Cannot clean up an incomplete XA transaction. 

6403968 

Add consumer-based flow control protocol to allow load balancing for multiple receivers 

6403958 

A broker exception is raised when the dead message queue tries to remove the oldest non-persistent message. 

6406862 

Not possible to monitor any destinations after broker error Monitor destination errormq.metrics.destination.queue.Name

6415068 

Transaction recovery fails in AS 8.1 UR2, generic resource adapter for JMS Message Queue. 

6421781 

Support connection to broker using the following syntax 

—b mqtcp://hostName:portNumber/serviceName

6423696 

Session.rollback does not actually roll back consumed messages after COMMIT REPLY error.