ENTMQCL-604 - Receiver name is not set when using the container.create_receiver() method

In earlier releases of the product, a flaw in the option processing of the container.create_receiver() method prevented the name option from taking effect.

In this release, the name option works as expected.

ENTMQCL-617 - Scheduling new work can starve out performing what has been scheduled before

In earlier releases of the product, frequent calls to schedule() could prevent the already-scheduled work from being processed.

In this release, the library ensures that the presence of excessive scheduled events cannot starve other events.

ENTMQCL-766 - connection:forced leads to JMSException even though reconnect is enabled

In earlier releases of the product, a client configured to reconnect raised an exception if there were messages sent, but not yet acknowledged, when a connection was lost.

In this release, a client configured to reconnect attempts to resend unacknowledged messages when a new connection is established.

ENTMQCL-690 - Container.schedule() fails if called from an event handler

In earlier releases of the product, the Container.schedule() method had no effect if it was called from inside a MessagingHandler callback function.

In this release, calling schedule() in an event handler works as expected.

ENTMQCL-707 - Credit is incremented on receipt of message instead of message acknowledgment

In earlier releases of the product, the client issued more message credit to the sender when a message was received, rather than when it was acknowledged.

In this release, the client issues more credit after the message is acknowledged.