The following table describes the bugs fixed in Message Queue 4.1.
Table 1–7 Bugs Fixed in Message Queue 4.1
Bug |
Description |
---|---|
6381703 |
Transacted remote messages can be committed twice if the broker originating the message restarts. |
6388049 |
Cannot clean up an uncompleted distributed transaction. |
6401169 |
The commit and rollback options for imqcmd do not prompt for confirmation. |
6473052 |
Default for autocreated queues should be round robin. (MaxNumberConsumers = -1). |
6474990 |
Broker log shows ConcurrentModificationException for imqcmd list dst command. |
6487413 |
Memory leak when limit behavior is REMOVE_OLDEST or REMOVE_LOWER_PRIORITY. |
6488340 |
Broker spins, and client waits for reply to acknowledge. |
6502744 |
Broker does not honor the dead message queue's default limit of 1000 messages. |
6517341 |
Client runtime needs to improve reconnect logic when the client is connected to a high-availability broker cluster by allowing the client to reconnect no matter what the value of the imqReconnectEnabled property is. |
6528736 |
Windows automatic startup service (imqbrokersvc) crashes during startup. |
6561494 |
Messages are delivered to the wrong consumer when both share a session. |
6567439 |
Produced messages in a PREPARED transaction are delivered out of order if they are committed after broker restarts. |