Sun GlassFish Message Queue 4.4 Release Notes

Bugs Fixed in Message Queue 4.4 and Recent Releases

Message Queue 4.4 includes new bug fixes and also incorporates bugs that were fixed in the previous releases in the Message Queue 4.x family.

The following sections list bugs that were fixed in their respective releases:

Bugs Fixed in Message Queue 4.4

The following table describes the bugs fixed in Message Queue 4.4.

Table 1–7 Bugs Fixed in Message Queue 4.4

Bug 

Description 

6242247 

MQ cluster with masterbroker startup and hangs if both broker is on same machine have same name 

6760937 

Broker does not reconnect to the DB if it is restarted 

6765410 

masterbroker sends local interests 2 times cause slave exception Durable subscription already active 

6796506 

remote PREPARED msg not redelivered after rollback in case timeout in receiving remote PREPARE reply 

6821639 

NPE on rollback/commitTransaction during AS recovery for MQRA-DIRECT mode 

6836364 

wildcard subscriber does not receive remote msg if its topic is created before subscriber 

6836749 

HA(JCAPS):ack exists in store exception on receive after 1 of durables rollback then commit a msg 

6858905 

ConcurrentModificationException in Consumer.destroyConsumer 

Bugs Fixed in Message Queue 4.3

The following table describes the bugs fixed in Message Queue 4.3.

Table 1–8 Bugs Fixed in Message Queue 4. 3

Bug 

Description 

6634033 

Cluster protocol does not propagate value of imqConsumerFlowLimit to remote brokers when a client is created.

6713012 

Destruction of a consumer on a broker in a cluster at the same time that a remote broker is being restarted can result in some messages not being delivered. 

6727555 

Broker log message "Max bytes per msg exceeded" has the actual message size and the max bytes per message values switched.

6737404 

JMX metrics need to provide counts of messages dispatched from destinations (topics and queues) but yet to be delivered to consumers. 

6740568 

Broker throws an exception when consuming too many messages in a single transaction. 

6758524 

The command to list durable subscriptions (imqcmd list dur -d "foo.*") does not accept wildcard characters in the destination name.

6758952 

Setting imq.portmapper.hostname=localhost causes brokers to be unable to connect into a cluster.

6758817 

Setting imq.cluster.hostname=localhost (not recommended) causes brokers on different machines to be unable to connect into a cluster.

Bugs Fixed in Message Queue 4.2

The following table describes the bugs fixed in Message Queue 4.2.

Table 1–9 Bugs Fixed in Message Queue 4.2

Bug 

Description 

6581592 

When the installer or uninstaller is run in text mode (installer –t), the Summary screen shows the directory containing the log/summary files but does not list the names of these files.

6585911 

The installer's JDK Selection screen incorrectly includes the JRE bundled with the installer and used to run the installer. 

6587112 

The installer summary screen shows garbage in multi-byte locales. 

6587127 

When running the installer by referencing an answer file (installer -a filename -s), if the answer file does not exist, the error messages are inconsistent and unclear.

6590969 

Allows DN username format in client connection authentication. 

6594381 

Installation of Message Queue 4.1 localization RPM's (which happens when you select the “Install Message Queue multilingual packages” checkbox on the Multilingual Packages screen) will fail if older versions of Message Queue localization RPM's exist on your system. 

6599144 

When uninstalling Message Queue 4.2, splash screen and uninstaller hangs and screens appear empty and gray on Java SE 6, but work on Java SE 5.  

6615741 

Message delivered in a transacted consumer session that is rolled back is not redelivered if the original consumer closed before rollback. 

6629922 

Distributed transaction handler does not redeliver message to inactive consumer in correct order. 

6635130 

Broker fails to notify producer of non persistent messages to resume production after having been paused because destination had reached memory or message limits. 

6641117 

Message delivered in a transacted consumer session that is rolled back is not redelivered if the original consumer closed after rollback. 

6683897 

Message Queue installer's summary screen reports configuration error even though configuration appears to complete successfully: installer cannot write to /dev/sterr on some computers.

6684069 

In broker cluster in which large number of messages are delivered to remote client in consumer transaction, commit transaction fails. 

6688935 

Default value of Portmapper read timeout is too small. 

6695238 

C-client applications cannot connect to a broker installed in a location that has spaces in the path. 

6710168 

Consumer no longer consumes messages if destination is paused twice without being resumed between the pauses. 

6710169 

JMX operation ConsumerManagerMonitor.getConsumerInfo always returns SESSION_TRANSACTED for the acknowledgement mode.

Bugs Fixed in Message Queue 4.1

The following table describes the bugs fixed in Message Queue 4.1.

Table 1–10 Bugs Fixed in Message Queue 4.1

Bug 

Description 

6381703 

Transacted remote messages can be committed twice if the broker originating the message restarts. 

6388049 

Cannot clean up an uncompleted distributed transaction. 

6401169 

The commit and rollback options for imqcmd do not prompt for confirmation. 

6473052 

Default for autocreated queues should be round robin. (MaxNumberConsumers = -1).

6474990 

Broker log shows ConcurrentModificationException for imqcmd list dst command.

6487413 

Memory leak when limit behavior is REMOVE_OLDEST or REMOVE_LOWER_PRIORITY.

6488340 

Broker spins, and client waits for reply to acknowledge. 

6502744 

Broker does not honor the dead message queue's default limit of 1000 messages. 

6517341 

Client runtime needs to improve reconnect logic when the client is connected to an enhanced broker cluster by allowing the client to reconnect no matter what the value of the imqReconnectEnabled property is.

6528736 

Windows automatic startup service (imqbrokersvc) crashes during startup.

6561494 

Messages are delivered to the wrong consumer when both share a session. 

6567439 

Produced messages in a PREPARED transaction are delivered out of order if they are committed after broker restarts.

Bugs Fixed in Message Queue 4.0

The following table describes the bugs fixed in Message Queue 4.0.

Table 1–11 Bugs Fixed in Message Queue 4.0

Bug Number 

Description 

4986481 

In Message Queue 3.5, calling Session.recover could hang in auto-reconnect mode.

4987325 

Redelivered flag was set to false for redelivered messages after calling Session.recover.

6157073 

Change new connection message to include the number of connections on the service in addition to the total number of connections. 

6193884 

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

6196233 

Message selection using JMSMessageID doesn't work.

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. 

6279833 

Message Queue should not allow two brokers to use the same jdbc tables. 

6293053 

Master broker does not start up correctly if the system's IP address is changed, unless the store is cleared (using —reset store.)

6294767 

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

6304949 

Unable to set ClientID property for TopicConnectionFactory.

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 

Multibroker cluster initialization throws java.lang.NullPointerException.

6330053 

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

6340250 

Support MESSAGE type in C-API.

6351293 

Add Support for Apache Derby database.