On Thu, Feb 2, 2017 at 11:25 AM, Andreas Mandel <[email protected]> wrote: > the exception appears in the log but is not > carried as root cause of the caught IOException any more. I did not find a > way to get the "cause" exception based on the references at hand. I also do > not know if this changed behavior of remoting is by intention
Not that I know of. Possibly a Remoting bug. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr23wsrNFy_BzGFCORLcQOx27tyL%3D2U%3DH%3Dy_KZSi0HeJ_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
