Sun Java System Message Queue 4.1 Release Notes

Known Issues and Limitations

This section contains a list of the known issues with Message Queue 4.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.1.

Product Registry and JES

Version 4.1 of Message Queue is installed by a new installer, which also installs and upgrades the shared components that Message Queue needs; for example, JDK, NSS libraries, JavaHelp, and so on. This installer and the Java Enterprise System (JES) installer do not share the same product registry. If a version of Message Queue that was installed with JES is removed and upgraded to Message Queue 4.1 by the Message Queue installer, the JES product registry may be in an inconsistent state. As a result, when the JES uninstaller is run, it may inadvertently remove Message Queue 4.1 and the shared components upon which it depends, which it did not install.

The best way to upgrade software that was installed by the JES installer is as follows.

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

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

Selecting the Appropriate JRE

The Message Queue 4. 1 Installer JDK Selection Screen allows you to select existing JDK/JRE's on the system for use by Message Queue. Unfortunately, the list shown also includes the JRE used to run the installer application. This JRE is part of the installer bundle and is not really installed on the system. (Bug 6585911)

The JRE used by the installer is recognizable by its path, which should be within the unzipped installer directory and should include the subdirectory mq4_1–installer. For example:


Do not select this JRE for use by Message Queue. Instead, select another JDK on the system. If one does not exist, take the action appropriate for your platform.

Installing on Windows

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

Installing on Solaris

The error message and “incomplete” summary status misleads user trying to install using the installer-n command. The command actually succeeds. (Bug 6594351)

Installing on Linux

The following issues affect installation on the Linux Platform

Installing on All Platforms

These issues affect installation on all platforms.

Version Information

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

On the Solaris platform, refer to the table below to determine the version being installed.

Table 1–11 Version Formats

Version as Displayed by the Installer 

Message Queue Release 


3.7 UR1 

3.7 UR2 

3.7 UR3 


3.6 SP1 

3.6 SP2 

3.6 SP3 

3.6 SP4 

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.

On the Linux platform, it is not possible to provide a simple format translation. The version number displayed by the installer on Linux is in the following form.


For example, 3.7–22. This tells us that it is one of the 3.7 releases, but not which specific one. To determine that, 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. You must furnish passwords as follows.

  1. Set the password property to the desired value in a file used to store only passwords.

    Use the following syntax to specify passwords in the password file.


  2. Pass the name of the password file using the —passfile option.

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 to abracadabra.


You can configure the broker to use the password file you create in one of the following ways.

General Issues

This section covers general issues in Message Queue 4.1. Some of these were introduced with previous Message Queue versions.

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 clustered brokers.

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 ID 6393359).

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

Support for SOAP

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