On Mon, 20 Apr 2026 19:34:07 GMT, Weijun Wang <[email protected]> wrote:
>> src/java.security.jgss/share/classes/sun/security/krb5/KrbServiceLocator.java
>> line 190:
>>
>>> 188: }
>>> 189: } catch (NamingException e) {
>>> 190: throw e;
>>
>> Do you really want to include the reason in the final exception, or just
>> printing out them when `-Dsun.security.krb5.debug=true` is set?
>
> Not sure which you prefer. If just debug log, it will be much simpler. No
> need to chain cause, no need to sanitize exception messages...
having the cause attached without needing to have debbuging enabled can be
benifical as no JVM restart is required which can be diffucult in some
production enviroments, however JDK-8381014 will tackle this issue once
integrated. So I am happy to just output as a debug log if preffered?
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/30824#discussion_r3115575426
