Author: toad
Date: 2008-06-21 12:20:58 +0000 (Sat, 21 Jun 2008)
New Revision: 20558
Modified:
branches/db4o/freenet/src/freenet/client/async/ClientRequestSchedulerCore.java
Log:
Change activation depth on allRequestsByClientRequest.
*MAYBE* fix mass-activation bug. (Note that I've seen this when there is
nothing to activate: current working theory is that it recurses over every
connected item to depth hops to see if it's activated or not).
Modified:
branches/db4o/freenet/src/freenet/client/async/ClientRequestSchedulerCore.java
===================================================================
---
branches/db4o/freenet/src/freenet/client/async/ClientRequestSchedulerCore.java
2008-06-21 12:16:33 UTC (rev 20557)
+++
branches/db4o/freenet/src/freenet/client/async/ClientRequestSchedulerCore.java
2008-06-21 12:20:58 UTC (rev 20558)
@@ -102,7 +102,7 @@
private void onStarted(ObjectContainer container, long cooldownTime,
ClientRequestScheduler sched, ClientContext context) {
if(!isInsertScheduler)
((Db4oMap)pendingKeys).activationDepth(Integer.MAX_VALUE);
-
((Db4oMap)allRequestsByClientRequest).activationDepth(Integer.MAX_VALUE);
+ ((Db4oMap)allRequestsByClientRequest).activationDepth(1);
((Db4oList)recentSuccesses).activationDepth(Integer.MAX_VALUE);
this.container = container;
if(!isInsertScheduler) {
