|
CVS commit messages
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=log4cxx-dev@logging.apache.org&msgNo=361 http://nagoya.apache.org/eyebrowse/ReadMsg?listName=log4cxx-dev@logging.apache.org&msgNo=362 http://nagoya.apache.org/eyebrowse/ReadMsg?listName=log4cxx-dev@logging.apache.org&msgNo=364 To avoid deadlocks, log4cxx::helpers::Mutex currently specifies nestable mutexes. It should not require much additional effort to eliminate nesting of mutex locks and allow use of platform optimial mutexes. Most of the network related appenders had substantial changes, but only the socket appender has sufficient unit tests to have confident that the changes weren't seriously damaging. AsynchAppender will lock up in Windows when the queue is full (occurs in test3), but not in Linux. Will need to research using newly released APR 1.01 and either correct or log APR bug. Have modified Makefile.am. Hard coded APR location as /usr/local/apr-1. APR apparently has a script that can be used to generate appropriate include and library paths, but I'm not very good with Autogen et al and would appreciate assistance. Atomic operations on Linux using APR appeared to be using mutexes instead of in-line assembler. Will need to research with APR 1.01.
Thread-specific data migrated to APR on 3 Jan 2005. Need to add tests to both log4j and log4cxx to make sure they work.
|
||||||||||||||||||||||||||||||||||||||||||||||||||
Solaris: http://nagoya.apache.org/eyebrowse/ReadMsg?listName=log4cxx-user@logging.apache.org&msgId=1895759
Thread name: http://nagoya.apache.org/eyebrowse/ReadMsg?listName=log4cxx-user@logging.apache.org&msgId=1629914