Full exception details will be logged at debug level from the Java side - since we seem to prefer (manual) exception logging at the plugin level. We also make sure to log cause, if any, on the Ruby side which now catches all (expected) Java exceptions.
NOTE: we also avoid installing the bouncy-castle security provider at runtime, done previously
To be able to easily log full Java SSL exception details, we first move the SSL builder to Java.
otherwise this is ~ same as https://github.com/logstash-plugins/logstash-input-beats/pull/405 :
NOTE: we also avoid installing the bouncy-castle security provider at runtime, done previously
resolves https://github.com/logstash-plugins/logstash-input-tcp/issues/177