Hentai@Home 1.2.1, Unraveling Options

- In some configurations, H@H could hang at startup because Java tried to reuse a connection that was already closed by the H@H C&C server. We now turn HTTP keepalive/connection reuse off entirely to prevent this from happening.

- Fixed a possible case where threads would fail to terminate and start piling up when using H@H as a proxy.

Unless either of these is a problem for you, there is no need to update.

Download from the usual place.

For information on how to join Hentai@Home, check out The Hentai@Home Project FAQ.

Thanks for the little-big patch. (IMG:[invalid] style_emoticons/default/laugh.gif)
Now I can run the H@H with two less things to worry about. Especially since I host all my client on VPSes and none of them would take excessive thread hoarding very well.

This post has been edited by LostLogia4: Aug 16 2014, 10:26

Thanks for the update. I use my server as a proxy and it was accumulating threads before.

I don't run H@H at home but I would to donate to the site by running adopted servers, 10b could you open me some slots so I can start doing so?

I don't run H@H at home but I would to donate to the site by running leased servers, 10b could you open me some slots so I can start doing so?

Didjya mean leased servers to run H@H clients, or Adopt-a-Server slots? (IMG:[invalid] style_emoticons/default/rolleyes.gif)
You'll need some Bitcoins to spare at your donation address for the latter.

Didjya mean leased servers to run H@H clients, or Adopt-a-Server slots? (IMG:[invalid] style_emoticons/default/rolleyes.gif)
You'll need some Bitcoins to spare at your donation address for the latter.

Sorry I don't really know what H@H does, I probably meant the latter >.<

I do have some spare bitcoins, just not into 10B wallet yet cuz I know I wouldn't get a refund, and bitcoin price is dropping like hell this days..

There's a pointer to a SO question ([stackoverflow.com] this one) in the changelog, but it doesn't seem related to the changes (IMG:[invalid] style_emoticons/default/blink.gif)

- In some configurations, H@H could hang at startup because Java tried to reuse a connection that was already closed by the H@H C&C server. We now turn HTTP keepalive/connection reuse off entirely to prevent this from happening.

Cool thanks Tenboro now maybe I will not like see this 10 times every time my H@H Starts up. (IMG:[invalid] style_emoticons/default/biggrin.gif)

[WARN] Rejecting connection request during startup.

This post has been edited by WhiteWolfRevy92: Aug 17 2014, 02:31

Sorry I don't really know what H@H does, I probably meant the latter >.<

Should've replied that earlier, but H@H is basically a Java-based image server. H@H downloads the most frequently used images files from either the E-Hentai itself, or from other clients and serve the images to the gallery visitors - i.e. whenever you views a page from E-Hentai gallery that image was most likely served from H@H hosted at a server near to you.

Until this patch though, H@Home was rigged with a bug that prevents the threads from being flushed properly. Left unchecked, it would hog enough threads to be considered as resource abuse in VPN, resulting in H@H being blacklisted by several VPN providers.

Btw, I updated the H@H yesterday on my multi-IP VPN and one of it ended up being killed twice, resulting to (temporary) negative trust.
I've asked the VPN provider and they claimed they're not killing the process afaik.

There's a pointer to a SO question ([stackoverflow.com] this one) in the changelog, but it doesn't seem related to the changes (IMG:[invalid] style_emoticons/default/blink.gif)

Oh that. It's just a note to self about some weirdness I was seeing with the log pane. Apparently, you're not supposed to be modifying it the way I'm doing. But I believe I fixed it another way.

Oh that. It's just a note to self about some weirdness I was seeing with the log pane. Apparently, you're not supposed to be modifying it the way I'm doing. But I believe I fixed it another way.

Ah ok, thanks for the explanation. I was afraid I would have missed a change in the source code.

Wow, when I get home I need to update H@H. Work accumulates when you're away, even EH work.

Tenboro did we get rid of the technical support on H@H board (or am I merging a completely unrelated forum with EH) ...

Getting a weird

CODE

Hentai@Home GUI 1.2.1 initializing...
The client will automatically start up momentarily...
2014-08-19T05:01:02Z [info] Hentai@Home 1.2.1 starting up
2014-08-19T05:01:02Z [info]
2014-08-19T05:01:02Z [info] Copyright (c) 2008-2014, E-Hentai.org - all rights reserved.
2014-08-19T05:01:02Z [info] This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL v3 license.
2014-08-19T05:01:02Z [info]
2014-08-19T05:01:02Z [info] Loaded login settings from client_login
2014-08-19T05:01:02Z [info] Connecting to the Hentai@Home Server to register client with ID ####...
2014-08-19T05:01:02Z [info] Connecting to rpc.hentaiathome.net...
2014-08-19T05:01:02Z [info] /clientapi.php?clientbuild=86&act=server_stat: Retrieving 66 bytes...
2014-08-19T05:01:02Z [info] Reading Hentai@Home client settings from server...
2014-08-19T05:01:02Z [info] Connecting to rpc.hentaiathome.net...
2014-08-19T05:01:03Z [info] /clientapi.php?clientbuild=86&act=client_login&add=&cid=####&acttime=1408424474&actkey=98774acc938d16558cd87c117fbf1d16f8edc149: Retrieving 282 bytes...
2014-08-19T05:01:03Z [info] Applying settings...
2014-08-19T05:01:03Z [info] Finished applying settings
2014-08-19T05:01:03Z [info] CacheHandler: Initializing database engine...
2014-08-19T05:01:03Z [info] CacheHandler: Database file data/hath.db backed up as data\hath.db.bak-temp
2014-08-19T05:01:03Z [info] CacheHandler: Loading database from data/hath.db
2014-08-19T05:01:03Z [info] CacheHandler: Using SQLite 3.7.2 over SQLiteJDBC 2.1 running in native mode
2014-08-19T05:01:03Z [info] CacheHandler: Initializing database tables...
2014-08-19T05:01:03Z [info] CacheHandler: Optimizing database...
2014-08-19T05:01:03Z [info] Last shutdown was clean - using fast startup procedure.
2014-08-19T05:01:03Z [info] CacheHandler: Rotating database backups
2014-08-19T05:01:03Z [info] CacheHandler: Database initialized
2014-08-19T05:01:03Z [info] CacheHandler: Initializing the cache system...
2014-08-19T05:01:03Z [info] Starting up the internal HTTP Server...
2014-08-19T05:01:03Z [info] Internal HTTP Server was successfully started, and is listening on port ####
2014-08-19T05:01:03Z [info] Notifying the server that we have finished starting up the client...
2014-08-19T05:01:03Z [info] Connecting to rpc.hentaiathome.net...
2014-08-19T05:01:04Z [info] {1/94.100.22.210}   Code=200 Bytes=36       GET /servercmd/still_alive//1408424475/91a3bfa9b9c8c1e0e3c3b127e0bd3b7991b61277 HTTP/1.1
2014-08-19T05:01:04Z [info] {1/94.100.22.210}   Code=200 Bytes=36       Finished processing request in 0.02 seconds (2.40 KB/s)
2014-08-19T05:01:20Z [info] /clientapi.php?clientbuild=86&act=client_start&add=&cid=####&acttime=1408424475&actkey=2865e92e21a770bbf8ed42b42865eb7634cd16cf: Retrieving 69 bytes...
2014-08-19T05:01:20Z [info] Startup notification failed.

After upgrading.
even tried it from a completely new folder. reset my ranges. still same message.
due note I've been running 1.2.0 for quiet some time.

EDIT: Fixed. Changed Port. Restarted Router. Working now.

This post has been edited by HV3: Aug 19 2014, 09:56

At rest of asking something dumb, how do I update my client? I can't find info about that anywhere.

Just download the new one and paste it over the old one.

Oh, thanks. I thought it would have been more complicated than that. :V

Seems there is no need to update. (IMG:[invalid] style_emoticons/default/tongue.gif)

what is this i always get this

Connecting to rpc.hentaiathome.net...
2014-08-21T13:35:10Z [info] /clientapi.php?clientbuild=86&act=still_alive&add=&cid=1616&acttime=1408628107&actkey=3be41a5107f07025e92e93410942d35fac7b8f6a: Retrieving 35 bytes...
2014-08-21T13:37:16Z [info] Connecting to rpc.hentaiathome.net...
2014-08-21T13:37:16Z [info] /clientapi.php?clientbuild=86&act=download_list&add=129e6bd1fa8d19322d39151c229aa0303234ffec-260054-1200-1716-jpg;56c4c499df4f79139ee0c4bc4bf801c8b991fce7-14741-1200-1740-jpg;1505cb107158da0223300afe8cfaa08ae714cf2e-499695-1200-1735-jpg;bc2ddb47aa0c828e883cbd1060108155224010b2-481312-1200-1735-jpg;4078c951c791205eb97a8896be2311307e13cc69-388492-1200-1735-jpg;c4a9da0dd12996befd1aed387c79ebd179049b81-402994-1200-1735-jpg;baa498d2201c4f793ec3a0296b1d724eec5c84da-392713-1200-1735-jpg;8831b4127ae08ab990ba6dcdb25372aa35a1ecaf-480649-1200-1735-jpg;5a4b0ffdb6654c7b2dde56e9edc8ec66b7c74d4a-393037-1200-1730-jpg;412662a794b637c788bdb83c6001c0e0f3a20a02-414512-1200-1730-jpg;7c8fc641eeb2def27936fc6758f906cad4881c61-396856-1200-1730-jpg;deb05dd567dad9994d2745bb47fb037fc6257dbb-370123-1200-1730-jpg;69df5fb45abcada1bb98f24e80aca5b839e87246-428152-1200-1730-jpg;381d67fe36a42389c4fbadbd3a727f2895c42f18-430932-1200-1730-jpg;8a0d26aeeedfd2ec30b954aa2bcb7c9e74f60241-353546-1200-1730-jpg;d1920babb56edd1cd0221ca298dccf5808e33df3-389241-1200-1730-jpg;61788aa4d94d597edc320877190e14372b6382bc-421944-1200-1714-jpg;00b6570ec141d2a61a092990ec934f61737335a7-429576-1200-1714-jpg;9c6fdfc252dfaba6bdd9e7bc9930f64ba10ed519-434573-1200-1714-jpg;fefd94d75a282915cf5a33fc69982092cfe84a97-418016-1200-1714-jpg;&cid=1616&acttime=1408628233&actkey=312a4d694a088c372f5680388e31a1149026974d: Retrieving 210 bytes...
2014-08-21T13:37:16Z [info] Could not grab token list - most likely the client has not been qualified yet. Will retry in a few minutes.

Just keep it running for longer.

TBH, I liked it better the way the gallery comments were managed in the previous update. Any chance of reverting back to that?