incubator-s4-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthieu Morel <>
Subject Re: logback configuration problems
Date Mon, 02 Sep 2013 16:08:06 GMT

I had a look and indeed could reproduce that issue. In order to customize the log config,
we need to include an arbitrary directory in the classpath of s4 nodes, so we can place logback.xml
there. The classpath for s4 nodes is given by a generated script (check s4 file and linked
s4-tools file), and apparently (maybe due to some gradle update) the generated classpath does
not include the lib directory anymore, only the jars it contains.

So that's a bug.

Workaround would be to manually modify the s4-tools script and include an arbitrary directory
in the CLASSPATH variable. You could do that from a generated binary distribution so you don't
have to worry about getting the s4-tools file rewritten.

Hope this helps,


On Aug 30, 2013, at 17:19 , Yago <> wrote:

> Hello all
> I'm having problems with log configuration in my s4 apps. Have tried a lot of things
in order to change the default behaviour of logback, but none of them worked. These were my
attempts (some of them might look a bit strange or desperate):
> - Put logback.xml in subprojects/s4-tools/build/install/s4-tools/lib/ directory as suggested
in doc, and even in lib/ directory.
> - Edited all the logback.xml files in my s4 directory, changing level and/or pattern
> - Edited all the files, changing level
> - Added both files to my application in /src/main/resources/ directory, so they are included
in the built jar (checked). No result.
> - Tried to pass s4.logger_level=info as a parameter in node start. A received an exception
from ParametersInjectionModule: property already configured.
> - Tried to pass that parameter in s4r deploy. Nothing changed.
> My actual s4 version is 0.6.0 final, built from src (was 0.5.0 but updated myself because
of this!)
> Any ideas? maybe I'm going with log4j... 
> Thanks + Regards

View raw message