Yes, but in this case it will just treat Throwable as another parameter, not as an explicit Throwable object. So it will effectively just call Throwable.toString() (I believe). Passing it to the overload expecting a typed Throwable will ensure the exception is handled by the logger properly and all details displayed.

I would argue if an exception is thrown something bad has happened, and the more information you can log for the user the better. Anything that is not 'bad' should be handled internally and a nice log message generated.

The reason I made these changes was people were using the MQTT binding, getting issues when connecting to the broker, but due to the error handling never being informed of any specific details as to what the error was being caused by.