All Products
Search
Document Center

ApsaraMQ for RocketMQ:Release notes for the TCP client SDK for C++

Last Updated:Mar 11, 2026

The following release notes cover all versions of the TCP client SDK for C++, including release dates, download links, and changes. Select a version that meets your business requirements to send and receive messages.

Before you begin

Set up your development environment after downloading the SDK:

Version compatibility

Important

SDK V3.x.x only supports instances that contain namespaces. If your instance does not contain a namespace, do not upgrade to V3.x.x.

All ApsaraMQ for RocketMQ 5.x instances contain namespaces by default. For ApsaraMQ for RocketMQ 4.x instances, check whether your instance contains a namespace in the Basic Information section of the Instance Details page in the ApsaraMQ for RocketMQ console.

V3.x.x

V3.x.x (2021-10-18)

Download: ons-client-cpp on GitHub

Note

For a full list of API changes in this release, see Release notes.

Improvements

  • Load balancing: Now message-based, distributing loads more evenly across consumers.

  • Dashboard: Added metrics for accumulated message count, duration, and success rate of each step from production to consumption.

  • Message trace: Trace query results now include parameters for scheduled messages, delayed messages, transactional messages, and message consumption.

  • Ordered messages: The maximum retry count is now 16.

  • Broadcasting consumption: The consumer offset can be set when starting a consumer.

  • Push mode: Added consumption throttling. Optimized processing logic for abnormal consumption thread counts.

Earlier versions

1.1.0

Release dateDescriptionDownload link for WindowsDownload link for Linux
2017-07-25

Fixed issues

  • The following issue is fixed: Core dumps are caused when a consumer is shut down.
  • The following issue is fixed: Access over HTTP is unavailable to the underlying URL class in Windows.
  • The following issue is fixed: Timestamp errors occur in message traces.
  • The following issue is fixed: Incorrect local IP addresses are displayed in message traces.
  • Memory leaks in Windows are fixed.
aliyun-mq-windows-cpp-sdk.zipaliyun-mq-linux-cpp-sdk.tar.gz

1.0.9

Release dateDescriptionDownload link for WindowsDownload link for Linux
2016-12-29

Added features

  • Messages can be sent in one-way mode.
  • Ordered messages are supported.
  • The timeout period for sending messages can be set.
  • The maximum number of retries for messages can be set.

Fixed issues

  • Resource leaks during shutdown are fixed.
  • Core dumps during shutdown are fixed.
None.None.

1.0.8

Release dateDescriptionDownload link for WindowsDownload link for Linux
2016-12-02

Added features

  • The earlier version of the SDK for C# is no longer supported. An updated version of the SDK for C# is generated by using SWIG. The updated version provides more stable support for ASP.NET.
  • Log paths can be customized.
  • Built-in UTF-8 encoding is provided to support implicit encoding and decoding.
  • The MQ_GUIDE documentation is provided. The ASP.NET demo is provided.

Optimized features

  • The boost library is updated to V1.6.2.

Fixed issues

  • The following issue is fixed: Core dumps occur when the producers or consumers of ordered messages are shut down.
None.None.

1.0.7

Release dateDescriptionDownload link for WindowsDownload link for Linux
2016-11-15

Added features

  • Consumption throttling is supported for consumers. By default, 1,000 messages are pulled and stored in the memory and then called back by the callback function one by one.
  • Ordered messages are supported.
  • The timeout period for sending messages can be set.
  • The maximum number of retries for messages can be set.

Optimized features

  • The message tracing feature is optimized. A separate thread pool is used to send trace data.
  • The granularity of the TCP lock is optimized.

Fixed issues

  • Issues related to message tracing are fixed.
  • Core dumps caused by shutdown are fixed.
  • Memory leaks are fixed.
  • The following issue is fixed: An exception is thrown if a message tag contains double vertical bars (||).
None.None.