Re: NTEventLogAppender
When I had this problem, it turned out to be because NTEventLogAppender only has the capability to log using an RPC call and my server was locked down to not accept remote event logs. I fixed this by patching the 0.9.7 NTEventLogAppender to have better error logging and to use the local API if the server was an empty string. Even if you are not logging to the local host, the error logging might be beneficial to you for tracking your trouble down. Attached is a patch for 0.9.7 On Tue, 1 Mar 2005 15:54:49 -0800, Ron Ohmer [EMAIL PROTECTED] wrote: I too am having difficulties with this... Here is the my add appender code: #ifdef WIN32 NTEventLogAppender* ntlog=new NTEventLogAppender(); ntlog-setLog(Application); ntlog-setServer(flormo04); ntlog-setName(syslogappender); ntlog-activateOptions(); CConfig::GetLogger()-addAppender(ntlog); #endif Where CConfig::GetLogger() is the logger... Do all the other types of loggers fine, but this one gives me: NT Event Log not opened.. I have tried it with out the set... Commands as well... Any advice? Thanks! Ron log4cxx_0_9_7.nteventappender.patch Description: Binary data
Re: Questions regarding CVS HEAD
Curt, thanks very much for the answer. Unfortunately, I can only assume we fit the bill of multithreaded logging since most of our applications are currently being run inside gSOAP or Tomcat.. I'll be watching the progress toward 0.9.8 closely. Thanks! Daniel On Fri, 11 Feb 2005 12:42:03 -0600, Curt Arnold [EMAIL PROTECTED] wrote: Unless you are immediately jumping into multithreaded logging I would recommend using the CVS HEAD over 0.9.7. Currently the synchronization and thread-local stuff is stubbed out. The next release will look almost exactly like the current CVS, but with more features fleshed out and tested. I've added a task to Jira (http://issues.apache.org/jira/browse/LOGCXX-62) to track the issues that are blocking (at least in my opinion) the release. Please feel free to add additional issues or petition to have issues reduced from blocking status. The CVS HEAD is now being build and tested daily by Gump (Ant build only) and any breakage will result in an nag message to the mailing list. On Feb 11, 2005, at 12:15 PM, Daniel Einspanjer wrote: How stable is the current CVS source? Is there a roadmap anywhere for a release of .9.8? We're in the early stages of trying to implement log4cxx in our system and I am catching a lot of flak from some of the developers on my team because of problems with static initialization and compilation problems with icc... I'm hoping that .9.8 is the answer to several of these problems, and I might even be able to work with CVS source for a while if it is relatively stable and close to what .9.8 is going to look like... Thanks, Daniel
Logging in templates?
Could anyone share their methods for logging within a templated class? Specifically, the problem I don't have a good solution for is the static instantiation of a logger object at all, let alone one that has a name giving the particular class for which the template is being used. Thanks, Daniel
Advice requested on best way to implement log4* to support non-hierarchal categories
My company is looking to standardize our logging across all of our C++ (and eventually Java) projects and we would certainly rather use a well-known architecture such as log4j/log4cxx rather than growing our own. My biggest challenge is that one of the key desires our developers have is to be able to mix and match the selectiveness of the logging. The easiest way to explain would probably be by example. We would like to be able to easily mix and match any of the following categories of log messages: * performance/timing related * search result related * search result quality related * any messages in the hierarchy com.foo * no messages from the class/hierarchy com.foo.bar We were hoping to be able to define the characteristics of log messages within the class com.foo.bar so that we could have overall performance log messages, search result performance messages, search result quality messages, overall search result messages, etc. and then via configuration we could say, hrm, lets take a look at the search result quality across all of com.foo. Is anyone else doing anything like this out there? I have done quite a bit of reading on the log4j and log4cxx documentation, but I have not found a good resource for explaining the Filter class hierarchy. Any pointers or advice is welcome. Thanks, Daniel E.
