http://permalink.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://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2439 Thanks for your reply. Switching to apr 1.2.11 and apr-util 1.2.10 did indeed eliminate the compiler errors. Unfortunately, the build is still failing with apr-util linker errors: [cc] Starting link [cc] Creating library aprutil-1.lib and object aprutil-1.exp [cc] getuuid.obj : error LNK2001: unresolved external symbol _apr_os_uuid_get< at >4 [cc] getuuid.obj : error LNK2001: unresolved external symbol _apr_generate_random_bytes< at >8 [cc] aprutil-1.dll : fatal error LNK1120: 2 unresolved externals Any ideas? Thanks, Moshe Moshe Matitya 2008-08-27T17:16:11 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2438 On Aug 27, 2008, at 6:48 AM, Moshe Matitya wrote: The APR and APR-Util versions listed are substantially later than the ones that were current at the time of the log4cxx 0.10.0 release. If I remember correctly, 1.2.12 was the current release, but compilation problems resulted in releasing against APR 1.2.11 and APR-Util 1.2.10. Does log4cxx build properly on your configuration with those versions of APR and APR-Util? If so, then we can look at figuring out what has changed and how to either compensate or push the issue back to APR. Curt Arnold 2008-08-27T16:07:44 http://permalink.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' [ Moshe Matitya 2008-08-27T11:48:10 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2436 Hi Dale, thanks for your answer and the usefull tips. I have expected something like this but 2 1/2 years since the last Chainsaw release is quite a bit too long. We will see if we use Chainsaw at all. Cheers Stefan Dale King wrote: Stefan Borovac 2008-08-19T18:02:32 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2435 You could modify CONFIGURATION_TAG and other code in domconfigurator.cpp and do a custom build, but unless only you are going to be dealing with the resulting app, and make it clear that it's not following log4j.dtd, it may bite someone in the future. I use multiple configuration files in a configuration directory. Jacob L. Anawalt 2008-08-19T16:59:22 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2434 On Tue, Aug 19, 2008 at 9:26 AM, Stefan.Borovac< at >t-online.de < Stefan.Borovac< at >t-online.de> wrote: Yes the following will do it for the current thread. It is on a per thread basis so needs to be done per thread. log4cxx::MDC::put( "application", "my application name" ); This is a known version compatibility issue with the released version of Chainsaw. The current version of Log4j is the 1.2.x branch which is what Log4Cxx is a port of. A long while back work was started on a new 1.3 branch of Log4J. This branch was later abandoned and most of the features ported to the 1.2.x branch. There are differences between 1.2 and 1.3 that mean that 1.2 serialized location info and MDC properties do not deserialize correctly in 1.3. The problem is that the currently released version of Chainsaw is built with the 1.3 branch of Log4J. For now stick to XMLSocketAppender. Feel free to complain loudly over on the Log4J forums about this. I find it unbelievable that there has been no new release of Chainsaw to f Dale King 2008-08-19T15:22:17 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2433 Not without changing the software. I don't understand why you would want this. You say that it contains other information. The parser ignores any child elements of the configuration that are not one of the tags it knows about so you can put other information within the configuration. On Tue, Aug 19, 2008 at 2:21 AM, Madhu Gowda <madhu.gowda_b< at >yahoo.com>wrote: Dale King 2008-08-19T15:00:44 http://permalink.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" ?> <!DOCTY Stefan.Borovac< at >t-online.de 2008-08-19T13:26:46 http://permalink.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://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2430 Thank you. When I build log4cxx using Visual Studio, it does not generate expat lib instead I see "xml" library getting generated. So is it possible that log4cxx may not depend on expat and may depend on xml.lib? Or do I need to use some flag to explicitly let log4cxx use expat? Regards. -----Original Message----- From: Curt Arnold [mailto:carnold< at >apache.org] Sent: Friday, August 15, 2008 11:50 PM To: Log4CXX User Subject: Re: apr-util-expat On Aug 13, 2008, at 9:19 AM, Mehta, Jenica wrote: Not quite sure what you are asking and seems like an APR question anyway. If you are building APR using configure and make, it will use a previously installed expat. If you are building using Visual Studio, apr-util has an embedded copy of expat that it will compile. Mehta, Jenica 2008-08-19T06:17:52 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2429 I've heard of this SocketServer. I'll have to check it out. Thanks. From: renny.koshy< at >rubixinfotech.com [mailto:renny.koshy< at >rubixinfotech.com] Sent: Monday, August 18, 2008 7:44 AM To: Log4CXX User Subject: RE: Is this a bug or user error? Peter - We've had the exact same requirement on platform we did, which used Log4j... and ended up running the included "SocketServer" app and then logging everything to the socket-server, which actually wrote out the combined file. Renny Koshy President & CEO -------------------------------------------- Rubix Information Technologies, Inc. www.rubixinfotech.com "Peter Steele" <psteele< at >maxiscale.com> 08/18/2008 10:35 AM Please respond to "Log4CXX User" <log4cxx-user< at >logging.apache.org> To "Log4CXX User" <log4cxx-user< at >logging.apache.org> cc Subject RE: Is this a bug or user error? A multi-file-appender would be a great addition. I guess in the meantime the only solution is to either have all of the applications log to their own log f Peter Steele 2008-08-18T16:14:04 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2428 Peter - We've had the exact same requirement on platform we did, which used Log4j... and ended up running the included "SocketServer" app and then logging everything to the socket-server, which actually wrote out the combined file. Renny Koshy President & CEO -------------------------------------------- Rubix Information Technologies, Inc. www.rubixinfotech.com "Peter Steele" <psteele< at >maxiscale.com> 08/18/2008 10:35 AM Please respond to "Log4CXX User" <log4cxx-user< at >logging.apache.org> To "Log4CXX User" <log4cxx-user< at >logging.apache.org> cc Subject RE: Is this a bug or user error? A multi-file-appender would be a great addition. I guess in the meantime the only solution is to either have all of the applications log to their own log file or implement a log server. We clearly can't continue to use the configuration we have now... -----Original Message----- From: Curt Arnold [mailto:carnold< at >apache.org] Sent: Friday, August 15, 2008 11:27 AM To: Log4CXX User Subject: Re: Is this a bug or user renny.koshy< at >rubixinfotech.com 2008-08-18T14:43:54 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2427 A multi-file-appender would be a great addition. I guess in the meantime the only solution is to either have all of the applications log to their own log file or implement a log server. We clearly can't continue to use the configuration we have now... -----Original Message----- From: Curt Arnold [mailto:carnold< at >apache.org] Sent: Friday, August 15, 2008 11:27 AM To: Log4CXX User Subject: Re: Is this a bug or user error? On Aug 15, 2008, at 10:59 AM, Peter Steele wrote: log4cxx's RFAs mimics log4j's RFAs and having multiple independent applications attempt to write to the same location is a common misconfiguration problem in the log4j world. There is no mechanism (at least using java.io) to detect the situation, so the best we can do is to tell people not to do it. You are apparently running on non-Windows platform. What is occurring is that one application rolls over renaming the previous log file and creates the new log file, when other applications decide that it is time to roll over, Peter Steele 2008-08-18T14:35:19 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2426 Hmmm, that justmight do the trick. Thanks for the suggestion... From: Chris D'Annunzio [mailto:ChrisD< at >verdiem.com] Sent: Friday, August 15, 2008 11:00 AM To: Log4CXX User Subject: RE: RollingFileAppender question You could manually trigger a rollover when the application starts up. We do something similar in our application when the user wants to clear the log files. log4cxx::LoggerPtr pLogger = log4cxx::Logger::getRootLogger(); log4cxx::AppenderPtr pAppender = pLogger->getAppender(LOG_FILEAPPENDER_NAME); if (pAppender) { // Down cast so we have access tot he rolling file appender's methods log4cxx::helpers::ObjectPtrT<log4cxx::RollingFileAppender> pRFAppender = pAppender; log4cxx::helpers::Pool pool; pRFAppender->rollover(pool); } That will trigger a log file rollover. So, you could configure the appender with Append = true and then trigger a rollover when the application first starts up. You might Peter Steele 2008-08-16T18:13:32 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2425 On Aug 15, 2008, at 10:59 AM, Peter Steele wrote: log4cxx's RFAs mimics log4j's RFAs and having multiple independent applications attempt to write to the same location is a common misconfiguration problem in the log4j world. There is no mechanism (at least using java.io) to detect the situation, so the best we can do is to tell people not to do it. You are apparently running on non-Windows platform. What is occurring is that one application rolls over renaming the previous log file and creates the new log file, when other applications decide that it is time to roll over, then fail to create the new log file and continue to write to their old handle (which has been renamed since they originally opened it). There has been a long stalled initiative to develop a MultiFileAppender for log4j which may handle the situation more gracefully (not its main objective), but that development has been stalled for a year or so. Curt Arnold 2008-08-15T18:26:52 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2424 On Aug 13, 2008, at 9:19 AM, Mehta, Jenica wrote: Not quite sure what you are asking and seems like an APR question anyway. If you are building APR using configure and make, it will use a previously installed expat. If you are building using Visual Studio, apr-util has an embedded copy of expat that it will compile. Curt Arnold 2008-08-15T18:20:15 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2423 You could manually trigger a rollover when the application starts up. We do something similar in our application when the user wants to clear the log files. log4cxx::LoggerPtr pLogger = log4cxx::Logger::getRootLogger(); log4cxx::AppenderPtr pAppender = pLogger->getAppender(LOG_FILEAPPENDER_NAME); if (pAppender) { // Down cast so we have access tot he rolling file appender's methods log4cxx::helpers::ObjectPtrT<log4cxx::RollingFileAppender> pRFAppender = pAppender; log4cxx::helpers::Pool pool; pRFAppender->rollover(pool); } That will trigger a log file rollover. So, you could configure the appender with Append = true and then trigger a rollover when the application first starts up. You might need a special case when the application starts for the first time if you don't want an extra empty log file, but hope this gets you closer. -Chris ________________________________ From: Peter Steele [mailto:pste Chris D'Annunzio 2008-08-15T18:00:12 http://permalink.gmane.org/gmane.comp.apache.logging.log4cxx.user/2422 Interesting that some fail to roll over and close the old file handle. I think it would be better to have individual processes write to a log server, either a log4cxx capable one that can read a config file and filter or a "dumb" one, and have a single log server write to the log file. Jacob L. Anawalt 2008-08-15T16:18:37 http://permalink.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 so Peter Steele 2008-08-15T15:59:01 http://permalink.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://permalink.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 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.apache.logging.log4cxx.user