Details
-
Bug
-
Status: Resolved
-
Trivial
-
Resolution: Fixed
-
None
-
None
Description
In the debug log, I saw this benign NullPointerException - the exception is caught and logged as a warning, and not propagated any further.
This was with 0.9.0-SNAPSHOT, as at 25th January 2016.
2016-02-12 11:18:22,934 WARN o.a.b.l.ssh.SshMachineLocation [brooklyn-execmanager-ZFqOzngN-1177]: Problem cleaning up ssh-pool-cache java.lang.NullPointerException: null at org.apache.brooklyn.location.ssh.SshMachineLocation$11$1.call(SshMachineLocation.java:463) [brooklyn-core-0.9.0-20160125.1743-p1.jar:0.9.0-20160125.1743-p1] at org.apache.brooklyn.location.ssh.SshMachineLocation$11$1.call(SshMachineLocation.java:457) [brooklyn-core-0.9.0-20160125.1743-p1.jar:0.9.0-20160125.1743-p1] at org.apache.brooklyn.util.core.task.BasicExecutionManager$ScheduledTaskCallable$1.call(BasicExecutionManager.java:416) [brooklyn-core-0.9.0-20160125.1743-p1.jar:0.9.0-20160125.1743-p1] at org.apache.brooklyn.util.core.task.BasicExecutionManager$SubmissionCallable.call(BasicExecutionManager.java:499) [brooklyn-core-0.9.0-20160125.1743-p1.jar:0.9.0-20160125.1743-p1] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_95] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_95] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_95] at java.lang.Thread.run(Thread.java:745) [na:1.7.0_95]