end users get confused when they see exception stacks printed in debug mode from JDK classes. Some equate it to a problem in the JDK libs.

example code :

632 KeyStore keyStore = null;
633 try {
634 keyStore = PolicyUtil.getKeyStore
635 (policy,
636 pp.getKeyStoreUrl(),
637 pp.getKeyStoreType(),
638 pp.getKeyStoreProvider(),
639 pp.getStorePassURL(),
640 debug);
641 } catch (Exception e) {
642 // ignore, treat it like we have no keystore
643 if (debug != null) {
644 e.printStackTrace();
645 }
646 }

We should be more clear and perhaps prepend such traces with a clue like "Running in debug mode and printing this stack trace for reference…"