The following table describes the bugs fixed in Message Queue 4.3.
Table 1–9 Bugs Fixed in Message Queue 4. 3
Bug |
Description |
---|---|
6634033 |
Cluster protocol does not propagate value of imqConsumerFlowLimit to remote brokers when a client is created. |
6713012 |
Destruction of a consumer on a broker in a cluster at the same time that a remote broker is being restarted can result in some messages not being delivered. |
6727555 |
Broker log message "Max bytes per msg exceeded" has the actual message size and the max bytes per message values switched. |
6737404 |
JMX metrics need to provide counts of messages dispatched from destinations (topics and queues) but yet to be delivered to consumers. |
6740568 |
Broker throws an exception when consuming too many messages in a single transaction. |
6758524 |
The command to list durable subscriptions (imqcmd list dur -d "foo.*") does not accept wildcard characters in the destination name. |
6758952 |
Setting imq.portmapper.hostname=localhost causes brokers to be unable to connect into a cluster. |
6758817 |
Setting imq.cluster.hostname=localhost (not recommended) causes brokers on different machines to be unable to connect into a cluster. |