-
Bug
-
Resolution: Fixed
-
P4
-
None
-
b25
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8362777 | repo-phoenix | Daniel Daugherty | P4 | Resolved | Fixed | master |
If an incorrect system property for locale providers is set, it should be logged and presetned to the user, but it's not in reality. There's such code in LocaleProvderAdapter static initializer:
---
} catch (IllegalArgumentException | UnsupportedOperationException e) {
// could be caused by the user specifying wrong
// provider name or format in the system property
LocaleServiceProviderPool.config(LocaleProviderAdapter.class, e.toString());
}
---
However, this ends up in jdk.internal.logger.SurrogateLogger which only logs JUL_DEFAULT_LEVEL( = PlatformLogger.Level.INFO) or more severe ones, ie., the message, which is CONFIG, will never be logged.
---
} catch (IllegalArgumentException | UnsupportedOperationException e) {
// could be caused by the user specifying wrong
// provider name or format in the system property
LocaleServiceProviderPool.config(LocaleProviderAdapter.class, e.toString());
}
---
However, this ends up in jdk.internal.logger.SurrogateLogger which only logs JUL_DEFAULT_LEVEL( = PlatformLogger.Level.INFO) or more severe ones, ie., the message, which is CONFIG, will never be logged.
- backported by
-
JDK-8362777 Incorrect locale provider preference is not logged
-
- Resolved
-