apache / apache/rocketmq-client-cpp

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

未關閉
#402 0 則留言 0 個 reaction 已指派 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):

貢獻指南

開啟貢獻指南

研究方向

首先,使用 C++ consumer 重現該問題,並將 C++ client 傳送的 ConsumeRunningInfo JSON 和 enum values 與 RocketMQ Java main project 進行比較。追蹤訂閱詳細資料的顯示,並驗證 client ID、consume type 和 consume mode 是否正確表示及解析,同時確保訊息消費仍可正常運作。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
cpp, java
領域
distributed-systems
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。