http://blog.gmane.org/gmane.comp.apache.logging.log4cxx.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2444 Hi All, I'am currently working with log4cxx 0.10.0 on W-XP using MSVC 2005 Group Edition. The problem I have is the following. I use an AnsycAppender which uses an XMLSocketAppender to publish events. When my application is going to terminate in the main method and no event was send to the server (chainsaw at the moment), the application hangs while performing "LogManager::shutdown();" and does not terminate. What I figured out so far is, that the XMLLayout is using "log4cxx::helpers::Transform::appendEscapingCDATA" which initialises some static variables. This initialisation interferes with an "atexit" handler. The result is, that appendEscapingCDATA never returns. Hence, the thread of the AsyncAppender never returns and the whole application does not terminate. A remedy is to perform the initialisation in advance, like this: { LogString buf; LogString input; log4cxx::helpers::Transform::appendEscapingCDATA(buf, input); } This helps, but is not very intentional. Are there nicer solutions available (a sleep also works, but one needs different periods in RELEASE/DEBUG mode)? Cheers Stefan Stefan.Borovac< at >t-online.de 2008-09-04T13:20:34 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2440 Hello, I noticed that log4cxx (SVN r677817) crashes (Segmentation Fault) when trying to log from an exit-handler. The code below reproduces the crash: #include <stdlib.h> #include <log4cxx/logger.h> #include <log4cxx/basicconfigurator.h> static log4cxx::LoggerPtr log; static void cleanup() { LOG4CXX_DEBUG(log, "Oops..."); } int main(int argc, char **argv) { atexit(cleanup); log4cxx::BasicConfigurator::configure(); log = log4cxx::Logger::getLogger("main"); atexit(cleanup); return 0; } Is this a bug in log4cxx or should one expect this behavior? If its expected: Is there a workaround for this problem (getting rid of 'atexit()' is not an option...). Thanks, - Michel Michel Marti 2008-08-29T19:46:54 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2437 I am trying to build log4cxx 0.10.0 using ant, but the build fails because of apr-util compilation errors. Am I doing something wrong here? I am using the following environment: Micosoft Windows XP SP2 Microsoft Visual C/C++ 6.0 SP 6 Microsoft Platform SDK Feb. 2003 Apache Ant 1.7.1 AntContrib 1.0b3 CppTasks 1.0b5 log4cxx 0.10.0 apr 1.3.3 apr-util 1.3.4 The compilation errors are all from apr_dbd_odbc.c: [cc] apr_dbd_odbc.c [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(68) : error C2061: syntax error : identifier 'henv' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(68) : error C2059: syntax error : ';' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(68) : error C2513: '/*global*/ ' : no variable declared before '=' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(72) : error C2146: syntax error : missing ')' before identifier 'rc' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(72) : error C2081: 'SQLRETURN' : name in formal parameter list illegal [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(72) : error C2061: syntax error : identifier 'rc' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(72) : error C2059: syntax error : ';' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(72) : error C2059: syntax error : ',' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(73) : error C2059: syntax error : ')' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(106) : error C2061: syntax error : identifier 'SQLHANDLE' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(118) : error C2059: syntax error : '}' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(122) : error C2061: syntax error : identifier 'SQLHANDLE' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(123) : error C2061: syntax error : identifier 'dbc' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(123) : error C2059: syntax error : ';' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(130) : error C2143: syntax error : missing '{' before '*' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(131) : error C2143: syntax error : missing '{' before '*' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(132) : error C2143: syntax error : missing '{' before '*' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(133) : error C2143: syntax error : missing '{' before '*' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(134) : error C2143: syntax error : missing '{' before '*' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(140) : error C2059: syntax error : '}' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(154) : error C2061: syntax error : identifier 'SQLHANDLE' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(155) : error C2061: syntax error : identifier 'dbc' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(155) : error C2059: syntax error : ';' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(158) : error C2059: syntax error : '}' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(161) : error C2061: syntax error : identifier 'SQLHANDLE' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(163) : error C2059: syntax error : '}' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(166) : error C2061: syntax error : identifier 'SQLHANDLE' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(167) : error C2061: syntax error : identifier 'dbc' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(167) : error C2059: syntax error : ';' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(173) : error C2059: syntax error : '}' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(197) : error C2061: syntax error : identifier 'SQLSMALLINT' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(198) : error C2059: syntax error : '}' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(207) : error C2143: syntax error : missing '{' before 'const' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(208) : error C2065: 'SQL_C_DEFAULT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(208) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(209) : error C2065: 'SQL_C_STINYINT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(209) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(210) : error C2065: 'SQL_C_UTINYINT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(210) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(211) : error C2065: 'SQL_C_SSHORT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(211) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(212) : error C2065: 'SQL_C_USHORT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(212) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(213) : error C2065: 'SQL_C_SLONG' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(213) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(214) : error C2065: 'SQL_C_ULONG' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(214) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(215) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(216) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(217) : error C2065: 'SQL_C_SBIGINT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(217) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(218) : error C2065: 'SQL_C_UBIGINT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(218) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(219) : error C2065: 'SQL_C_FLOAT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(219) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(220) : error C2065: 'SQL_C_DOUBLE' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(220) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(221) : error C2065: 'SQL_C_CHAR' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(221) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(222) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(223) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(224) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(225) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(226) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(227) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(228) : error C2065: 'SQL_LONGVARBINARY' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(228) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(229) : error C2065: 'SQL_LONGVARCHAR' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(229) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(231) : error C2065: 'SQL_TYPE_NULL' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(231) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(234) : error C2143: syntax error : missing '{' before 'const' [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(235) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(236) : error C2065: 'SQL_TINYINT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(236) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(237) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(238) : error C2065: 'SQL_SMALLINT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(238) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(239) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(240) : error C2065: 'SQL_INTEGER' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(240) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(241) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(242) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(243) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(244) : error C2065: 'SQL_BIGINT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(244) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(245) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(246) : error C2065: 'SQL_FLOAT' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(246) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(247) : error C2065: 'SQL_DOUBLE' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(247) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(248) : error C2065: 'SQL_CHAR' : undeclared identifier [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(248) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(249) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(250) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(251) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(252) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(253) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(254) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(255) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(256) : error C2099: initializer is not a constant [cc] C:\Projects\HEAD\ExtLib\Log4cxx\apr-util\dbd\apr_dbd_odbc.c(256) : fatal error C1003: error count exceeds 100; stopping compilation Any help wuld be appreciated. Thanks, Moshe Moshe Matitya 2008-08-27T11:48:10 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2432 Hi All, I'am using log4cxx 0.10.0 and Chainsaw v2 as a server. On the Chainsaw side I'am using a SocketReceiver and a XMLSocketReceiver. Now I have three beginner questions concerning this setup. 1) The events logged by the XMLSocketReceiver are all written to the "chainsaw-log" tab. This is somehow ugly. Is it possible to set the "Application property" such that the XML messages are going to a different tab? I have found only vague descriptions on setting this property (even on the name of the key). 2) Question (1) is also a problem for the SocketReceiver, well different tabs are open for different remote hosts, but an application name is still missing. 3) While it was possible to send the "locationInfo" with the XMLSocketAppender, the same does not work on the SocketAppender/SocketReceiver pair, although the C++ code suggest that the location info is serialized. Any clou here? Any help is welcome! Cheers Stefan P.S.: Here is the Chainsaw config. <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE log4j:configuration > <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="true"> <appender name="A2" class="org.apache.log4j.ConsoleAppender"> <layout class="org.apache.log4j.SimpleLayout"/> </appender> <plugin name="SocketReceiver" class="org.apache.log4j.net.SocketReceiver" style="margin:0px;"> <param name="port" value="4560"/ style="margin:0px;"> <param name="name" value="mySocketReceiver"/ style="margin:0px;"> <param name="threshold" value="TRACE"/ style="margin:0px;"> </plugin> <plugin name="XMLSocketReceiver" class="org.apache.log4j.net.XMLSocketReceiver" style="margin:0px;"> <param name="decoder" value="org.apache.log4j.xml.XMLDecoder"/ style="margin:0px;"> <param name="port" value="4448"/ style="margin:0px;"> <param name="name" value="myXMLSocketReceiver"/ style="margin:0px;"> <param name="threshold" value="TRACE"/ style="margin:0px;"> </plugin> <root> <level value="debug"/> </root> </log4j:configuration> And here the C++ config on the client side: // XML socket stuff +++++++++++++++++++++++++++++++++++++++++++++++ XMLSocketAppenderPtr myXMLSocketAppender( new XMLSocketAppender( LOG4CXX_STR("XXX.XXX.XXX.XXX"), 4448 ) ); XMLLayoutPtr myXMLLayout( new XMLLayout() ); myXMLLayout->setLocationInfo(true); myXMLSocketAppender->setLayout(myXMLLayout); myXMLSocketAppender->activateOptions(pool); // plain socket stuff +++++++++++++++++++++++++++++++++++++++++++++++ SocketAppenderPtr mySocketAppender( new SocketAppender( LOG4CXX_STR("XXX.XXX.XXX.XXX"), 4560 ) ); mySocketAppender->activateOptions(pool); logger->addAppender(mySocketAppender); logger->addAppender(myXMLSocketAppender); logger->setLevel(log4cxx::Level::getDebug()); Stefan.Borovac< at >t-online.de 2008-08-19T13:26:46 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2431 Hi all, I am using a xml file to configure the logger. Here, the xml file needs the root node as <log4j:configuration> or <configuration>. I donot want the root node to be named as <log4j:configuration> or <configuration>, as my configuration file contains some other information also. Is this possible to keep the root node something other than <log4j:configuration> or <configuration>. Regards, Madhu Gowda Madhu Gowda 2008-08-19T06:21:37 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2421 We use the DailyRollingAppender, defined as follows in our config file: <appender name="FILE" class="org.jboss.logging.appender.DailyRollingFileAppender"> <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/> <param name="File" value="<logfile>"/> <param name="Append" value="true"/> <!-- Rollover at midnight each day --> <param name="DatePattern" value="'.'yyyy-MM-dd"/> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5p [%c{1}] %m%n"/> </layout> </appender> Several applications log to the same log file using this appender. What's happening is when the rollover occurs at midnight, some processes still log to the original file, which has now been renamed, whereas others log to the main log file as they should. I'm suspecting that this is an error on our part and we should not have multiple processes all log to the same file, although I've heard that others do this. What's the solution? Peter Steele 2008-08-15T15:59:01 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2420 Hi, I would like to integrate lib4cxx into my project, which uses automake for the build-process. How can I automatically detect if lib4cxx is installed and which lib and include flags I have to use? I am thinking of either a nice automake .m4 macro like the find_apr.m4, or a config program, which gives the needed information (e.g. pkg-config or apr-config). Best regards, Heiko Heiko Klein 2008-08-15T12:22:08 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2419 We are using a RollingFileAppender defined as follows: <appender name="FILE" class="org.apache.log4j.RollingFileAppender"> <param name="maxFileSize" value="200MB" /> <param name="maxBackupIndex" value="12" /> <param name="File" value="${LOGNAME}" /> <param name="Append" value="false"/> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d{MM-dd HH:mm:ss.SSS} %5p %c{1} - %m%n" /> </layout> </appender> This works the way we want with one exception: When our app that uses this appender starts up it overwrites the existing log file. This is of course because we have Append set to false. What we'd like to have happen is that if there is an existing log file have a rollover occur immediately so that no log data is lost. Can that be setup or is our only option is to set Append to true? Peter Steele 2008-08-14T17:24:04 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2418 Hi, Any idea if expat project inside apr-util, has a separate project called XML. Apr-util depends on expat libs or xml lib? Or under some condition? Jenica Mehta Mehta, Jenica 2008-08-13T14:19:41 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2417 Hey *, I have found the following two lines of code to adapt an existing FileAppender: Appender* appender = Logger::getRootLogger()->getAppender ("RollingFile"); FileAppender* fa = dynamic_cast<FileAppender*>(appender); But when I try to implement this functionylity in my method I get always an dynamic_cast exception, here is my code snippet: std::string errorLogFile = "test.log"; const log4cxx::LogString rootLoggerFileAppenderName = LOG4CXX_STR("RootLoggerFileAppender"); ... std::wstring logFilePathName(errorLogFile.begin(), errorLogFile.end()); log4cxx::Appender* rootFileAppender = log4cxx::Logger::getRootLogger()->getAppender(rootLoggerFileAppenderName ); if(rootFileAppender == 0 || rootFileAppender == NULL) { log4cxx::LogString logStringFormat = LOG4CXX_STR("[%-5p] - %m%n"); log4cxx::LayoutPtr layout(new log4cxx::PatternLayout(logStringFormat)); rootFileAppender = new log4cxx::FileAppender(layout, logFilePathName, true); rootFileAppender->setName(LOG4CXX_STR("RollingFile")); log4cxx::Logger::getRootLogger()->addAppender(rootFileAppender);} /* the following dynamic_cast throws an exception */ try { dynamic_cast<log4cxx::FileAppender*>(rootFileAppender)->setFile(logFileP athName); } catch(...) { log4cxx::Logger::getRootLogger()->removeAppender(rootLoggerFileAppenderN ame); log4cxx::BasicConfigurator::configure(); LOG4CXX_ERROR(m_logger, "FileAppender couldn't be configured for root logger, invalid log file specified: " << errorLogFile); LOG4CXX_ERROR(m_logger, "A ConsoleAppender was added to the root logger instead of the FileAppender."); return 1; } Where is my bug? Thanks for any respons Markus Eberhard, Markus (external 2008-08-07T14:15:49 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2413 Hello, I wish to setup my application to forward logs to a remote server. I was looking at the log4cxx distribution - no server binary is provided. How can I build such a server ? I'm sure there is a way to build a simple server given the log4cxx library, but it'll be nice if the distribution itself provides a server that one can forward to. - Mohit Mohit Aron 2008-08-04T04:37:36 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2412 Hello, I am in the process of upgrading from version 0.9.7 to 0.10.0 of the log4cxx library. I've successfully built the library and I am now in the process of integrating into our product. Some of the methods that we were previously calling have a new required log4cxx::helpers::Pool parameter. For example, we are calling the activateOptions() method on an log4cxx::AppenderPtr. From what I can tell, this appears to be a memory pool interface that log4cxx uses internally. What is the proper way to get this Pool object? Am I supposed to create one myself during initialization? I can't seem to find any mention of it in the documentation. Any help would be greatly appreciated. Best Regards, Chris D'Annunzio Chris D'Annunzio 2008-08-01T21:39:08 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2411 Hello everyone: My question is: - Has anyone built log4cxx 0.9.7 with MinGW 5.1.4 successfully before? // my compiling enviroment is similar as Olivier's (please check attached mail) What I've tried and learnt recently (correct me if I'm wrong) : #1 build log4cxx 0.9.7 needs pthread support // MSYS log ---------------------------------------------------------------- ... checking pthread.h usability... no checking pthread.h presence... no checking for pthread.h... no configure: error: pthread library not found ! ---------------------------------------------------------------- #2 MinGW 5.1.4 didn't ship pthread #3 I installed 3rd-party pthread (POSIX Threads for Win32) and when I make get following building error: // MSYS log ------------------------------------------------------------------------------------------------------------------------ if /bin/sh ../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I../include/log4cxx -I../include -D_REENTRANT -g -O2 -MT semaphore.lo -MD -MP -MF ".deps/semaphore.Tpo" \ -c -o semaphore.lo `test -f 'semaphore.cpp' || echo './'`semaphore.cpp; \ then mv ".deps/semaphore.Tpo" ".deps/semaphore.Plo"; \ else rm -f ".deps/semaphore.Tpo"; exit 1; \ fi g++ -DHAVE_CONFIG_H -I. -I. -I../include/log4cxx -I../include -D_REENTRANT -g -O2 -MT semaphore.lo -MD -MP -MF .deps/semaphore.Tpo -c semaphore.cpp -DDLL_EXPORT -DPIC -o .libs/semaphore.o In file included from semaphore.cpp:20: D:/MinGW/bin/../lib/gcc/mingw32/3.4.5/../../../../include/semaphore.h:149: error: `mode_t' has not been declared make[1]: *** [semaphore.lo] Error 1 make[1]: Leaving directory `/home/Isaac.Lee/log4cxx-0.9.7/src' make: *** [all-recursive] Error 1 ------------------------------------------------------------------------------------------------------------------------ #4 Yesterday I asked in MinGW user-list and get an answer from Giel: "Nope, MinGW stands for *Minimalistic* GNU for Windows, meaning it's meant to be just enough to communicate with the windows API and standard C & C++ libraries. Pthreads is part of POSIX and Windows isn't a POSIX system." So is it possible to build log4cxx 0.9.7 with MinGW 5.1.4 successfully? On 6/27/08, Olivier Beaton <olivier.beaton< at >gmail.com> wrote: Isaac 2008-08-01T06:44:22 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2409 Hi, I'm trying to compile log4cxx on Visual Studio 2008 Express Edition on Windows Vista. Thus far I've been following the instructions at: http://logging.apache.org/log4cxx/building/vstudio.html I've installed sed from: http://voxel.dl.sourceforge.net/sourceforge/gnuwin32/sed-4.1.5-setup.exe And added it to my path. I downloaded and unzipped apr-1.2.11-win32-src.zip, and apr-util-1.2.10-win32-src.zip, to the parent directory above my apache-log4cxx-0.10.0 directory. I also renamed both of the files to apr and apr-util respectively. I ran the configure, and configure-aprutil batch files. Finally when I got to the step "Building log4cxx.dll" in <a href="(http://logging.apache.org/log4cxx/building/vstudio.html)">the build instructions</a> I opened apache-log4cxx-0.10.0/projects/log4cxx.dsw and was presented with a message stating that I needed to upgrade the VCPP6 workspace to a 2008 Express Edition workspace, and I receive the following messages: <quote author="Visual C++ 2008 Express Edition Warning dialog..."> A Visual C++ project of the name 'apr.vcproj' already exists in the current format. Would you like to load the existing project instead? </quote> And I click "Yes" <quote author="Visual C++ 2008 Express Edition Warning dialog..."> A Visual C++ project of the name 'xml.vcproj' already exists in the current format. Would you like to load the existing project instead? </quote> And I click "Yes" again... <quote author="Visual C++ 2008 Express Edition Warning dialog..."> A Visual C++ project of the name 'aprutil.vcproj' already exists in the current format. Would you like to load the existing project instead? </quote> And I click "Yes" one more time... <quote author="Visual C++ 2008 Express Edition Warning dialog..."> A Visual C++ project of the name 'log4cxx.vcproj' already exists in the current format. Would you like to load the existing project instead? </quote> And I click "Yes" once again... Now my project workspace loads, I select log4cxx as the "startup project" and I build it. now I get the following errors in my output window: <quote author="output window"> 1>------ Build started: Project: apr, Configuration: Debug Win32 ------ 1>Compiling... 1>multicast.c 1>.\network_io\unix\multicast.c(137) : error C2079: 'mip' uses undefined struct 'group_source_req' 1>.\network_io\unix\multicast.c(168) : error C2224: left of '.gsr_interface' must have struct/union type 1>.\network_io\unix\multicast.c(168) : warning C4013: 'find_if_index' undefined; assuming extern returning int 1>.\network_io\unix\multicast.c(169) : error C2224: left of '.gsr_group' must have struct/union type 1>.\network_io\unix\multicast.c(169) : error C2224: left of '.gsr_group' must have struct/union type 1>.\network_io\unix\multicast.c(169) : error C2198: 'memcpy' : too few arguments for call 1>.\network_io\unix\multicast.c(170) : error C2224: left of '.gsr_source' must have struct/union type 1>.\network_io\unix\multicast.c(170) : error C2224: left of '.gsr_source' must have struct/union type 1>.\network_io\unix\multicast.c(170) : error C2198: 'memcpy' : too few arguments for call 1>Build log was saved at "file://c:\temp\apr\LibD\BuildLog.htm" 1>apr - 8 error(s), 1 warning(s) 2>------ Build started: Project: log4cxx, Configuration: Debug Win32 ------ 2>Linking... 2>LINK : fatal error LNK1181: cannot open input file '..\..\apr\libd\apr-1.lib' 2>Build log was saved at "file://c:\temp\apache-log4cxx-0.10.0\projects\Debug\BuildLog.htm" 2>log4cxx - 1 error(s), 0 warning(s) ========== Build: 0 succeeded, 2 failed, 2 up-to-date, 0 skipped ========== </quote> Could there be some reason why aprlib is not compiling? Andrew J. Leer 2008-07-31T13:48:56 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2406 I am interested in extending DailyRollingFileAppender. The existing appender can be configured to roll over at intervals like once a month, once a week, once a day, once a half-day (AM/PM), once a minute, etc. What I need is to be able to roll over at other intervals in between, such as every ten minutes. Does anyone know of an already-written appender that supports this? Alternatively, where can I find documentation of what I need to do to write a new appender (for log4cxx of course, as opposed to log4j), and what I'd need to change from DailyRollingFileAppender to support the added functionality? Thanks, Moshe Moshe Matitya 2008-07-29T11:48:39 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2404 Hi, Is there any way (other than changing the source code ) for configuring the SyslogAppender to be configured for forwarding the messages to any specified port so that a syslog server listening to any specific port which is non standard port(different than 514) can consume. I see the port defined at syslogwriter.cpp as follows : #define SYSLOG_PORT 514 Assumes that this is the only port that log4cxx forwards the logs for the syslog appender. Please let me know if there is any way. Regards Unni Unnikrishnan Udinoor 2008-07-26T01:31:30 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2400 Hi All, I'am planing to use log4cxx 0.10.0 on Windows XP, SP2 and MS VC 8, SP1, Group Edition. I have loaded the necessary packages and compiling them, as described on the website, works perfectly well. When trying to run the unit tests, i.e. 'testsuite' and/or 'testsuite-standalone', the executables crash without any warning right after (or at the end) of 'TimeBasedRollingTest'. Any clou why this happens? Perhaps, is this known issue .... Cheers Stefan Stefan.Borovac< at >t-online.de 2008-07-17T08:12:13 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2396 We use a RollingFileAppender defined as follows: <appender name="FILE" class="org.apache.log4j.RollingFileAppender"> <param name="maxFileSize" value="200MB" /> <param name="maxBackupIndex" value="20" /> <param name="File" value="${LOGNAME}" /> <param name="Append" value="false"/> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d{MM-dd HH:mm:ss.SSS} %5p %c{1} - %m%n" /> </layout> </appender> It works fine, except that the maxBackupIndex appears to top out at 13, even though we have 20 specified. Are we doing something wrong or is 13 a hard coded maximum for this field? Peter Steele 2008-07-16T20:33:06 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2394 Hello *, I ma trying to build log4cxx as static library using MS Visual Studio 2003, but it doesn't work. I have opened the project log4cxx.dsw of the log4cxx package, converted it to a MS Visual Studio 2003 project, set the project "log4cxx" as start-up project and changed two properties: - build "static library" not "dynamic library" - and the pre-processor definition "LOG4CXX" to "LOG4CXX_STATIC" When linking during the build process I get 544 warnings like the followings: apr-1.lib(dir.obj) : warning LNK4006: _apr_os_dir_put< at >12 already defined in aprutil-1.lib(dir.obj); second definition ignored apr-1.lib(fileacc.obj) : warning LNK4006: _apr_file_name_get< at >8 already defined in aprutil-1.lib(fileacc.obj); second definition ignored Linking my own test project with the build static library results in the following errors: log4cxx.lib(start.obj) : error LNK2019: unresolved external symbol __imp__WSACleanup< at >0 referenced in function _apr_initialize< at >0 log4cxx.lib(start.obj) : error LNK2019: unresolved external symbol __imp__WSAStartup< at >8 referenced in function _apr_initialize< at >0 log4cxx.lib(apr_snprintf.obj) : error LNK2019: unresolved external symbol __imp__ntohl< at >4 referenced in function _conv_in_addr log4cxx.lib(sockaddr.obj) : error LNK2001: unresolved external symbol __imp__ntohl< at >4 log4cxx.lib(sockaddr.obj) : error LNK2019: unresolved external symbol __imp__htons< at >4 referenced in function _apr_sockaddr_vars_set ... What have I to do to get the static library running? Please help. Thanks Markus Eberhard, Markus (external 2008-07-15T06:25:55 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2392 Hi, I am trying to build log4cxx in cygwin(CYGWIN_NT-5.1 1.5.25(0.156/4/2) 2008-06-12 19:34). It fails with: ./configure: line 20435: syntax error near unexpected token `,' ./configure: line 20435: `APR_FIND_APR( , , 1, 1)' Thanks for any help, bernd< at >prager.ws 2008-07-08T16:16:05 http://comments.gmane.org/gmane.comp.apache.logging.log4cxx.user/2391 STEINECKE Michael STD4-G (AREVA NP GmbH 2008-07-07T09:41:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.apache.logging.log4cxx.user