You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Thomas Neidhart (JIRA)" <ji...@apache.org> on 2013/01/13 19:06:12 UTC
[jira] [Commented] (LOGGING-135) Thread-safety improvements
[ https://issues.apache.org/jira/browse/LOGGING-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552264#comment-13552264 ]
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: https://issues.apache.org/jira/browse/LOGGING-135
> 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: http://www.atlassian.com/software/jira