Bug #1573

Thread Aborted does not close TCP connection

Added by drbits over 10 years ago. Updated over 9 years ago.

Status:ClosedStart date:04/10/2010
Priority:NormalDue date:
Assignee:jiaz% Done:


Category:GeneralEstimated time:3.00 hours
Target version:010 - Next Major Public Release 1.xxx


The uploaded log http://jdownloader.net:8081/pastebin/62592e0f16ad6545cc106cd82bc93910
shows that Rapidshare sent a "Temporary unavailable" with a wait time of 10 minutes (600000 ms). JD ignored the wait time and tried to start a new download. This time receiving an "Unexpected error" (as one might expect) and aborted the thread. Rapidshare did not know the thread was aborted, which means that no RST or FIN was received at the Rapidshare end.

JD made many attempts to start new downloads, all failed because of the existing connection for about 1/2 hour (RS must have timed out the TCP connection). JD continued trying to start new downloads and ignoring the Temporary unavailable message.

Also available in: Atom PDF