Shawn Ellis created RIVER-467: --------------------------------- Summary: NullPointerException when JoinManager is terminating Key: RIVER-467 URL: https://issues.apache.org/jira/browse/RIVER-467 Project: River Issue Type: Bug Components: com_sun_jini_lookup Affects Versions: River_3.0.0 Reporter: Shawn Ellis Attachments: LeaseRenewalManager-NPE-1.patch
Every now and then I would encounter a NullPointerException with the JoinManager. The way that I was able to reproduce this problem was to have a service up and running and then switch the network on my laptop. For example, I would switch from one wifi network to another. I've attached a patch that protects against the NullPointerException and seems to work fine when switching networks. [^LeaseRenewalManager-NPE-1.patch] {code:java} Oct 7 14:8:28 CDT SEVERE:thr 652:Exception in thread "LeaseRenewalManager_thread-3" Oct 7 14:8:28 CDT SEVERE:thr 652:java.lang.NullPointerException Oct 7 14:8:28 CDT SEVERE:thr 652: at net.jini.lookup.JoinManager$ProxyReg.terminate(JoinManager.java:1266) Oct 7 14:8:28 CDT SEVERE:thr 652: at net.jini.lookup.JoinManager.removeTasks(JoinManager.java:2774) Oct 7 14:8:28 CDT SEVERE:thr 652: at net.jini.lookup.JoinManager.access$400(JoinManager.java:456) Oct 7 14:8:28 CDT SEVERE:thr 652: at net.jini.lookup.JoinManager$ProxyReg$DiscLeaseListener.notify(JoinManager.java:1188) Oct 7 14:8:28 CDT SEVERE:thr 652: at net.jini.lease.LeaseRenewalManager.tell(LeaseRenewalManager.java:1412) Oct 7 14:8:28 CDT SEVERE:thr 652: at net.jini.lease.LeaseRenewalManager.access$500(LeaseRenewalManager.java:322) Oct 7 14:8:28 CDT SEVERE:thr 652: at net.jini.lease.LeaseRenewalManager$RenewTask.run(LeaseRenewalManager.java:451) Oct 7 14:8:28 CDT SEVERE:thr 652: at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135) Oct 7 14:8:28 CDT SEVERE:thr 652: at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) Oct 7 14:8:28 CDT SEVERE:thr 652: at java.base/java.lang.Thread.run(Thread.java:844) {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)