java.lang.IllegalStateException

Timer already cancelled.

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web153

  • via GitHub by mhilbush
    ,
  • Stack trace

    • java.lang.IllegalStateException: Timer already cancelled. at java.util.Timer.sched(Timer.java:397)[:1.8.0_91] at java.util.Timer.schedule(Timer.java:208)[:1.8.0_91] at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager.startTransactionTimer(ZWaveTransactionManager.java:509)[188:org.openhab.binding.zwave:2.0.0.201609251032] at org.openhab.binding.zwave.internal.protocol.ZWaveTransactionManager.queueTransactionForSend(ZWaveTransactionManager.java:190)[188:org.openhab.binding.zwave:2.0.0.201609251032] at org.openhab.binding.zwave.internal.protocol.ZWaveController.enqueue(ZWaveController.java:493)[188:org.openhab.binding.zwave:2.0.0.201609251032] at org.openhab.binding.zwave.internal.protocol.ZWaveController.sendData(ZWaveController.java:1043)[188:org.openhab.binding.zwave:2.0.0.201609251032] at org.openhab.binding.zwave.handler.ZWaveControllerHandler.sendData(ZWaveControllerHandler.java:634)[188:org.openhab.binding.zwave:2.0.0.201609251032] at org.openhab.binding.zwave.handler.ZWaveThingHandler$1.run(ZWaveThingHandler.java:392)[188:org.openhab.binding.zwave:2.0.0.201609251032] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_91] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)[:1.8.0_91] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)[:1.8.0_91] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)[:1.8.0_91] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_91] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_91] at java.lang.Thread.run(Thread.java:745)[:1.8.0_91]

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    mauritiusmauritius
    35 times, last one
    poroszdporoszd
    2 times, last one
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    bpbhat77bpbhat77
    Once,
    6 more bugmates