Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Local Mode cannot work properly without necessary remoting ext-headers accessible #7552

Closed
3 tasks done
lizhanhui opened this issue Nov 10, 2023 · 0 comments
Closed
3 tasks done

Comments

@lizhanhui
Copy link
Contributor

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

N/A

RocketMQ version

N/A

JDK Version

N/A

Describe the Bug

N/A

Steps to Reproduce

Run the following integration test src/test/java/org/apache/rocketmq/test/grpc/v2/LocalGrpcIT

What Did You Expect to See?

Test should pass

What Did You See Instead?

Test failed

Additional Context

No response

lizhanhui added a commit that referenced this issue Nov 10, 2023
Signed-off-by: Zhanhui Li <[email protected]>
lizhanhui added a commit that referenced this issue Nov 10, 2023
Signed-off-by: Li Zhanhui <[email protected]>
lizhanhui added a commit that referenced this issue Nov 13, 2023
…fer (#7550)

* Reuse helper methods from Netty to free direct byte buffer, making codebase JDK 9+ compatible

Signed-off-by: Li Zhanhui <[email protected]>

* Guard against null

Signed-off-by: Li Zhanhui <[email protected]>

* fix #7552

Signed-off-by: Li Zhanhui <[email protected]>

---------

Signed-off-by: Li Zhanhui <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant