You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
Runtime platform environment
Ubuntu 22.04.2 LTS
RocketMQ version
5.3.2-SNAPSHOT
JDK Version
1.8
Describe the Bug
In the connect event of the ChannelDuplexHandler in netty, the SocketAddress localAddress is empty because the connection has not yet been established.
Steps to Reproduce
no
What Did You Expect to See?
192.168.1.1 => 192.168.1.1:9876
We can just get the local ip without getting the port to print the local ip, if we want to get the port, we may need to print the relevant information in the channelActive event
What Did You See Instead?
UNKNOWN => 192.168.1.1:9876
Additional Context
No response
The text was updated successfully, but these errors were encountered:
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
Runtime platform environment
Ubuntu 22.04.2 LTS
RocketMQ version
5.3.2-SNAPSHOT
JDK Version
1.8
Describe the Bug
In the connect event of the ChannelDuplexHandler in netty, the SocketAddress localAddress is empty because the connection has not yet been established.
Steps to Reproduce
no
What Did You Expect to See?
192.168.1.1 => 192.168.1.1:9876
We can just get the local ip without getting the port to print the local ip, if we want to get the port, we may need to print the relevant information in the channelActive event
What Did You See Instead?
UNKNOWN => 192.168.1.1:9876
Additional Context
No response
The text was updated successfully, but these errors were encountered: