Known Issues and Limitations

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

• General Issues

• LDAP User Repository Properties

• Broker Clusters

• Administration/Configuration

• Broker Issues

• Documentation

• Installation Issues

For a list of current bugs, their status, and workaround, Java Developer Connection^SM members should see the Bug Parade page on the Java Developer Connection web site at http://bugs.sun.com/bugdatabase/index.jsp. 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.

Java Developer Connection membership is free but requires registration. For details about how to become a Java Developer Connection member, see the Sun’s “For Developers” web page.

To report a new bug or submit a feature request, send an email message to imq-feedback@sun.com.

General Issues

• A connection service using SSL is currently limited to supporting only self-signed server certificates, that is, host-trusted mode.

• When a JMS client using the HTTP transport terminates abruptly, for example, using Control-C, the broker takes approximately one minute before releasing the client connection and all the associated resources.

  If another instance of the client is started within the one-minute period that tries to use the same ClientID, durable subscription, or queue, a “Client ID is already in use” exception might occur. This exception is just the side effect of the termination process described above. If the client is started after a delay of approximately one minute, no problem should occur.

LDAP User Repository Properties

In Message Queue 3.7 UR1, the example broker configuration for using an LDAP server as a user repository is provided in the comment area in the config.properties . The LDAP user repository example in the default.properties file has been commented out.

If you previously relied on any property value in the example LDAP user repository properties specified in the default.properties file, once you upgrade to Message Queue 3.7 UR1. your JMS application client will receive a security exception when attempting to create a JMS connection.

When your JMS client tries to make a connection to the Message Queue 3.7 UR1 broker, an error appears in the broker log and your JMS client receives the following exception:

SecurityException.
20/Aug/2004:11:16:41 PDT] ERROR [B4064]: Ldap repository ldap property
.uidattr not defined for authentication type 
basic:com.sun.messaging.jmq.auth.LoginException: 
[B4064]: Ldap repository ldap property .uidattr not defined 
for authentication type basic

Workaround Set the broker property imq.user_repository.ldap.uidattr following the instructions in Chapter 7, Managing Security, in Sun Java System Message Queue 3.7 UR1 Administration Guide.

Broker Clusters

The following items relate to the use of broker clusters.

• Only fully-connected broker clusters are supported in this release. Therefore, every broker in a cluster must communicate directly with every other broker in the cluster. If you are connecting brokers using the imqbrokerd -cluster command line argument, ensure that all brokers in the cluster are included.

• A client connected to a broker that is part of a cluster cannot currently use QueueBrowser to browse queues that are located on remote brokers in that cluster. The client can only browse the contents of queues that are located on the broker to which it is directly connected. The client may still send messages to any queue or consume messages from any queue on any broker in the cluster. The limitation only affects browsing.

• If a master broker is not used in a broker cluster, persistent information stored by a broker being added to the cluster is not propagated to other brokers in the cluster.

• In a broker cluster, a broker will queue messages to a remote connection that has not been started (Bug ID 4951010).

  WorkaroundThe messages will be received by the consumer once the connection is started. The messages will be redelivered to another consumer if the consumer’s connection is closed.

Administration/Configuration

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

• The imqadmin and imqobjmgr utilities throw an error when the CLASSPATH contains double quotes on Windows machines (Bug ID 5060769)

  Workaround You can ignore this error message. The broker correctly handles notifying consumers of any error. This error does not affect the reliability of the system.

• The -javahome option in all Solaris and Windows scripts does not work if the value provided contains a space (Bug ID 4683029).

  The javahome option is used by Message Queue commands and utilities to specify an alternate Java 2 compatible runtime to use. However, the path name to the alternate Java runtime must not contain spaces. For example:

  Windows: C:/jdk 1.4

  Solaris: /work/java 1.4

  Workaround Install the Java runtime at a location or path that does not contain spaces.

• The imqQueueBrowserMaxMessagesPerRetrieve attribute specifies the maximum number of messages that the client runtime retrieves at one time when browsing the contents of a queue destination. The client application will always get all the messages on the queue. Therefore, the imqQueueBrowserMaxMessagesPerRetrieve attribute affects how the queued messages are divided to be delivered to the client runtime, either in several smaller pieces orfewer large chunks. This attribute does not affect the total messages browsed. Changing the value of this attribute might affect performance, but it will not result in the client application getting a different amount of data (Bug ID 6387631).

Broker Issues

The following issues affect the Message Queue broker.

• HTTPS createQueueConnection occasionally throws an exception on Windows 2000. (Bug ID 4953348).

  Workaround Retry the connection.

• When using Control-C to shut down a broker, transactions might be cleaned up after store is closed (Bug ID 4934446).

  The broker might show the errors message “Store method accessed after the store is closed” if the broker is shut down while messages or transactions are processed.

  Workaround You can ignore this error message. The broker correctly handles notifying consumers of any error. This error does not affect the reliability of the system.

• Consumers are orphaned when a destination is destroyed (Bug ID 5060787).

  Active consumers are orphaned when a destination is destroyed. Once the consumers have been orphaned, they will no longer receive messages even if the destination is re-created.

  Workaround None.

• Message selection using JMSMessageID doesnot work (Bug ID 6196233).

  Change the selector from the following expression

  JMSMessageID = "ID:message-id-string"

  to the following expression

  JMSMessageID IN (’ID:message-id-string’, ’message-id-string’)

Documentation

Message Queue 3.7 UR1 does not include a stand-alone product. For this release, you must install Message Queue using the Java Enterprise System Installer. Consult the Sun Java System Installation Guide for instructions.

• Message Queue menu->Index shows incorrect locations for the product documentation URL and the Read Me First file Bug ID 6515574

  Description Older documentation is displayed when the user selects documentation from the Message Queue entry in the Windows Start menu.

  WorkaroundAccess the documentation from http://docs.sun.com/app/docs/coll/1307.2http://docs.sun.com/app/docs/coll/1307.2.

Installation Issues

• The Add/Remove Programs Control Panel lists Sun Java Enterprise System instead of Message Queue

• The file Config_MQ.txt contains incorrect information. The following items correct some of the errors:

  • The Configure Automatically and Configure Manually options are not available with Message Queue, and no option exists to set the Administrator password

  • The Configure Automatically option installs and starts the Message Queue Broker Windows service automatically.

  • The Configure Manually option enables you to install the Message Queue Broker without starting it as a Windows service.

• The error messages that appear when attempting to install on a disk without sufficient disk space are potentially confusing. For example, "Error: -1603 Fatal error during installation."

• mq/bin was not added to the path during installationBug ID 6515557

  DescriptionThe Message Queue executables can not be found from a Windows command prompt. For example, typing imqcmd will trigger the following error: 'imqcmd' is not recognized as an internal or external command, operable program or batch file.

  Workaround Edit the PATH variable to include install-MQ-directory/bin or run the applications from the install-MQ-directory/bin directory.

• Message Queue Install does not support automated installation of shared components.

  WorkaroundUse JDK version 1.6.0 (SOAP components in 1.6.0) or Install Application Server on Windows which will install SOAP shared components.