Creating multiple connections from the same host ip/port to an identical remote ip/port to contact separate slaves results in the second connection being dropped by the peer.
Affected Version
1.11.0
Screenshots
Expected
Unsure, commit af11b5ac64b28511eafa377dfa185a71bbbac87d seems to indicate that this behavior should be possible
Actual
When sending execute requests, the connection for the second "master" is rejected resulting in the request failing.
Steps to Reproduce
create two TcpMaster instances with the same IP/port, send requests from each, the second fails with "ConnectionResetError: [Errno 104] Connection reset by peer"
Description of Issue
Creating multiple connections from the same host ip/port to an identical remote ip/port to contact separate slaves results in the second connection being dropped by the peer.
Affected Version
1.11.0
Screenshots
Expected
Unsure, commit af11b5ac64b28511eafa377dfa185a71bbbac87d seems to indicate that this behavior should be possible
Actual
When sending execute requests, the connection for the second "master" is rejected resulting in the request failing.
Steps to Reproduce
create two TcpMaster instances with the same IP/port, send requests from each, the second fails with "ConnectionResetError: [Errno 104] Connection reset by peer"