Adding SocketChannel toString to connection exception messages (original) (raw)
Alan Bateman Alan.Bateman at oracle.com
Tue Jan 2 16:35:03 UTC 2018
- Previous message: RFR [11] JDK-8179424: Remove terminally deprecated sun.reflect.Reflection.getCallerClass
- Next message: Adding SocketChannel toString to connection exception messages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 29/12/2017 00:33, Steven Schlansker wrote:
Thanks for the discussion!
So, it sounds like amending the message by default is going to be a non-starter -- but at least adding the information otherwise might be possible. There are examples in other area where exceptions include detail information (for diagnostics purposes) when not running with a security manager. This may be something to look at here (and easy to try out too as it wouldn't require touching any native code either).
-Alan
- Previous message: RFR [11] JDK-8179424: Remove terminally deprecated sun.reflect.Reflection.getCallerClass
- Next message: Adding SocketChannel toString to connection exception messages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]