You may be right. But the problem is that the request seem to stall internally without to fail or to do anything else. And this is not ok.
So now we know that reregisterAll helps, nothing new but its an info :) Some solution would be nice. Toad siad this is hard to debug, but if we check the various user reports then many users seem to have this problem. On 5/1/07, Florent Daigni?re (NextGen$) <nextgens at freenetproject.org> wrote: > * Bob Ham <rah at bash.sh> [2007-05-01 17:28:05]: > > > On Mon, 2007-04-30 at 18:19 +0200, bbackde at googlemail.com wrote: > > > > > I've noticed this as well on downloads. If I change the priority, > > > either lower or higher, the download will start retrieving blocks > > > again. > > > > I can confirm this behaviour. > > changing the priority of a request calls > ClientRequestScheduler.reregisterAll(ClientRequester) ... meaning that > nothing is very surprising... > > NextGen$ > PS: see > https://emu.freenetproject.org/svn/trunk/freenet/src/freenet/client/async/ClientRequestScheduler.java > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGN27SU/Z/dHFfxtcRAmDfAKCsQIEul7CNwaVWpp/qKMSQNFbblQCffsuJ > Tsf9Usaoh1McV42g5gELxN0= > =cZnG > -----END PGP SIGNATURE----- > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl >
