-
Bug
-
Resolution: Fixed
-
P4
-
8, 11, 12
-
b10
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8233979 | 11.0.6 | Daniel Fuchs | P4 | Resolved | Fixed | b04 |
A DESCRIPTION OF THE PROBLEM :
The JavaDoc of this method states that "It will return false if the {@code LogRecord} is null.", but there is no null-check. Instead in the second line of the method a call is done on the log record, resulting in NPE.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Call java.util.logging.Handler#isLoggable with null argument.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
false
ACTUAL -
NullPointerException
CUSTOMER SUBMITTED WORKAROUND :
Override the method in every handler and add a null-check
FREQUENCY : always
The JavaDoc of this method states that "It will return false if the {@code LogRecord} is null.", but there is no null-check. Instead in the second line of the method a call is done on the log record, resulting in NPE.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Call java.util.logging.Handler#isLoggable with null argument.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
false
ACTUAL -
NullPointerException
CUSTOMER SUBMITTED WORKAROUND :
Override the method in every handler and add a null-check
FREQUENCY : always
- backported by
-
JDK-8233979 NullPointerException in java.util.logging.Handler#isLoggable
- Resolved