4pr0n / ripme

Downloads albums in bulk
MIT License
918 stars 203 forks source link

SocketTimeoutException during imgur subreddit rip #64

Open dragoon-heli opened 10 years ago

dragoon-heli commented 10 years ago

On large imgur.com albums, it's common to receive a SocketTimeoutException error:

java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read1(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source) at sun.net.www.http.HttpClient.parseHTTP(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at java.net.HttpURLConnection.getResponseCode(Unknown Source) at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:443) at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:424) at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:178) at org.jsoup.helper.HttpConnection.get(HttpConnection.java:167) at com.rarchives.ripme.ripper.rippers.ImgurRipper.ripSubreddit(ImgurRipper.java:310) at com.rarchives.ripme.ripper.rippers.ImgurRipper.rip(ImgurRipper.java:95) at com.rarchives.ripme.App.rip(App.java:44) at com.rarchives.ripme.App.handleArguments(App.java:88) at com.rarchives.ripme.App.main(App.java:35)

dragoon-heli commented 10 years ago

property setting when encountering this fault: threads.size = 3 download.retries = 10 download.timeout = 180000

CaspianRoach commented 10 years ago

I can reproduce, couldn't update from .59, so tried manually downloading the latest one and just launching that.

2014-06-12 13:18:13,274 3700 [Thread-5] ERROR ui.UpdateUtils - Error while fetching update: java.net.SocketTimeoutException: connect timed out at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at sun.net.NetworkClient.doConnect(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source) at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:439) at org.jsoup.helper.HttpConnection$Response.execute(HttpConnection.java:424) at org.jsoup.helper.HttpConnection.execute(HttpConnection.java:178) at org.jsoup.helper.HttpConnection.get(HttpConnection.java:167) at com.rarchives.ripme.ui.UpdateUtils.updateProgram(UpdateUtils.java:44) at com.rarchives.ripme.ui.MainWindow$2.run(MainWindow.java:155) at java.lang.Thread.run(Unknown Source)

The program won't launch at all, stuck at white screen. Turning autoupdate off launches the program properly.

4pr0n commented 10 years ago

I reproduced this. Imgur subreddit rip timeout was increased to 10 seconds in https://github.com/4pr0n/ripme/commit/8b2d30496da620ef294a2e58b138e3bda0429a6a

Let me know if you see the error again and I may bump it up further.

If you do see it again, retry the rip once or twice after failure -- it should work then.

4pr0n commented 10 years ago

Is there a way to turn the autoupdate off?

@CaspianRoach In rip.properties file, set:

auto.update = false
CaspianRoach commented 10 years ago

Yes, on the second inspection it's not the same error, but a similar one. Mine occurs on auto-updates. Works fine after turning autoupdate off.