Server doesn't reply any peer created after old peers have been closed.
Closed this issue · 0 comments
mattatcha commented
Here are some logs. You can reproduce the same problem by running the tests I created in the referenced PR.
You should be able to see that the last client sends a frame but the server doesn't read the frame.
2014/11/01 20:34:20 6 Sending frame [ 0 ]: &{false 0xc2080059e0 0xc208005920 0 0 Arith.Add map[] false []}
2014/11/01 20:34:20 6 Pumping started for channel 0
2014/11/01 20:34:20 6 Sending frame: &{false 0xc208005aa0 0xc208005920 1 0 map[] true [130 161 65 7 161 66 8]}
2014/11/01 20:34:20 Reading frame: {false <nil> <nil> 0 0 Arith.Add map[] false []}
2014/11/01 20:34:20 4 Pumping started for channel 0
2014/11/01 20:34:20 Reading frame: {false <nil> <nil> 1 0 map[] true [130 161 65 7 161 66 8]}
2014/11/01 20:34:20 4 Sending frame: &{false 0xc208005d40 0xc208005bc0 1 0 map[] true [129 161 67 15]}
2014/11/01 20:34:20 4 Pumping finished for channel 0
2014/11/01 20:34:20 EOF
2014/11/01 20:34:20 Reading frame: {false <nil> <nil> 1 0 map[] true [129 161 67 15]}
2014/11/01 20:34:20 6 Pumping finished for channel 0
2014/11/01 20:34:20 read tcp 127.0.0.1:9876: use of closed network connection
2014/11/01 20:34:20 7 Connecting 127.0.0.1:9876
2014/11/01 20:34:20 EOF
2014/11/01 20:34:20 sending greeting to 127.0.0.1:9876 : f724082e-b216-4aa3-bf68-46913ae5c91c
2014/11/01 20:34:20 received greeting from 127.0.0.1:57515 : f724082e-b216-4aa3-bf68-46913ae5c91c
2014/11/01 20:34:20 sending greeting to 127.0.0.1:57515 : 3246bc2c-f770-4ad4-8a5a-cfe611a6db82
2014/11/01 20:34:20 received greeting from 127.0.0.1:9876 : 3246bc2c-f770-4ad4-8a5a-cfe611a6db82
2014/11/01 20:34:20 7 Connected
2014/11/01 20:34:20 7 First connection, routing...
2014/11/01 20:34:20 7 Sending frame [ 0 ]: &{false 0xc208005f80 0xc208005ec0 0 0 Arith.Add map[] false []}
2014/11/01 20:34:20 7 Pumping started for channel 0
2014/11/01 20:34:20 7 Sending frame: &{false 0xc2080aa060 0xc208005ec0 1 0 map[] true [130 161 65 7 161 66 8]}