Improve exception messages when cascading SSL derived exceptions
Debugging SSL issues during CN-to-MN communications can be difficult due to lack of pertinent information in the exception message body. Specifically, the Java SNI constraints in Java 7 result in a somewhat cryptic message: "handshake alert: unrecognized_name" (see below):
[ERROR] 2016-07-19 17:21:00,186 (ObjectListHarvestTask:retrieve:303) urn:node:mn
TestGRIIDC- <?xml version="1.0" encoding="UTF-8"?>
class org.dataone.client.exception.ClientSideException: /handsh
ake alert: unrecognized_name
Adding more specific information related to the upstream exception would be very helpful in debugging such issues.