I still get occurences of #393 (No results after some time).
I made a simple test with amule + JEmule server and detected indeed a problem.
Test case:
- start server
- start amule
- let connect it to the server
- search -> works
- quit the server -> I see a FIN, ACK packet
- redo search -> hangs; I see the search request and a RST packet from the server.
-> even the server keepalive in the extended tab does not manage to get amule out of this trap.
It sounds like amule is stuck waiting for a reply from the server and can not handly the connection abort (both FIN and RST).
And this is not even a real "timeout situation", as the server responds clearly "I'm not here (anymore)" on TCP level ...
I still get occurences of #393 (No results after some time).
I made a simple test with amule + JEmule server and detected indeed a problem.
Test case:
-> even the server keepalive in the extended tab does not manage to get amule out of this trap.
It sounds like amule is stuck waiting for a reply from the server and can not handly the connection abort (both FIN and RST).
And this is not even a real "timeout situation", as the server responds clearly "I'm not here (anymore)" on TCP level ...