https://issues.apache.org/bugzilla/show_bug.cgi?id=46129
Gertjan Donkers <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
--- Comment #2 from Gertjan Donkers <[EMAIL PROTECTED]> 2008-10-30 18:30:58
PST ---
OK, you are right that the problem does not manifest itself in the standard
log4j AsyncAppender. We were using our own asyncappender because we use the
log4j.properties format for configuration (which does not allow for log4j
AsyncAppender to be used to my knowledge).
I still think the thread name should be captured when constructing the
LoggingEvent though. The way the asyncappender gets around it now is a bit
dodgy, calling a getter to set state and all that.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
