gmane.comp.apache.logging.log4cxx.user

Re: C++ using Qt and Log4cxx does not show in console

Thorsten Schöning — 2013-05-21T21:00:37

Guten Tag Mike,
am Dienstag, 21. Mai 2013 um 19:44 schrieben Sie:


Could you give some more details about why your QT library doesn't
support stdout/stderr or what it is doing with those? Maybe one can
provide some alternatives, but doesn't know exactly what the problem
with the QT library is.

Mit freundlichen Grüßen,

Thorsten Schöning

Re: C++ using Qt and Log4cxx does not show in console

Mike — 2013-05-21T20:06:05

Yes, I currently have this set up (and working) in a test application which only uses the standard C++ library that is also a console application as opposed to an actual application project.  For the test application, it will write as intended to the console among other files.
I believe these two have a different approach to being able to write to the console(perhaps I am mistaken.)
However, as you have your properties (and I have mine) it will not work for this project.
Regards-Mike

--- On Tue, 5/21/13, Wesley J. Miller <WMiller< at >sdr.com> wrote:

From: Wesley J. Miller <WMiller< at >sdr.com>
Subject: Re: C++ using Qt and Log4cxx does not show in console
To: "Log4CXX User" <log4cxx-user< at >logging.apache.org>
Date: Tuesday, May 21, 2013, 3:13 PM

Mike,

Hee is the logs.config file I use.  To turn on logging to console just add    , stdout  to the first line like this:

log4j.rootLogger=INFO, File, stdout

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Re: C++ using Qt and Log4cxx does not show in console

Mike — 2013-05-21T20:00:21

I am trying to write to the Output console that is dock able on the bottom of the screen.

It says "Show output from: Build, Build Order, Debug"
If I do a qDebug() this goes there.

However, in a test application when using the standard C++ library with log4cxx all output for the console would go to a typical cmd prompt.

I am fine using either or.

Regards,
-Mike




--- On Tue, 5/21/13, Jacob L. Anawalt <janawalt< at >geckosoftware.com> wrote:

From: Jacob L. Anawalt <janawalt< at >geckosoftware.com>
Subject: Re: C++ using Qt and Log4cxx does not show in console
To: log4cxx-user< at >logging.apache.org
Date: Tuesday, May 21, 2013, 3:37 PM

On 5/21/2013 11:44 AM, Mike wrote:

Do you mean the VS debug output window via OutputDebugString, or are you talking about a standard console via AllocConsole or a Win32 console application?

Re: C++ using Qt and Log4cxx does not show in console

Jacob L. Anawalt — 2013-05-21T19:37:31

Do you mean the VS debug output window via OutputDebugString, or are you talking 
about a standard console via AllocConsole or a Win32 console application?

Re: C++ using Qt and Log4cxx does not show in console

Wesley J. Miller — 2013-05-21T19:13:44

Mike,

Hee is the logs.config file I use.  To turn on logging to console just add    , stdout  to the first line like this:

log4j.rootLogger=INFO, File, stdout

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

log4j.rootLogger=INFO, File


log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n

log4j.appender.File=org.apache.log4j.RollingFileAppender
log4j.appender.File.File=logs/system.logs
log4j.appender.File.MaxFileSize=1MB
log4j.appender.File.MaxBackupIndex=10
log4j.appender.File.layout=org.apache.log4j.PatternLayout
log4j.appender.File.layout.ConversionPattern=%d{MM/dd/yyyy HH:mm:ss:SSS a} %p %c %m%n


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

C++ using Qt and Log4cxx does not show in console

Mike — 2013-05-21T17:44:48

I am attempting to use log4cxx to write to the Visual Studio (2008) 
console.  However, I am using a Qt library in a Win 32 application that 
does not use (and won't work) std::cout or std::cerr to print to the console . 

I 
know in the properties file you are able to create you own appenders.  
How would I go about doing this to get it to display in the console or is there a better way to approach this?

Regards,
Mike

Re: Caching LoggerPtr using local statics (the singleton pattern)

Rhosyn — 2013-05-17T07:17:37

Hi Balaji,

Static Singletons are problematic during system shutdown in multithreaded
systems.

This thread discusses that issue in a slightly different context with
log4cxx along with a slightly ugly but effective  workaround (allocate the
object using new and store a raw pointer rather than a smart pointer in the
static variable):

http://mail-archives.apache.org/mod_mbox/logging-log4cxx-dev/200901.mbox/%3C4975157F.8070001< at >purplescarab.com%3E

Hth,

Rhosyn
On May 17, 2013 7:50 AM, "Balaji Babu" <babu.lbk< at >gmail.com> wrote:

Re: Caching LoggerPtr using local statics (the singleton pattern)

Balaji Babu — 2013-05-17T06:21:24

pointer instead of a smart-pointer a better solution?On Tue, May 26, 2009 at 
4:20 PM, Curt Arnold <carnold <at> apache.org> wrote:Try using the one 
parameter constructor for LoggerPtr, instead of the default constructor and 
then an assignment:
singleton(log4cxx::LogManager::getLogger("some.logger"));
the default constructor, it is
constructor results in APR being destroyed last.
getLogger in a local static variable (i.e. singleton) like this:
log4cxx::LogManager::getLogger("some.logger");
please shed light on this? Does this happen to you?

Hello Assaf Lavie,
May I know whether you got the solution for this issue. Me too facing the 
same kind of issue in my application. The application is crashing at exit by 
pointing the apr_thread_mutex_destroy. It would be great help if I get the 
solution to resolve this issue.

Thanks in advance.
Balaji

Re: Add, enable, disable log4cxx ConsoleAppender at runtime

Wesley J. Miller — 2013-05-09T17:47:47


CONFIDENTIALITY NOTE:

This e-mail and any attachments are confidential. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please notify us immediately by returning it to the sender and delete this copy from your system. Thank you for your cooperation.

Re: Add, enable, disable log4cxx ConsoleAppender at runtime

log4cxx — 2013-05-09T17:17:33

Hi Wea,

Our product has code to dynamically add a console appender, but it is not currently in use. As such, I can't say for 
sure whether it works or not.

===========
static const LogString DateTimeThreadLevelClassMessagePattern (LOG4CXX_STR("%d{dd/MM HH:mm:ss.SSS} 
%-5p %c - %m%n"));
LogString lsPattern = DateTimeThreadLevelClassMessagePattern;
if (!overridePattern.IsEmpty())
{
lsPattern = GetLogString(overridePattern);
}
LoggerPtr root = Logger::getRootLogger();
LayoutPtr layout(new PatternLayout(lsPattern));
AppenderPtr appender(new ConsoleAppender(layout));
root->addAppender(appender);
==========

Code to remove a named appender is also untested and I don't know off-hand if this works for "stdout". 
GetLogString is our function which takes our own String class and creates a LogString
=====
LogString strAppenderName = GetLogString(appenderName);

LoggerPtr root = Logger::getRootLogger();
root->removeAppender(strAppenderName);
return true;
=====

Hope this helps,
Andy

On Thu, May 9, 2013

Add, enable, disable log4cxx ConsoleAppender at runtime

Wesley J. Miller — 2013-05-09T15:03:39


How would I dynamically turn log4cxx logging to the console on and off in an application?

Goal here is to process a used choice, command line parm or GUI input or whatever. Thus in a hypothetical main loop:

if ( userWantsToStartConsoleLogger )
    ConsoleLogger( true );
if ( userWantsToStopConsoleLogger )
    ConsoleLogger( false );

My logging setup is:

#include <log4cxx/logger.h>
#include <log4cxx/propertyconfigurator.h>
#include <log4cxx/helpers/exception.h>

int main( int argc, char** argv )
{
   const log4cxx::LoggerPtr   logger;
   log4cxx::PropertyConfigurator::configure("./logs.config");
}

where ./logs.config looks like:

log4j.rootLogger=INFO, File

log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n

log4j.appender.File=org.apache.log4j.RollingFileAppender
log4j.appender.File.File=logs/system.logs
log4j.appender.File.MaxFileSize=1MB
log4j.appender.File.MaxBacku

Re: Rolling File appender with compression doesn't seem to work

chand priyankara — 2013-05-08T23:41:14

Can we look at your configuration file please?

regards,


*Chand Priyankara*  [image: Facebook]<http://www.facebook.com/chand.priyankara>
 [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image:
Blogger] <http://chandpriyankara.blogspot.com/> [image: Google
Plus]<http://plus.google.com/104246340732624023499>

|BSc(Eng) - Electrical & Information
|(094) 773-361-566
|chand< at >engineering.com
|http://chandpriyankara.blogspot.com
<http://www.iucnredlist.org/amazing-species>sent via internet


On Tue, May 7, 2013 at 10:34 PM, dolbydc <donevan.dolby< at >base2s.com> wrote:

Re: Rolling File appender with compression doesn't seem to work

dolbydc — 2013-05-07T17:04:42

I am running on linux with the following as my rolling filename my.log.%d.gz,
gzip's location is in my path, however upon rolling over I only get files of
the nature:

my.log.3
my.log.2
my.log.1
my.log

They are not compressed using gzip as I would expect given the documenation.



--
View this message in context: http://apache-logging.6191.n7.nabble.com/Rolling-File-appender-with-compression-doesn-t-seem-to-work-tp32646p37311.html
Sent from the Log4cxx - Users mailing list archive at Nabble.com.

Re: RollingFileAppender Exception

dolbydc — 2013-05-07T16:41:39

It appears to be a lack of write permissions on the folder.  In the deployed
environment only the owner of the folder had write permission and on my dev
everyone had write permission.

Thanks
dolbydc



--
View this message in context: http://apache-logging.6191.n7.nabble.com/RollingFileAppender-Exception-tp37288p37309.html
Sent from the Log4cxx - Users mailing list archive at Nabble.com.

Re: RollingFileAppender Exception

Thorsten Schöning — 2013-05-07T15:53:52

Guten Tag dolbydc,
am Dienstag, 7. Mai 2013 um 17:41 schrieben Sie:


I can't see anything but if you configured a filename then check
permissions on the path configured.

Mit freundlichen Grüßen,

Thorsten Schöning

Re: RollingFileAppender Exception

dolbydc — 2013-05-07T15:41:04

Thorsten,

Thanks for the reply.  I am not sure what happened with my original paste,
but these are the settings I have within the appxNormalAppender appender
declaration.  I do have a filename.








--
View this message in context: http://apache-logging.6191.n7.nabble.com/RollingFileAppender-Exception-tp37288p37306.html
Sent from the Log4cxx - Users mailing list archive at Nabble.com.

Re: RollingFileAppender Exception

Thorsten Schöning — 2013-05-07T05:14:28

Guten Tag dolbydc,
am Dienstag, 7. Mai 2013 um 01:01 schrieben Sie:

[...]

There's no filename configured, this may work because of some defaults
in your development environment, but may can't because of missing
permissions or whatever in other environments. You shouldn't use empty
layout configurations, too.

http://apache-logging.6191.n7.nabble.com/help-RollingFileAppender-xml-configuration-td31386.html
http://www.yolinux.com/TUTORIALS/Log4cxx.html

Mit freundlichen Grüßen,

Thorsten Schöning

RollingFileAppender Exception

dolbydc — 2013-05-06T23:01:13

All,

I am getting the following error on one machine when running log4cxx, but
the appender works properly on my development VM.

log4cxx: Exception during rollover
log4cxx: No output stream or file set for the appender named
[appxNormalAppender].

Here is my current xml configuration for this.

<?xml version="1.0" encoding="UTF-8" ?>
  <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
  
  <appender name="appxConsoleAppender"
class="org.apache.log4j.ConsoleAppender">
      
     <layout class="org.apache.log4j.PatternLayout">
       
     </layout>
  </appender>

  
  <appender name="appxNormalAppender"
class="org.apache.log4j.RollingFileAppender">
      
      
      
      
      <rollingPolicy
class="org.apache.log4j.rolling.TimeBasedRollingPolicy">
            
      </rollingPolicy>
      <layout class="org.apache.log4j.PatternLayout">
            
      </layout>
  </appender>


  
  <appender name="appxAuditAppender" class="org.apache.log4j.FileAppender">
      
      
      <layo

Re: log4cxx - reaching out for interested developers

Pedro Lamarão — 2013-05-06T17:10:39

Em 06/05/2013 14:00, chand priyankara escreveu:


I have somehow missed this.

We will see about rebasing our internal fork onto that.

Is there a process for patch reviewing and/or pull requests already in
place?

Re: log4cxx - reaching out for interested developers

chand priyankara — 2013-05-06T17:00:56

Hi All,

Pretty good discussions, thanks to every body.
Git seems a good track, and I'm in.

Since *Christian* is here, I hope we can continue with:
https://github.com/apache/log4cxx

:)



regards,


*Chand Priyankara*  [image: Facebook]<http://www.facebook.com/chand.priyankara>
 [image: LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image:
Blogger] <http://chandpriyankara.blogspot.com/> [image: Google
Plus]<http://plus.google.com/104246340732624023499>

|BSc(Eng) - Electrical & Information
|(094) 773-361-566
|chand< at >engineering.com
|http://chandpriyankara.blogspot.com
<http://www.iucnredlist.org/amazing-species>sent via internet


On Mon, May 6, 2013 at 9:38 PM, Pedro Lamarão
<pedro.lamarao< at >prodist.com.br>wrote:

Re: log4cxx - reaching out for interested developers

Pedro Lamarão — 2013-05-06T16:08:36

Em 06/05/2013 11:38, Rhys Ulerich escreveu:


If someone could instruct me on this process, I could submit a
contribution agreement ASAP, and then keep this in mind while managing
the fork. I suspect a small community would not give me much trouble in
this regard.