#1
|
|||
|
|||
Incorrect queue handling when mirrors present
If a file is added to queue on different servers, example:
file1 hotfile file1 fileserve (the same file as on hotfile) then following scenario can occur: 1. hotfile is starting download 2. fileserve is disabled with message "Mirror hotfile.com is loading: File already exists" 3. hotfile is disabled because "File not found" As a result nothing is downloaded and jdownloader requires user attention. Last edited by Jiaz; 25.03.2011 at 09:17. |
#2
|
||||
|
||||
__________________
JD-Dev & Server-Admin |
#3
|
|||
|
|||
The disabling of a link should only happen when a (mirror) file has been successfully downloaded.
The Status message "File already exists" does not correspond to reality, because the file doesn't exist. @kretos I would not load too many links in your download queue. This avoids the situation that files go off-line after they have been added to the queue. If you can't avoid it, you can use the function "Check Online Status" before your packages start downloading. |
#4
|
|||
|
|||
Thanks for reply, as I understand the queue shold be used to store links - mirrors also:) The problem is that jd marks files as downloaded when one of mirrors is starting and it shows 100% downloaded file which is invalid.
|
#5
|
|||
|
|||
I'm sorry but I don't understand.
|
#6
|
|||
|
|||
When file (same name) is on different servers, then one of those servers (according to priority and position in queue) is asked to send file. JD disables all others files (mirrors) on different servers. Also all mirrors are marked as 100% complete but the real download is not completed yet. I'm not sure if those mirrors are set as completed at the same stage when disabling happens or when JD is restarted. Sorry for my english - it's not my spoken language so here's an example:
stage 1 - put into queue: file1 hotfile file1 fileserve (the same name of file as on hotfile) stage 2 - download: file1 hotfile - starts to download file1 fileserve - disabled with message "Mirror hotfile.com is loading: File already exists" stage 3 - file 1 hotfile - interrupted (file not found on hoster/error during transport/JD restart) - interrupted download file 1 fileserve - disabled but presented as 100% completed - as remi wrote "The disabling of a link should only happen when a (mirror) file has been successfully downloaded. The Status message "File already exists" does not correspond to reality, because the file doesn't exist". It would be nice to disable mirrors when download actually starts to avoid "File deleted" errors and to set mirrors to completed when any of mirrors is actually completed not started. |
#7
|
|||
|
|||
The way mirror handling should be designed is that all mirror links are put in one row. If one link fails then another links should be tried automatically until at least one of them downloads properly.
|
Thread Tools | |
Display Modes | |
|
|