Fixing NullPointerException with jboss_wildfly integration and user/password not set #546
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rayz
approved these changes
Nov 7, 2024
aliciascott
approved these changes
Nov 7, 2024
carlosroman
deleted the
carlosroman/AMLII-2162-jmx.remote.credentials_NullPointerException
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should fix #545 as we now check if user or password no
nullbefore settingjmx.remote.credentials.According to the docs, the
CREDENTIALSattribute specifies the authentication credentials to be used in establishing a connection. They should be a user name and password as the corresponding value passed toCREDENTIALSis a 2–element string array containing the user name at index 0 and the password at index 1.