On Fri, 2004-09-17 at 11:35, Elias Ross wrote: > If this is a concern, you might want to create some sort of semaphore so > that when an event is being logged, the appender state can't be > affected. However, as many concurrent events can be logged at the same > time. >
Instead of a semaphore, what I really was thinking of was a read-write lock. Somewhat paradoxically, the doAppend routine would hold a read lock, and any attempt to modify the state of the logger would require a write lock. It seems like Log4J already has a cheap one that should do the job. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
