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

Concurrent problems with client-side connection creation #1108

Closed
zhanguohuang opened this issue Mar 22, 2019 · 4 comments
Labels
bug
Milestone

Comments

@zhanguohuang
Copy link
Contributor

@zhanguohuang zhanguohuang commented Mar 22, 2019

The issue tracker is ONLY used for bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before your raise a new one.

Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.

Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:

BUG REPORT

  1. Please describe the issue you observed:
  • What did you do (The steps to reproduce)?
    Send two messages at the same time. When the producer needs to create a new connection with the broker, one message will fail because the connection is disconnected.

  • What did you expect to see?
    Both messages were sent successfully

  • What did you see instead?
    From the producer, we can see from the log.

2019-03-20 17:07:35,911 INFO test1-send2mq-thread-1 NettyRemotingClient createChannel: remote host[192.168.0.2:10909] success, DefaultChannelPromise@2c99850(success)
2019-03-20 17:07:35,912 INFO test2-send2mq-thread-2 NettyRemotingClient createChannel: remote host[192.168.0.2:10909] success, DefaultChannelPromise@5a0a54b3(success)

From the broker, we can see it from the remoteing.log.

2019-03-20 17:07:35 INFO NettyServerCodecThread_1 - Netty Sever PIPELINE: channelRegistered 192.168.0.1:41548
2019-03-20 17:07:35 INFO NettyServerCodecThread_1 - Netty Sever PIPELINE: channelActive 192.168.0.1:41548
2019-03-20 17:07:35 INFO NettyServerCodecThread_1 - Netty Sever PIPELINE: channelInactive 192.168.0.1:41548
2019-03-20 17:07:35 INFO NettyServerCodecThread_1 - Netty Sever PIPELINE: channelUnregistered 192.168.0.1:41548
2019-03-20 17:07:35 INFO NettyServerCodecThread_1 - Netty Sever PIPELINE: channelRegistered 192.168.0.1:41659
2019-03-20 17:07:35 INFO NettyServerCodecThread_1 - Netty Sever PIPELINE: channelActive 192.168.0.1:41659
  1. Please tell us about your environment:
    rocketmq version: 4.3.2
    jdk version: 1.8.0_101

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

FEATURE REQUEST

  1. Please describe the feature you are requesting.

  2. Provide any additional detail on your proposed use case for this feature.

  3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

  4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

@zhanguohuang

This comment has been minimized.

Copy link
Contributor Author

@zhanguohuang zhanguohuang commented Mar 22, 2019

I have fixed this problem. #1109

@duhenglucky

This comment has been minimized.

Copy link
Contributor

@duhenglucky duhenglucky commented Jul 31, 2019

@zhanguohuang Good catch, It seems that it's indeed a bug in creating remoting channel.

@zhanguohuang

This comment has been minimized.

Copy link
Contributor Author

@zhanguohuang zhanguohuang commented Jul 31, 2019

@duhenglucky Thanks.

duhenglucky added a commit that referenced this issue Sep 19, 2019
…lient

[ISSUE #1108] Fix concurrent problems with client-side connection creation
@zongtanghu

This comment has been minimized.

Copy link
Contributor

@zongtanghu zongtanghu commented Nov 13, 2019

This issue has already been resolved by link:#1109

@zongtanghu zongtanghu closed this Nov 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.