Broker Issues

The following issues affect the Message Queue broker.

• The imqbrokerd —license command displays outdated or duplicate information. It displays information about the try license, even though this type of license is no longer supported (Bug ID 6489711) and it displays duplicate information about the unl license (Bug ID 6441015).

  Workaround These are cosmetic problems that require no workaround.

• The broker does not honor the default limit of 1000 messages for the dead message queue; it keeps adding messages to the dead message queue until the broker runs out of memory. (Bug ID 6502744)

  Workaround Reset the Dead Message Queue limit to 1001 or any value other than 1000.

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

  Workaround Retry the connection.

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

  The broker may show errors with the following reason “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.

• Broker becomes inaccessible when persistent store opens too many destinations. (Bug ID 4953354).

  Workaround This condition is caused by the broker reaching the system open-file descriptor limit. On Solaris and Linux use the ulimit command to increase the file descriptor limit.

• 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 recreated).

  Workaround There is no workaround for this problem.

• Message selection using JMSMessageID doesn’t work (Bug ID 6196233).

  Workaround 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’)

• Message Queue A queue browser shows uncommitted messages (Bug ID 6264003).

  When browsing the contents of a queue, messages that were produced in a transaction but are not yet committed may appear in the queue browser enumeration.

  Workaround There is no workaround for this problem.

• Messages may become unavailable after broker crashes during a commit (Bug ID 6467874).

  In very rare cases, during a broker crash, messages in a transaction may become unavailable to consumers. Specifically, there is a small window during Commit processing that may cause the message to become stuck in the persistent store. When this occurs, the following message is displayed at startup of the broker after a crash.

  [06/Sep/2006:10:11:11 PDT] ERROR [B2085]: 
     Loading Destination q0 [Queue] failed. 
     Messages stored on that destination will not be available.:
     > com.sun.messaging.jmq.jmsserver.util.BrokerException: 
    The message 8-129.145.180.87(b8:8b:26:15:41:26)-38998-1157562551217 
    has an associated acknowledgement list already. 

  Workaround There is no workaround for this problem.