commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Neidhart (JIRA)" <>
Subject [jira] [Commented] (LOGGING-135) Thread-safety improvements
Date Sun, 13 Jan 2013 18:06:12 GMT


Thomas Neidhart commented on LOGGING-135:

Can this really happen, as the logger field is set in the constructor?
A second thread would only be able to use the LogKitLogger object after it has been created.
> Thread-safety improvements
> --------------------------
>                 Key: LOGGING-135
>                 URL:
>             Project: Commons Logging
>          Issue Type: Bug
>            Reporter: Sebb
> The LogKitLogger.logger field is not final or volatile so changes are not guaranteed
to be published.
> This includes calls to getLogger(), so two different threads using the same instance
can theoretically both create the logger.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message