-
Notifications
You must be signed in to change notification settings - Fork 306
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
CUSTOM-54: NullPointerException when JMX attribute is null #4365
Conversation
… rest-monitoring endpoint
@MarkWareham Added Unit tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test was successful, not sure with AssertJ usage, but ok.
<dependency> | ||
<groupId>org.glassfish</groupId> | ||
<artifactId>javax.json</artifactId> | ||
<version>1.1</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I though the org.glassfish:jakarta.json
pointed to the API, and not an actual implementation., as only the API artifacts should be 'jakartified'.
Fixed in new commit.
appserver/payara-appserver-modules/rest-monitoring/rest-monitoring-war/pom.xml
Outdated
Show resolved
Hide resolved
jenkins test please |
CUSTOM-54: NullPointerException when JMX attribute is null within the rest-monitoring endpoint
Description
This is a bug fix
When JMX attributes are null, it results in NPE when accessed from the rest-monitoring endpoint.
The fix checks if the attribute value is null and return JsonValue.NULL in that case instead of the 'generic' method who tries to convert the instance to a JsonValue.
Testing
Testing Performed
Manual testing
Testing Environment
Oracle 1.8.0_181 on Mac 10.14.6 with Maven 3.5.4
Documentation
N/A