manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luis Cabaceira <>
Subject Re: MCF 2.8.1 agent logs
Date Wed, 27 Sep 2017 14:11:01 GMT
Hi, i've had the exact same problem and the issue is related to the log
level setting that apparently its not honoured for the connectors logging.
Normal logs are still being written to logs/manifoldcf.log.

When you change the log level to let's say DEBUG or TRACE by changing the
Root level in logging.xml (see below)

<Configuration status="warn" name="ManifoldCF" packages="">
    <File name="MyFile" fileName="logs/manifoldcf.log">
        <Pattern>%5p %d{ISO8601} (%t) - %m%n</Pattern>
    <Root level="debug">
      <AppenderRef ref="MyFile"/>

You do get all the other logs in DEBUG :

DEBUG 2017-09-27T15:01:21,844 (qtp895366343-408) - Created '20' parsers.
DEBUG 2017-09-27T15:01:21,844 (qtp895366343-408) - Velocimacro :
"velocimacro.library" is not set.  Trying default library:
DEBUG 2017-09-27T15:01:21,844 (qtp895366343-408) - Could not load resource
'VM_global_library.vm' from ResourceLoader
org.apache.manifoldcf.core.i18n.MCFVelocityResourceLoader: Resource
'VM_global_library.vm' not found.
DEBUG 2017-09-27T15:01:21,844 (qtp895366343-408) - Velocimacro : Default
library not found.
DEBUG 2017-09-27T15:01:21,844 (qtp895366343-408) - Velocimacro :
allowInline = true : VMs can be defined inline in templates
DEBUG 2017-09-27T15:01:21,844 (qtp895366343-408) - Velocimacro :
allowInlineToOverride = false : VMs defined inline may NOT replace previous
VM definitions
DEBUG 2017-09-27T15:01:21,844 (qtp895366343-408) - Velocimacro :
allowInlineLocal = false : VMs defined inline will be global in scope if
DEBUG 2017-09-27T15:01:21,844 (qtp895366343-408) - Velocimacro : autoload
off : VM system will not automatically reload global library macros
DEBUG 2017-09-27T15:01:21,845 (qtp895366343-408) - ResourceManager : found
editSpecification_CMISQuery.html with loader

BUT, when inside my connector development if i try to log as debug, for
example :

Logging.connectors.debug("Testing DEBUG on logging.xml settings by Luis

That is not outputted in manifoldcf.log. To prove this i've executed the
same line in error and it does get written.

Logging.connectors.error("Testing Error log on logging.xml settings by Luis

I assume that the connectors logging implementation is not reading its
configuration from the same place...


On 27 September 2017 at 14:35, Karl Wright <> wrote:

> Hi Julien,
> Thanks for bringing the documentation issue to our attention.  Can you
> create a ticket for that?
> As for the problem: Do you not see log output for manifoldcf.log for (say)
> the unaltered single-process example?  It has been a while since the port
> to log4j2 was done but I'm pretty sure I saw log output after that port.  I
> know for a fact that the IT tests generate log output without issue.
> Please try to verify this.  Thanks!
> Karl
> On Wed, Sep 27, 2017 at 9:22 AM, Julien Massiera <
>> wrote:
>> Hi MCF community,
>> I recently switched from MCF 2.5 to MCF 2.8.1 and I am a little bit
>> confused with the agent logs.
>> First of all I noticed that MCF is now using log4j2 and the documentation
>> is not up to date on this point (the old logging.ini format is mentioned) :
>> w-to-build-and-deploy.html#Logging+configuration+file+properties
>> Then I decided to use the logging.xml provided in the example directory
>> of MCF and I just changed the log level of the root logger :
>> <Configuration status="warn" name="ManifoldCF" packages="">
>>   <Appenders>
>>     <File name="MyFile" fileName="logs/manifoldcf.log">
>>       <PatternLayout>
>>         <Pattern>%5p %d{ISO8601} (%t) - %m%n</Pattern>
>>       </PatternLayout>
>>     </File>
>>   </Appenders>
>>   <Loggers>
>>     <Root level="all">
>>       <AppenderRef ref="MyFile"/>
>>     </Root>
>>   </Loggers>
>> </Configuration>
>> The problem is that the logging file is correctly created but is never
>> filled. Any idea of what's wrong ? Did I miss something ?
>> Thanks for your help,
>> Julien

Luis Cabaceira

View raw message