apache / apache/rocketmq-client-cpp

Consumer can normally consume message, but subscription detail and consume type and mode display unusual.

オープン
#402 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る
主要言語
C++
スター
393
フォーク
167
PR マージ指標
30日以内にマージされた PR はありません

説明

**BUG REPORT**

1. Please describe the issue you observed:

- What did you do (The steps to reproduce)?

When I run a cpp consumer, I found that there's no clientID information in subscription in console, but the consumer can normally consume. As follows:

Can normally consume:
![image](https://user-images.githubusercontent.com/50660789/152937023-a9f8d8d9-fe0b-4d4e-b2fe-d70e5b183b20.png)

Subscription detail display unusual:

![image](https://user-images.githubusercontent.com/50660789/152937279-cfa7a5ab-d36f-43fa-a002-ec09bbb264d7.png)

Didn't show subsciption's consume type and consume mode:

![image](https://user-images.githubusercontent.com/50660789/152937467-49410be9-6f75-4894-bc26-65a206986167.png)

- What did you expect to see?

The reason for subscription detail display unusual is the json format of ConsumeRunningInfo is incompatible with RocketMQ Java main project.

The reason for client didn't show consume type and consume mode is that c client send enum element as 0/1/2,which can't be parsed by RocketMQ Java main project.

- What did you see instead?

2. Please tell us about your environment:

- What is your OS?

- What is your client version?

- What is your RocketMQ version?

3. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

Start by reproducing the issue with a C++ consumer and comparing the ConsumeRunningInfo JSON and enum values sent by the C++ client with the RocketMQ Java main project. Trace the subscription detail display and verify that client ID, consume type, and consume mode are represented and parsed correctly while message consumption still works.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
cpp, java
領域
distributed-systems
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
おおむね明確
初心者へのやさしさ
35/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。