Loading... (original) (raw)
The test test/java/util/logging/TestLogConfigurationDeadLock.java attempts to detect deadlocks for
and
, but passes always whether the fix is present or not.
Recent sighting of
have shown that obtaining the deadlock is much frequent when creating a new logger whose parent does not exists yet, but has a level defined in the j.u.l config file.
A new test somewhat similar to TestLogConfigurationDeadLock - but using a configuration file defining levels for parent loggers should be added to obtain more testing coverage for the deadlock shown in
.