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.

Sign up for GitHub

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

Jump to bottom

resource is taken #93

Closed
jiait opened this issue Jan 6, 2022 · 3 comments
Closed

resource is taken #93

jiait opened this issue Jan 6, 2022 · 3 comments
Milestone
2.1.0

Comments

@jiait
Copy link

jiait commented Jan 6, 2022 •
edited
Loading

Call message from remote node, error code is received for the first time: Can't connect to [email protected] Resource is taken, continue communication with no problem, not sure whether the initial connection of the node is wrong, or the process connecting to the remote node is wrong? Do you need to ping each other in advance to avoid this problem?
@halturin
Copy link
Collaborator

halturin commented Jan 6, 2022 •
edited
Loading

If two or more processes are trying to send a message to the peer it hasn't connected to yet, it tries to create this connection, so there could be a case of two or more concurrent connection processes. You can workaround this case by just making a connection in advance.

Its already been fixed in the development branch.

@jiait
Copy link
Author

jiait commented Jan 7, 2022

Thank you. Look forward to updates

@jiait jiait mentioned this issue Jan 13, 2022
Closed
@halturin halturin added this to the 2.1.0 milestone Jan 13, 2022
@halturin
Copy link
Collaborator

fixed in 2.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.1.0
Development

No branches or pull requests
2 participants
@halturin @jiait