[mafourti]

25.04.23 11.41.11 <--> 25.04.23 13.46.15 jdlog://0494311370661/

I'm downloading using a premium uptobox account. When starting the download, I see some MB downloaded, then the download status doesn't seem to change, but I see on windows explorer that the temporary file size increase.
After some time, it then shows "network problems"


edit: clicking on stop button then play button allowed it to resume
25.04.23 11.41.11 <--> 25.04.23 13.49.48 jdlog://1494311370661/

[notice]

@mafourti: the other chunks/connections are getting killed

java.net.SocketException: Connection reset

Issue can be caused by Firewall/AV/lokal network tools and/or remote side, eg Firewall/Server/ISP..
Try to set max chunks/connections to 1 and see if that helps

[mafourti]

i've tested a few times and indeed, setting to max 1 chunk solve the problem. Thank you
It's very strange. It was working with multiple chunks when I had non premium account.
What is problematic there is that it takes like 2 minutes before jdownloader become responsive again (i can't remove the file, restart it, stop downloads etc)

is it possible to set the number of chunks per account or per hoster ?
Or maybe could you more quickly detect the chunk problem and prevent rendering the interface unresponsive by restarting the chunk faster ? I don't know

[notice]

Originally Posted by mafourti

i've tested a few times and indeed, setting to max 1 chunk solve the problem. Thank you
It's very strange. It was working with multiple chunks when I had non premium account.

Thanks for the feedback and confirmation. Most likely it's caused by overloaded server that has too many connections ongoing and therefore random connections dying.

Originally Posted by mafourti

What is problematic there is that it takes like 2 minutes before jdownloader become responsive again (i can't remove the file, restart it, stop downloads etc)

IO handling within the OS cannot be interrupted and JDownloader/Java has to wait for api method from OS to return normally/abnormally.

Originally Posted by mafourti

is it possible to set the number of chunks per account or per hoster ?

unfortunately not yet :( there are open tickets for this

[mafourti]

i understand that it's handled by the os, however, stopping the downloads using the button stop or by doing right click stop could kill the threads or whatever ?
Because right now even stopping the downloads does nothing for a few minutes

[notice]

Originally Posted by mafourti

i understand that it's handled by the os, however, stopping the downloads using the button stop or by doing right click stop could kill the threads or whatever ?

It's not possible to interrupt a method that is currently in OS. the program/Java has to wait for this method to return.
Have you checked local firewall/av? maybe tried to disable/uninstall for testing? for example they could intercept the connection for scanning and block reader until some result is available and then stop will take longer.

[pspzockerscene]

* it might be possible to force interrupt this by disabling/enabling the currently used "internet connection adapter" in your system.

[mafourti]

I tried disabling avast anvirus and the windows firewall but it didn't changed, it still does the same thing.

Completely uninstalling avast to test is not possible however.

Disabling the network card does indeed make jdownloader able to respond quicker pspzockerscene

[mafourti]

Strangely, downloading to my local ssd doesn't trigger the problem, but when I download it to a HDD from my nas with SMB, it does have the problem

[notice]

Originally Posted by mafourti

Strangely, downloading to my local ssd doesn't trigger the problem, but when I download it to a HDD from my nas with SMB, it does have the problem

Downloading with multiple connections and larger files require sparse file support. If that's not available, the OS has to create/write the complete empty file before the next connections/chunks can start. Imagine a 4GB file with 2 connections, then the OS has to write 2GB on file , which is blocking OS action and that may easily take some time (as many NAS don't provide fast IO over network). That fill operation of the OS cannot be interrupted and the next chunk will die of socket closing when this takes too long.

[mafourti]

thanks.