[
https://issues.apache.org/jira/browse/LOG4J2-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-3.
------------------------------
Resolution: Fixed
Fix Version/s: 2.0-alpha1
Assignee: Ralph Goers
In Log4j 2 the core components are designed to be immutable and thread safe.
However, annotations aren't being used since everything is expected to work
that way. I'm going to mark this as resolved, however feel free to reopen this
if you believe more needs to be done.
> Minimal (aka fine grained) locking
> ----------------------------------
>
> Key: LOG4J2-3
> URL: https://issues.apache.org/jira/browse/LOG4J2-3
> Project: Log4j 2
> Issue Type: Wish
> Components: Core
> Reporter: Curt Arnold
> Assignee: Ralph Goers
> Fix For: 2.0-alpha1
>
>
> Most components of log4j 1.2 are not inherently thread-safe but depend on
> locks that are acquired after the threshold check and are not released until
> processing is completed. Unless the AsyncAppender is used, this effectively
> limits log4j 1.2 to handlng only one logging request at a time.
> Core classes in log4j 2.0 should not depend on external synchronization for
> thread safety.
> Immutable classes should be preferred in the logging pipeline.
> Class attributes (aka @Immutable and @ThreadSafe) should be used to document
> thread-safety.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
