Apparently using LOG.exception here raises another exception.
    
    So demoting to use LOG.debug instead of LOG.exception.
    
    The error has been reported by email and this fix has been tested and
    does solve the issue (although, it's an odd one, granted).