A "Scanner" instance in the ExecuteServiceImpl class is not properly closed: possible resource leak
Steps to reproduce
This bug does not cause any visible issues, but Eclipse has warned me of the possible resource leak while I reviewed a pull request. The fix is easy enough and we can save ourselves from trouble down the road.