Opened 10 years ago
Closed 9 years ago
#355 closed defect (worksforme)
java.io.IOException: Inactivity timeout ???
Reported by: | DISABLED | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 0.8.3 |
Component: | streaming | Version: | 0.8.1 |
Keywords: | Cc: | ||
Parent Tickets: | Sensitive: | no |
Description (last modified by )
I2P version: 0.8.1-37-rc
Java version: Sun Microsystems Inc. 1.6.0_20 (Java™ SE Runtime Environment 1.6.0_20-b02)
Platform: Linux amd64 2.6.28-19-generic
Processor: uninitialized (athlon64)
Jbigi: Locally optimized native BigInteger? library loaded from the library path
Encoding: UTF-8
2010/12/13 14:00:54 | java.io.IOException: Inactivity timeout 2010/12/13 14:00:54 | at net.i2p.client.streaming.Connection$ActivityTimer.timeReached(Connection.java:944) 2010/12/13 14:00:54 | at net.i2p.util.SimpleTimer2$TimedEvent.run(SimpleTimer2.java:220) 2010/12/13 14:00:54 | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 2010/12/13 14:00:54 | at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 2010/12/13 14:00:54 | at java.util.concurrent.FutureTask.run(FutureTask.java:138) 2010/12/13 14:00:54 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) 2010/12/13 14:00:54 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207) 2010/12/13 14:00:54 | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 2010/12/13 14:00:54 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 2010/12/13 14:00:54 | at java.lang.Thread.run(Thread.java:619)
Subtickets
Change History (3)
comment:1 Changed 10 years ago by
Component: | router/general → streaming |
---|---|
Milestone: | → 0.8.3 |
comment:2 Changed 10 years ago by
Description: | modified (diff) |
---|
I'm not sure if I fixed this or not. Due to the way the exception is generated at a different place from where it is thrown, it's difficult to see where this needs to be caught. It looks like the error was copied from your wrapper log, which means it was a critical error, but I really need the class name from the router log to see where to catch this.
comment:3 Changed 9 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
No response and not seen by others, closing for now, please reopen if it occurs again.
this used to be hidden but due to some other changes it's visible now. I'll try to hide it again.