v0.9.22-19 SimpleTimer2 & "not possible to be in RUNNING"
Opened 6 years ago
Last modified 5 years ago
#1694testingdefect
v0.9.22-19 SimpleTimer2 & "not possible to be in RUNNING"
Reported by:hummingbirdOwned by:zzz Priority: minor Milestone: 0.9.23 Component: api/utils Version: 0.9.22 Keywords:
Cc:
Parent Tickets:
Sensitive: no
Description
A strange stuff (wrote in red) in http://127.0.0.1:7657/logs
Perhaps related to the changes made after this issue: http://trac.i2p2.i2p/ticket/1672
27/10/15 00:41:02 ↓↓↓ 1 similar message omitted ↓↓↓
27/10/15 00:41:02 ERROR [leTimer2 4/4] net.i2p.util.SimpleTimer2 : timer error
java.lang.IllegalStateException?: net.i2p.router.transport.OutboundMessageRegistry?$CleanupTask?@115f60c0 not possible to be in RUNNING
at net.i2p.util.SimpleTimer2$TimedEvent?.run2(SimpleTimer2.java:418)
at net.i2p.util.SimpleTimer2$TimedEvent?.run(SimpleTimer2.java:397)
at java.util.concurrent.Executors$RunnableAdapter?.call(Executors.java:471)
at java.util.concurrent.FutureTask?.run(FutureTask?.java:262)
at java.util.concurrent.ScheduledThreadPoolExecutor?$ScheduledFutureTask?.access$201(ScheduledThreadPoolExecutor?.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor?$ScheduledFutureTask?.run(ScheduledThreadPoolExecutor?.java:292)
at java.util.concurrent.ThreadPoolExecutor?.runWorker(ThreadPoolExecutor?.java:1145)
at java.util.concurrent.ThreadPoolExecutor?$Worker.run(ThreadPoolExecutor?.java:615)
at java.lang.Thread.run(Thread.java:745)
26/10/15 17:13:40 ERROR [ms #45673]: ] lient.impl.I2PSessionMuxedImpl: Error: message 30947273 already received!
26/10/15 17:13:40 ERROR [ms #45673]: ] lient.impl.I2PSessionMuxedImpl: Receive message 30947273 had no matches
26/10/15 17:13:40 ERROR [ms #45673]: ] lient.impl.I2PSessionMuxedImpl: Error: message 30947271 already received!
Subtickets
#1705: net.i2p.util.SimpleTimer2 : timer errortesting