You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2004/03/28 23:51:45 UTC
DO NOT REPLY [Bug 28006] -
AsyncAppender: Dispatcher should run at normal prio
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28006>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28006
AsyncAppender: Dispatcher should run at normal prio
paul.smith@lawlex.com.au changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Normal |Critical
------- Additional Comments From paul.smith@lawlex.com.au 2004-03-28 21:51 -------
Ouch. We would appreciate a unified diff against the HEAD of log4j cvs if you
can.
I agree that a default of normal priority would be nice, however I am wondering
whether we should maintain the backward 'compatibility' and leave the default
priority as it is now, and we could expose the priority as a Javabean property
to be modified via the config. We would then need to document clearly the
limitations of the priority under stress.
If you have any time to create a junit test to reproduce the current problem
prior to the change and verify that the the change fixes the issue, that would
be even better! :)
cheers,
Paul Smith
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org