Opened 9 years ago

Closed 9 years ago

#848 closed defect (fixed)

SimpleTimer2: Connection exited unexpectedly

Reported by: DISABLED Owned by: HungryHobo
Priority: major Milestone: 0.9.5
Component: apps/plugins Version: 0.9.4
Keywords: Cc:
Parent Tickets: Sensitive: no


CRIT [mer kUdx ¼] net.i2p.util.SimpleTimer2 : Streaming Timer kUdx: Timed task net.i2p.client.streaming.Connection$ActivityTimer?@136b519 exited unexpectedly, please report


Change History (5)

comment:1 Changed 9 years ago by DISABLED

I2P version: 0.9.4-3
Java version: Oracle Corporation 1.7.0_09 (OpenJDK Runtime Environment 1.7.0_09-b30)
Wrapper version: 3.5.17
Server version: 6.1.26
Servlet version: Jasper JSP 2.1 Engine
Platform: Linux i386 3.6.5-linode47
Processor: Core i7 (45nm) (corei)
Jbigi: Locally optimized native BigInteger? library loaded from file
Encoding: ANSI_X3.4-1968
Charset: US-ASCII

comment:2 Changed 9 years ago by DISABLED

comment:3 Changed 9 years ago by zzz

Component: unspecifiedapps/plugins
Owner: set to HungryHobo
Status: newassigned

OP had some info in IRC on another paste http://pastethis.i2p/show/2635/ that indicates he was running bote. As seen there, he was OOMing massively. Unfortunately he stopped bote before he took the thread dump. The good news is that there's nothing left of bote on the dump, so it stopped cleanly. The bad news is there's nothing left to look at.

Assigning to HH as there are lots of similar tickets about bote problems, although that's just a guess, and there's probably not enough to go on with the info here now. @OP if it happens again, please get a thread dump before you stop bote.

comment:4 Changed 9 years ago by HungryHobo

There are 66 StreamForwarder? threads in the stack trace. Could they have been started by bote? If so, it must have been an older build.

Please include the build number if this happens again.

comment:5 Changed 9 years ago by HungryHobo

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.