Closed cweitkamp closed 5 years ago
As a side note: I didn't find time to replace the ExpiringCacheAsync with the ESH implementation (see https://github.com/openhab/openhab2-addons/pull/2765#pullrequestreview-75794884). Maybe someone can give me a hand on that.
Another one:
2018-04-19 08:51:34.243 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception
java.lang.NullPointerException: null
at java.util.LinkedList$ListItr.next(LinkedList.java:893) ~[?:?]
at org.openhab.binding.network.internal.toberemoved.cache.ExpiringCacheAsync.setValue(ExpiringCacheAsync.java:90) ~[?:?]
at org.openhab.binding.network.internal.PresenceDetection.submitFinalResult(PresenceDetection.java:321) ~[?:?]
at org.openhab.binding.network.internal.PresenceDetection.waitForPresenceDetection(PresenceDetection.java:350) ~[?:?]
at org.openhab.binding.network.internal.PresenceDetection.performPresenceDetection(PresenceDetection.java:288) ~[?:?]
at org.openhab.binding.network.internal.PresenceDetection.lambda$4(PresenceDetection.java:479) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]
The OP NPE is fixed in the lasted code base. Closing this now. If the second NPE still (which might be related) still occurs, please reopen.
@davidgraeff Agreed. They never occurred again.
Do you think we can at least take care of the replacement for the "toberemoved" class (ExpiringCacheAsync)?
My next round of fixing will be MQTT related, the network binding is like super low on my priority list atm. But yeah at some point that class should go.
You will see this NPE whenever a hostname cannot be resolved to an IP address (e.g. if you configure an unknown hostname).
On initialization of the ThingHandler we see an ERROR log which should be reduced to DEBUG level: