Chapter 3. Resolved Issues

ENTMQCL-584 - Kerberos authentication cannot proceed if the user option is not set

In earlier releases of the product, it was necessary to supply a value to the user connection option in order to use Kerberos authentication.

In this release, it is no longer necessary to set the user option.

ENTMQCL-565 - Windows build does not compile the examples that require C++11

In earlier releases of the product, compiling the C++11 examples was not supported on Windows.

In this release, the C++11 examples are supported on Windows.

ENTMQCL-600 - Epoll proactor pointer NULL in pn_connection_wake causes segmentation fault

In earlier releases of the product, it was possible for the pn_connection_wake operation to fail during reconnect and trigger a segmentation fault.

In this release, the operation no longer fails.

ENTMQCL-601 - Container continues to run after container.stop() called from main thread

In earlier releases of the product, the container.stop() operation failed when called before any connections were established.

In this release, the operation can safely be called before connecting.

ENTMQCL-571 - Missed connect error on start can lead to hung failover reconnect cycle

In earlier releases of the product, it was possible for the client to miss a connection error and hang during reconnect.

In this release, the client no longer hangs due to the missed error.

ENTMQCL-606 - Connection fails using Kerberos against Interconnect

In earlier releases of the product, the client did not handle an empty SASL challenge from AMQ Interconnect during Kerberos authentication. This prevented the client from establishing the connection.

In this release, the client handles the empty challenge, and the connection can be established.

ENTMQCL-620 - Application property keys are incorrectly encoded as AMQP binary

In earlier releases of the product, the client encoded the keys of message application properties as AMQP binary data. AMQP specifies that they be AMQP string data instead.

In this release, the keys are encoded as AMQP strings.

ENTMQCL-500 - Receive does not raise exception when link closed with error

In earlier releases of the product, it was possible for pipelined protocol state events to prevent the client from raising link errors to the API user.

In this release, the link errors are raised when the link is closed.