logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 51612] LoggingEvent can contain wrong thread name in multithreaded environment
Date Thu, 11 Aug 2011 14:48:21 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=51612

--- Comment #2 from RJoker <r_gorbonosov@mail.ru> 2011-08-11 14:48:21 UTC ---
Thanks for the answer, Curt.

Just to make sure the solution which is used in AsyncAppender is bullet-proof.
As I mentioned, LoggingEvent.threadName is not volatile and access to it is not
synchronized. So, where is the guarantee that after being initialized in one
thread (with event.getThreadName()) it is visible to other threads as well
(dispatcher in case of AsyncAppender)?
Does the guarantee come from the piggybacking on synchronization on buffer?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message