You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@manifoldcf.apache.org by Fuad Efendi <fu...@efendi.ca> on 2011/03/11 21:26:11 UTC
Logging
Hi,
I am running example application using Jetty; how to configure logging? I
believe there is overlap of LOG4J somewhere with something (SLF4J?) - no any
output of logs, but application sees existence of *.ini file
-Fuad
RE: Logging
Posted by Fuad Efendi <fu...@efendi.ca>.
It is trunk...
-----Original Message-----
From: Karl Wright [mailto:daddywri@gmail.com]
Sent: March-11-11 3:57 PM
To: connectors-user@incubator.apache.org
Subject: Re: Logging
I don't have any problems at all generating logs.
Are you using trunk, or 0.1?
Karl
On Fri, Mar 11, 2011 at 3:44 PM, Fuad Efendi <fu...@efendi.ca> wrote:
> Hi Karl,
>
> I commented existing settings and set this:
> log4j.appender.Console=org.apache.log4j.ConsoleAppender
> log4j.appender.Console.layout=org.apache.log4j.PatternLayout
> log4j.appender.Console.layout.conversionPattern=%-5p - %-26.26c{1} -
> %m\n log4j.rootLogger=TRACE, Console
>
> - and no any console output in Windows, nothing... however, LOG4J sees
> if there are any typo in this file...
>
> Thanks,
> Fuad
>
>
>
> -----Original Message-----
> From: Karl Wright [mailto:daddywri@gmail.com]
> Sent: March-11-11 3:34 PM
> To: connectors-user@incubator.apache.org
> Subject: Re: Logging
>
> The logging.ini file in dist/example should look something like this:
>
> log4j.appender.MAIN.File=logs/manifoldcf.log
> log4j.rootLogger=WARN, MAIN
> log4j.appender.MAIN=org.apache.log4j.RollingFileAppender
> log4j.appender.MAIN.layout=org.apache.log4j.PatternLayout
>
> The log output goes to dist/example/logs/manifoldcf.log.
>
> The way you turn on logging is either in logging.ini, describing
> standard log4j loggers, or in properties.xml, where the properties
> that ManifoldCF interprets as system loggers can be set to WARN, INFO,
> DEBUG, etc. These
> are:
>
> org.apache.manifoldcf.misc (miscellaneous) org.apache.manifoldcf.db
> (database) org.apache.manifoldcf.connectors (connectors) etc.
>
> e.g:
> <property name="xxx" value="DEBUG"/>
>
> The complete list is in the code, but let me know what loggers you are
> interested in and I can probably remember. After you set either
> properties or logging.ini, you should restart ManifoldCF so it reads
> the new logging files.
>
> Also, on Windows, you may need to ^C out of ManifoldCF to get it to
> flush to the log; this seems to be a problem with log4j on that platform.
>
> Karl
>
> On Fri, Mar 11, 2011 at 3:26 PM, Fuad Efendi <fu...@efendi.ca> wrote:
>> Hi,
>>
>> I am running example application using Jetty; how to configure
>> logging? I believe there is overlap of LOG4J somewhere with something
>> (SLF4J?) - no any output of logs, but application sees existence of
>> *.ini file
>>
>> -Fuad
>
>
RE: Logging
Posted by Fuad Efendi <fu...@efendi.ca>.
Ok, it works now with additional settings in properties.xml file:
<property name="org.apache.manifoldcf.root" value="ALL"/>
<property name="org.apache.manifoldcf.misc" value="ALL"/>
<property name="org.apache.manifoldcf.db" value="ALL"/>
<property name="org.apache.manifoldcf.lock" value="ALL"/>
<property name="org.apache.manifoldcf.cache" value="ALL"/>
<property name="org.apache.manifoldcf.keystore" value="ALL"/>
<property name="org.apache.manifoldcf.perf" value="ALL"/>
You can use any level supported by LOG4J
-----Original Message-----
From: Fuad Efendi [mailto:fuad@efendi.ca]
Sent: March-11-11 4:02 PM
To: 'connectors-user@incubator.apache.org'
Subject: RE: Logging
It is trunk...
-----Original Message-----
From: Karl Wright [mailto:daddywri@gmail.com]
Sent: March-11-11 3:57 PM
To: connectors-user@incubator.apache.org
Subject: Re: Logging
I don't have any problems at all generating logs.
Are you using trunk, or 0.1?
Karl
On Fri, Mar 11, 2011 at 3:44 PM, Fuad Efendi <fu...@efendi.ca> wrote:
> Hi Karl,
>
> I commented existing settings and set this:
> log4j.appender.Console=org.apache.log4j.ConsoleAppender
> log4j.appender.Console.layout=org.apache.log4j.PatternLayout
> log4j.appender.Console.layout.conversionPattern=%-5p - %-26.26c{1} -
> %m\n log4j.rootLogger=TRACE, Console
>
> - and no any console output in Windows, nothing... however, LOG4J sees
> if there are any typo in this file...
>
> Thanks,
> Fuad
>
>
>
> -----Original Message-----
> From: Karl Wright [mailto:daddywri@gmail.com]
> Sent: March-11-11 3:34 PM
> To: connectors-user@incubator.apache.org
> Subject: Re: Logging
>
> The logging.ini file in dist/example should look something like this:
>
> log4j.appender.MAIN.File=logs/manifoldcf.log
> log4j.rootLogger=WARN, MAIN
> log4j.appender.MAIN=org.apache.log4j.RollingFileAppender
> log4j.appender.MAIN.layout=org.apache.log4j.PatternLayout
>
> The log output goes to dist/example/logs/manifoldcf.log.
>
> The way you turn on logging is either in logging.ini, describing
> standard log4j loggers, or in properties.xml, where the properties
> that ManifoldCF interprets as system loggers can be set to WARN, INFO,
> DEBUG, etc. These
> are:
>
> org.apache.manifoldcf.misc (miscellaneous) org.apache.manifoldcf.db
> (database) org.apache.manifoldcf.connectors (connectors) etc.
>
> e.g:
> <property name="xxx" value="DEBUG"/>
>
> The complete list is in the code, but let me know what loggers you are
> interested in and I can probably remember. After you set either
> properties or logging.ini, you should restart ManifoldCF so it reads
> the new logging files.
>
> Also, on Windows, you may need to ^C out of ManifoldCF to get it to
> flush to the log; this seems to be a problem with log4j on that platform.
>
> Karl
>
> On Fri, Mar 11, 2011 at 3:26 PM, Fuad Efendi <fu...@efendi.ca> wrote:
>> Hi,
>>
>> I am running example application using Jetty; how to configure
>> logging? I believe there is overlap of LOG4J somewhere with something
>> (SLF4J?) - no any output of logs, but application sees existence of
>> *.ini file
>>
>> -Fuad
>
>
Re: Logging
Posted by Karl Wright <da...@gmail.com>.
I don't have any problems at all generating logs.
Are you using trunk, or 0.1?
Karl
On Fri, Mar 11, 2011 at 3:44 PM, Fuad Efendi <fu...@efendi.ca> wrote:
> Hi Karl,
>
> I commented existing settings and set this:
> log4j.appender.Console=org.apache.log4j.ConsoleAppender
> log4j.appender.Console.layout=org.apache.log4j.PatternLayout
> log4j.appender.Console.layout.conversionPattern=%-5p - %-26.26c{1} - %m\n
> log4j.rootLogger=TRACE, Console
>
> - and no any console output in Windows, nothing... however, LOG4J sees if
> there are any typo in this file...
>
> Thanks,
> Fuad
>
>
>
> -----Original Message-----
> From: Karl Wright [mailto:daddywri@gmail.com]
> Sent: March-11-11 3:34 PM
> To: connectors-user@incubator.apache.org
> Subject: Re: Logging
>
> The logging.ini file in dist/example should look something like this:
>
> log4j.appender.MAIN.File=logs/manifoldcf.log
> log4j.rootLogger=WARN, MAIN
> log4j.appender.MAIN=org.apache.log4j.RollingFileAppender
> log4j.appender.MAIN.layout=org.apache.log4j.PatternLayout
>
> The log output goes to dist/example/logs/manifoldcf.log.
>
> The way you turn on logging is either in logging.ini, describing standard
> log4j loggers, or in properties.xml, where the properties that ManifoldCF
> interprets as system loggers can be set to WARN, INFO, DEBUG, etc. These
> are:
>
> org.apache.manifoldcf.misc (miscellaneous) org.apache.manifoldcf.db
> (database) org.apache.manifoldcf.connectors (connectors) etc.
>
> e.g:
> <property name="xxx" value="DEBUG"/>
>
> The complete list is in the code, but let me know what loggers you are
> interested in and I can probably remember. After you set either properties
> or logging.ini, you should restart ManifoldCF so it reads the new logging
> files.
>
> Also, on Windows, you may need to ^C out of ManifoldCF to get it to flush to
> the log; this seems to be a problem with log4j on that platform.
>
> Karl
>
> On Fri, Mar 11, 2011 at 3:26 PM, Fuad Efendi <fu...@efendi.ca> wrote:
>> Hi,
>>
>> I am running example application using Jetty; how to configure
>> logging? I believe there is overlap of LOG4J somewhere with something
>> (SLF4J?) - no any output of logs, but application sees existence of
>> *.ini file
>>
>> -Fuad
>
>
RE: Logging
Posted by Fuad Efendi <fu...@efendi.ca>.
Hi Karl,
I commented existing settings and set this:
log4j.appender.Console=org.apache.log4j.ConsoleAppender
log4j.appender.Console.layout=org.apache.log4j.PatternLayout
log4j.appender.Console.layout.conversionPattern=%-5p - %-26.26c{1} - %m\n
log4j.rootLogger=TRACE, Console
- and no any console output in Windows, nothing... however, LOG4J sees if
there are any typo in this file...
Thanks,
Fuad
-----Original Message-----
From: Karl Wright [mailto:daddywri@gmail.com]
Sent: March-11-11 3:34 PM
To: connectors-user@incubator.apache.org
Subject: Re: Logging
The logging.ini file in dist/example should look something like this:
log4j.appender.MAIN.File=logs/manifoldcf.log
log4j.rootLogger=WARN, MAIN
log4j.appender.MAIN=org.apache.log4j.RollingFileAppender
log4j.appender.MAIN.layout=org.apache.log4j.PatternLayout
The log output goes to dist/example/logs/manifoldcf.log.
The way you turn on logging is either in logging.ini, describing standard
log4j loggers, or in properties.xml, where the properties that ManifoldCF
interprets as system loggers can be set to WARN, INFO, DEBUG, etc. These
are:
org.apache.manifoldcf.misc (miscellaneous) org.apache.manifoldcf.db
(database) org.apache.manifoldcf.connectors (connectors) etc.
e.g:
<property name="xxx" value="DEBUG"/>
The complete list is in the code, but let me know what loggers you are
interested in and I can probably remember. After you set either properties
or logging.ini, you should restart ManifoldCF so it reads the new logging
files.
Also, on Windows, you may need to ^C out of ManifoldCF to get it to flush to
the log; this seems to be a problem with log4j on that platform.
Karl
On Fri, Mar 11, 2011 at 3:26 PM, Fuad Efendi <fu...@efendi.ca> wrote:
> Hi,
>
> I am running example application using Jetty; how to configure
> logging? I believe there is overlap of LOG4J somewhere with something
> (SLF4J?) - no any output of logs, but application sees existence of
> *.ini file
>
> -Fuad
Re: Logging
Posted by Karl Wright <da...@gmail.com>.
The logging.ini file in dist/example should look something like this:
log4j.appender.MAIN.File=logs/manifoldcf.log
log4j.rootLogger=WARN, MAIN
log4j.appender.MAIN=org.apache.log4j.RollingFileAppender
log4j.appender.MAIN.layout=org.apache.log4j.PatternLayout
The log output goes to dist/example/logs/manifoldcf.log.
The way you turn on logging is either in logging.ini, describing
standard log4j loggers, or in properties.xml, where the properties
that ManifoldCF interprets as system loggers can be set to WARN, INFO,
DEBUG, etc. These are:
org.apache.manifoldcf.misc (miscellaneous)
org.apache.manifoldcf.db (database)
org.apache.manifoldcf.connectors (connectors)
etc.
e.g:
<property name="xxx" value="DEBUG"/>
The complete list is in the code, but let me know what loggers you are
interested in and I can probably remember. After you set either
properties or logging.ini, you should restart ManifoldCF so it reads
the new logging files.
Also, on Windows, you may need to ^C out of ManifoldCF to get it to
flush to the log; this seems to be a problem with log4j on that
platform.
Karl
On Fri, Mar 11, 2011 at 3:26 PM, Fuad Efendi <fu...@efendi.ca> wrote:
> Hi,
>
> I am running example application using Jetty; how to configure logging? I
> believe there is overlap of LOG4J somewhere with something (SLF4J?) – no any
> output of logs, but application sees existence of *.ini file
>
> -Fuad