Skip to content

[Bug] Create topic failed with TLS enable in DLedger mode. #9136

@hexueyuan

Description

@hexueyuan

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

CentOS 8

RocketMQ version

4.9.8

JDK Version

JDK 21

Describe the Bug

Create topic failed with TLS enable in DLedger mode, I notice that it first report at #4273 and fix in #4274 , but it seems not merge to current release. And no processing logic related to this problem was found in the code, I don't know if this issue has been resolved.

Steps to Reproduce

Startup a DLedger cluster and enable TLS, then create new topic to reproduce this issue.

What Did You Expect to See?

Broker should provide service normally with TLS enable in DLedger mode.

What Did You See Instead?

Create topic failed with TLS enable in DLedger mode.

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions