-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE when com.sun.identity.util.debug.provider is Invalid #41
Comments
This is really dumb... ROFL. The reason for the NPE is that the initialization of the In short, the debug provider is |
Kortanul
added a commit
to Kortanul/wrenam
that referenced
this issue
Mar 2, 2019
- Ensure that debug provider fallback is in place BEFORE trying to log any exceptions about failing to initialize the debug provider. - Upgrade `openam-shared` to JDK 8+ (see below). - Clean-up debug provider initialization. - Switch to multi-catch instead of repetitive `catch` blocks (JDK 7+). - Pull-in `forgerock-guava-base` to allow us to use `Strings.isNullOrEmpty()`. - Switch to `Optional` to support chaining `trim()` on provider names without an explicit `null` check (JDK 8+).
Kortanul
added a commit
to Kortanul/wrenam
that referenced
this issue
Mar 2, 2019
- Ensure that debug provider fallback is in place BEFORE trying to log any exceptions about failing to initialize the debug provider. - Upgrade `openam-shared` to JDK 8+ (see below). - Clean-up debug provider initialization. - Switch to multi-catch instead of repetitive `catch` blocks (JDK 7+). - Pull-in `forgerock-guava-base` to allow us to use `Strings.isNullOrEmpty()`. - Switch to `Optional` to support chaining `trim()` on provider names without an explicit `null` check (JDK 8+). Closes WrenSecurity#41.
Kortanul
added a commit
to Kortanul/wrenam
that referenced
this issue
Mar 2, 2019
- Ensure that debug provider fallback is in place BEFORE trying to log any exceptions about failing to initialize the debug provider. - Upgrade `openam-shared` to JDK 8+ (see below). - Clean-up debug provider initialization. - Switch to multi-catch instead of repetitive `catch` blocks (JDK 7+). - Pull-in `forgerock-guava-base` to allow us to use `Strings.isNullOrEmpty()`. - Switch to `Optional` to support chaining `trim()` on provider names without an explicit `null` check (JDK 8+). Closes WrenSecurity#41.
Kortanul
added a commit
to Kortanul/wrenam
that referenced
this issue
Mar 2, 2019
- Ensure that debug provider fallback is in place BEFORE trying to log any exceptions about failing to initialize the debug provider. - Upgrade `openam-shared` to JDK 8+ (see below). - Clean-up debug provider initialization. - Switch to multi-catch instead of repetitive `catch` blocks (JDK 7+). - Pull-in `forgerock-guava-base` to allow us to use `Strings.isNullOrEmpty()`. - Switch to `Optional` to support chaining `trim()` on provider names without an explicit `null` check (JDK 8+). Closes WrenSecurity#41.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Affected Versions
sustaining/13.5.x
, at 772b7a7)Summary
If you specify a custom class name for
com.sun.identity.util.debug.provider
when running Tomcat, and that class name is invalid, AM fails to start with an NPE instead of recovering gracefully.Steps to Reproduce
CATALINA_OPTS
for AM to include the following:webapps
folder.Expected Results
Actual Results
The text was updated successfully, but these errors were encountered: