Broker Issues

The following issues affect the Message Queue broker.

• There has been some confusion about how to configure the broker for round-robin delivery. The solution is simple and configurable.

  1. Set the destination attribute maxNumActiveConsumers to -1. This turns on round-robin delivery.

  2. Set the destination attribute consumerFlowLimit to 1. This specifies the number of messages delivered to a single consumer before delivery progresses to the next consumer. For different chunking, set this attribute to the desired value. By default, one hundred messages are delivered to each consumer.

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