[Bug classpath/35974] New: Deadlock in java.util.logging.Logger

[neugens at limasoftware dot net]

The class java.util.logging.Logger deadlocks when two threads try to access
concurrently some of its methods.

The problem is that when a thread tries to get the logger, it lock on the
LogManager and then the calls getResourceBundleName which is synchronized at
method level. A thread then may log an event, asking for a lock on the
LogManager which is cannot be released, because, again, log is synchronized at
method level.

Introducing a lock object is a better practice and ensures that this kind of
synchronization issues never happens. A better approach would be to use the
Concurrent API, but this can be costly on some runtimes in term of performance.

A fix and a mauve test case are in CVS for this issue.


-- 
           Summary: Deadlock in java.util.logging.Logger
           Product: classpath
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: classpath
        AssignedTo: neugens at limasoftware dot net
        ReportedBy: neugens at limasoftware dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35974