Hi guys.

I'm owning a 6360 Fritzbox (cable version) using it with my cable provider unity media in germany. 32mbit downstream.

So sometimes it happens that the box freezes/reboots during downloading via jdownloader. First I thought that happens also when I download via Firefox or similar. But It doesn't. Since I'm a software developer, I wanted to check out what might be the problem. So here's what I've found out. Maybe someone gets an idea what is causing the problem.

Environment:
- Fritzbox 6360 cable, 32 mbit downstream, provider unity media, germany, NRW
- No reconnects configured (keeps the same IP all the time)
- Tested with netload and plain http links only
- Jdownloader, latest stable, running on Win7 (but also happens under Ubuntu)
- Jdownloader connected via wired, 1Gbit lan
- Netload premium account

Test setup:
- Created 200 100mb files.
- Uploaded them to netload and my private apache server running under debian linux
- Configured jdownloader to: max con: 2, max dls: 2 (only then 32mbit is reached constantly).

Tests:
- Downloading these files from my apache server works without any problems (simple http links). No freezes, no reboots.
- Downloading these files from netload forces a freeze with an following reboot of my 6360 fritzbox after max. 30 minutes of downloading.

Since I've only owning a netload account I couldn't perform the test with other oneclick hosters like rapidshare. Also it also seems to happen only when 32mbit is completely maxed out.

Any clue what that could be? Maybe the netload plugin doesn't close connections properly? Or the netload http server handles connection differently? Strange is that simple http links work (to my own server).

[Jiaz]

hardware issues with router. seems it has issues with high bandwith load. happens on other routers too
try to set speed limit in jdownloader and try again

[Jiaz]

also check for qos options and such things, some routers have issues there

But why is it happening only with netload and not with my own apache server?
Bandwith is also maxed out with it.

How is the connection handling implemented in jdownloader? Does each plugin handle this by it's own or is there a common connection class that every plugin is using (plain http link plugin, netload plugin)?

[Jiaz]

there also exists isp which have routing issues etc. using netload = issue can happen and kill connection.

its not jdownloader causing this trust me. every user reporting the same it was
firewall/Av/isp/router issues and all could be solved.

Originally Posted by vguna

How is the connection handling implemented in jdownloader? Does each plugin handle this by it's own or is there a common connection class that every plugin is using (plain http link plugin, netload plugin)?

jD is open source. You can check it.

@Jiaz:
Sure. There're a lot of routers that have problems with load. And I would agree that's the problem with mine too if that would happen also with plain http links. Don't get me wrong. You're probably right. But since I'm also a java developer I want to know what's the difference between these two providers. Why the one works and the other don't. network/routing issues on netload side may be reason, yes.

@Remi:
Yeah, thought about it. But I get tired fixing bugs in open source projects.
If you tell me it's the same connection class for all plugins then I won't take a look at it. But if it isn't maybe I grab cold beer and looking into it.

Thanks anyways guys!

[Jiaz]

use wireshark and then you know the difference on deepest level
all reports from other users with same issues, it was isp/router issues, thats all i can say.

Originally Posted by vguna

If you tell me it's the same connection class for all plugins then I won't take a look at it. But if it isn't maybe I grab cold beer and looking into it.

I don't know the code. I'd expected that Jiaz would be able to reply to that question.

[Jiaz]

yes, it is one browser class used by all plugins