Opened 5 years ago

Closed 5 years ago

#1174 closed defect (fixed)

Error processing job [Iterative search timeout] on thread 2: null

Reported by: dg Owned by: zzz
Priority: blocker Milestone: 0.9.11
Component: router/netdb Version: 0.9.10
Keywords: Cc:
Parent Tickets:

Description

19/01/14 XX:XX:XX CRIT 3/5? net.i2p.router.JobQueueRunner? : Error processing job [Iterative search timeout] on thread 2: null

java.lang.NullPointerException?
at net.i2p.router.networkdb.kademlia.IterativeSearchJob?.sendQuery(IterativeSearchJob?.java:318)
at net.i2p.router.networkdb.kademlia.IterativeSearchJob?.retry(IterativeSearchJob?.java:243)
at net.i2p.router.networkdb.kademlia.IterativeSearchJob?.failed(IterativeSearchJob?.java:371)
at net.i2p.router.networkdb.kademlia.IterativeTimeoutJob?.runJob(IterativeTimeoutJob?.java:26)
at net.i2p.router.JobQueueRunner?.runCurrentJob(JobQueueRunner?.java:134)
at net.i2p.router.JobQueueRunner?.run(JobQueueRunner?.java:75)
at java.lang.Thread.run(Thread.java:724)
at net.i2p.util.I2PThread.run(I2PThread.java:84)

0.9.9-10

Subtickets

Change History (3)

comment:1 Changed 5 years ago by dg

I think this happened after stopping I2PBote?

comment:2 Changed 5 years ago by zzz

  • Component changed from unspecified to router/netdb
  • Milestone changed from 0.9.10 to 0.9.11
  • Owner set to zzz
  • Priority changed from minor to blocker
  • Status changed from new to accepted
  • Version changed from 0.9.9 to 0.9.10

Rats, I really wish I had seen this before the release.

I agree with your analysis, looks like a transient error related to the client going away.

comment:3 Changed 5 years ago by zzz

  • Resolution set to fixed
  • Status changed from accepted to closed

Fixed in eb2820957208e17c76e8c10a2c36e59e0da61895 0.9.10-2

Note: See TracTickets for help on using tickets.