Opened 6 years ago

Last modified 6 years ago

#1694 testing defect

v0.9.22-19 SimpleTimer2 & "not possible to be in RUNNING"

Reported by: hummingbird Owned by: zzz
Priority: minor Milestone: 0.9.23
Component: api/utils Version: 0.9.22
Keywords: Cc:
Parent Tickets: Sensitive: no


A strange stuff (wrote in red) in
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(
at net.i2p.util.SimpleTimer2$TimedEvent?.run(
at java.util.concurrent.Executors$RunnableAdapter?.call(
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?$

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!


#1705: net.i2p.util.SimpleTimer2 : timer errortesting

Change History (10)

comment:1 Changed 6 years ago by hummingbird

Component: unspecifiedapi/utils
Owner: set to zzz
Status: newassigned

comment:2 Changed 6 years ago by zzz

version info please
as noted in #1672 there's been several fixes

comment:3 Changed 6 years ago by zzz

oh version info is in the title, n/m

comment:4 Changed 6 years ago by zzz

Milestone: undecided0.9.23
Status: assignedaccepted

Related to #1672 in that it's an error that was previously hidden, but a transport timer, not streaming. Probably related to reschedule() but not clear exactly.

comment:5 Changed 6 years ago by zzz

full version info please

comment:6 Changed 6 years ago by zzz

Status: acceptedtesting

I don't fully understand what's causing this, but taking a shot based on what's different about the OMR timer compared to most of the others - an out-of-thread reschedule.

Adding locking in 7c7c5cd7a371b07c27174d83ac90349e821d031f 0.9.22-22

comment:7 Changed 6 years ago by zzz

Add a subticket #1705.

comment:8 Changed 6 years ago by zzz

Status: testingneeds_work

comment:9 Changed 6 years ago by zzz

re: comment 5, see subticket for full version info, same OP

comment:10 Changed 6 years ago by zzz

Status: needs_worktesting

see #1705 for status

Note: See TracTickets for help on using tickets.