> You're correct. Should I just include e.toString() or e.getMessage() there?
Probably e.getMessage(). Please run some tests to see how it looks after the patch.
> I think there are a couple of other places where the exception might get printed more than once. Should those be fixed as part of this jira, or filed separately?
It would be great if you can fix it separately.
> Finally, do you know why some stack traces are printed out by using stringifyException() and others are printed by just passing the exception to the LOG.error() function?
If I remember correctly, the previous log API did not have methods for printing exceptions, i.e. the only have log.info(message) but not log.info(message, exception). So we have to use stringifyException(). From now on, we should not use stringifyException().