Chapter 1. Fixed issues


1.1. AMQ JMS

  • ENTMQCL-2337 - Failure decoding large messages with special characters

    In earlier releases of the product, the client failed to decode messages containing multi-byte characters if the characters spanned transfer frames.

    In this release, large messages with multi-byte characters are correctly decoded.

  • ENTMQCL-2339 - The client can ignore transactions right after failover

    In earlier releases of the product, the client sometimes failed to mark a message transfer as belonging to a transaction directly after connection failover.

    In this release, transactions are correctly recovered after failover.

1.2. AMQ .NET

  • ENTMQCL-2241 - Client example sends empty begin frames

    In earlier releases of the product, the ReconnectSender example program sent an AMQP begin frame lacking required fields.

    In this release, the example correctly provides the mandatory fields.

1.3. AMQ C++

  • ENTMQCL-1863 - On receiving a forced close, send a corresponding protocol close and close the socket

    In earlier releases of the product, when the client received a forced AMQP connection close from the remote peer, it then closed its local TCP socket without sending a matching AMQP close in return.

    In this release, the client sends an AMQP close before closing the socket.

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.