There is very little advantage to low timeouts.

For example the captcha timeout: what's the point of dismissing a Bitshare captcha if the user was away from the computer for 15 seconds? He will have to restart the link and wait another minute or so before a new captcha comes up (Bitshare has a pre-captcha delay, unlike Uploaded). Why not default the timeout at 5 minutes?

The really bad timeout is the network inactivity one. If my computer is busy with many tasks and swapping (trashing the HDD), JD will notice that no bytes were written for an Uploaded download after 30 seconds (or whatever the default was, I can't remember) and cancel the download. Then I have to wait 3 hours to retry it. The network timeout should be something like 15 minutes. It doesn't really serve a purpose anyway.

[pspzockerscene]

Ticket:


GreeZ psp

[coalado]

Captcha Dialog TImeout: Advanced Settings: "CaptchaSettings: Dialog Countdown"

About Your network - whatever problems:

1. If you have 2 Problems - Create to Topics. Mixed Topics make it hard for us to track problems
2. Please Explain in detail about our Network timeout Problem.

There are many timeout options. A log would be great as well.

@coalado: I blame the Http Read Timeout (filter by http in advanced settings). Just an informed guess.

I've had my Linux box swapping for minutes on end (when it was low on memory) and JD ended up killing some connections, presumably because it wasn't getting any timeslots from the OS (thus it wasn't reading anything). After increasing the Http Read Timeout, it hasn't happened again.

Thanks for the bug. I knew how to fix the problem, but I think the defaults should be more reasonable. Also when reinstalling JD, it's good to not have to tweak so many values.

[coalado]

what would be a reasonable timeout.

The problem is, that jd cannot interrupt socket reads. that means, that it may take up to the timeout time to stop a download that is in a readtimeout.

So, worst-case, when the hoster stops responding (which doesn't happen so often), JD will not restart as early as it could? The user can interrupt manually if they see downloads stalling.

In my opinion, maybe 5 minutes. The default is 30 seconds I think. By the way this is one of the advanced settings where the unit is not defined (the default is 30000, but in what units? Seconds? msec?). This is why I think either all constants should be in msec, or you should add a "Units" column after the Type column.

[coalado]

all constants are in ms. there are some in seconds, but they will be replaced

The user cannot stop.. that IS the problem. if you set the timeout to 5 minutes... a shutdown may take 5 minutes.


The only good solution is proper "close connections on interrupt"