Sun GlassFish Message Queue 4.4 Update 1 Release Notes

Known Issues and Limitations

This section contains a list of the known issues with Message Queue 4.4 Update 1. The following product areas are covered:

For a list of current bugs, their status, and workarounds, Java Developer Connection™ members should see the Bug Parade page on the Java Developer Connection web site. Please check that page before you report a new bug. Although all Message Queue bugs are not listed, the page is a good starting place if you want to know whether a problem has been reported.

Note –

Java Developer Connection membership is free but requires registration. Details on how to become a Java Developer Connection member are provided on Sun’s “For Developers” web page.

To report a new bug or submit a feature request, send mail to

Installation Issues

This section describes issues related to the installation of Message Queue version 4.4 Update 1.

Product Registry and Java ES

Message Queue 4.4, like Message Queue 4.2 and 4.1, is installed by a relatively new installer, which also installs and upgrades the Java Enterprise System (Java ES) shared components required by Message Queue; for example, JDK, NSS, JavaHelp, and so on.

The new Message Queue installer and the older Java ES installer, which was used to install previous Message Queue versions, do not share the same product registry. If a version of Message Queue that was installed with the Java ES installer is removed and then Message Queue 4.4 is subsequently installed by the Message Queue installer, the Java ES product registry might be in an inconsistent state. As a result, if the Java ES uninstaller is run, it may inadvertently remove Message Queue 4.4 and the shared components upon which it depends, even though it did not install them.

The best way to upgrade Message Queue software that was installed by the Java ES installer is as follows.

  1. Use the Java ES uninstaller to remove Message Queue and its shared components.

  2. Use the Message Queue installer to install Message Queue 4.4.

Installing on All Platforms

These issues affect installation on all platforms.

Installing on Windows

When installing Message Queue on Windows, please note the following limitations.

Installing on Solaris

Installing on OpenSolaris

Installing on Linux

The following issues affect installation on the Linux Platform:

Version Anomalies in the Installer

The installer displays Message Queue version information in an opaque form. (Bug 6586507)

Solaris Platform

On the Solaris platform, refer to the following table to determine the Message Queue version displayed by the installer.

Table 1–13 Version String Translation

Version as Displayed by the Installer on Solaris OS 

Corresponding Message Queue Release 

4.4 Update 1 




4.1 Patch 2 

4.1 Patch 1 


3.7 UR2 Patch 1 

3.7 UR2 

3.7 UR1 


3.6 SP4 

3.6 SP3 

3.6 SP2 

3.6 SP1 

Note –

For Patch releases to 3.6 SP4 (for example, 3.6 SP4 Patch 1), the releases string displayed by the installer stays the same. You need to run the command imqbrokerd -version to determine the exact version.

Linux Platform

On the Linux platform, the version number displayed by the installer is in the following form.


For example, 3.7–22. This tells us only that this is one of the 3.7 releases, but not which specific one. To determine the installed Message Queue version, run the command:

imqbrokerd -version.

Localization Issues

The following issues relate to localization problems.

Deprecated Password Option

In previous versions of Message Queue, you could use the —p or —password option to specify a password interactively for the following commands: imqcmd, imqbrokerd, and imdbmgr. Beginning with version 4.0, these options have been deprecated.

Instead, you can create a password file that specifies the relevant passwords and reference the password file using the -passfile command option, or simply enter a password when prompted by the command.

A password file can contain one or more of the passwords listed below.

In the following example, the password to the JDBC database is set in the password file to abracadabra.


You can use a password file in one of the following ways.

Administration/Configuration Issues

The following issues pertain to administration and configuration of Message Queue.

Broker Issues

The following issues affect the Message Queue broker.

Broker Clusters

The following issues affect broker clusters.

JMX Issues

On the Windows platform, the getTransactionInfo method of the Transaction Manager Monitor MBean returns transaction information that has incorrect transaction creation time. (Bug 6393359)

Workaround: Use the getTransactionInfoByID method of the Transaction Manager Monitor MBean instead.

SOAP Support

You need to be aware of two issues related to SOAP support