Save This Page
Home » apache-log4j-1.2.15 » org.apache » log4j » [javadoc | source]
org.apache.log4j
class: Dispatcher [javadoc | source]
java.lang.Object
   java.lang.Thread
      org.apache.log4j.Dispatcher

All Implemented Interfaces:
    Runnable

Deprecated! Since - 1.3.

Obsolete AsyncAppender dispatcher provided for compatibility only.
Field Summary
 AsyncAppender container     
Fields inherited from java.lang.Thread:
MIN_PRIORITY,  NORM_PRIORITY,  MAX_PRIORITY
Constructor:
 Dispatcher(BoundedFIFO bf,
    AsyncAppender container) 
    Parameters:
    bf -
    container -
Method from org.apache.log4j.Dispatcher Summary:
close,   run
Methods from java.lang.Thread:
activeCount,   checkAccess,   countStackFrames,   currentThread,   destroy,   dumpStack,   enumerate,   getAllStackTraces,   getContextClassLoader,   getDefaultUncaughtExceptionHandler,   getId,   getName,   getPriority,   getStackTrace,   getState,   getThreadGroup,   getUncaughtExceptionHandler,   holdsLock,   interrupt,   interrupted,   isAlive,   isDaemon,   isInterrupted,   join,   join,   join,   resume,   run,   setContextClassLoader,   setDaemon,   setDefaultUncaughtExceptionHandler,   setName,   setPriority,   setUncaughtExceptionHandler,   sleep,   sleep,   start,   stop,   stop,   suspend,   toString,   yield
Methods from java.lang.Object:
equals,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from org.apache.log4j.Dispatcher Detail:
  void close() 
      Deprecated!
 public  void run() 
      Deprecated!
    The dispatching strategy is to wait until there are events in the buffer to process. After having processed an event, we release the monitor (variable bf) so that new events can be placed in the buffer, instead of keeping the monitor and processing the remaining events in the buffer.

    Other approaches might yield better results.