there is no parent child relationship with log4j configuration resolution, to see how log4j finds its configuration, enable the system property log4j.debug via the start script of jvm command line using -Dlog4j.debug=true and it will output to stderr as it tries various options. Typically it will resolve a file using the classpath.
some more detail in the docs for log4j: http://logging.apache.org/log4j/1.2/manual.html#defaultInit On 31 August 2010 18:32, Ben Stover <bxsto...@yahoo.co.uk> wrote: > Is ActiveMQ log4j default configuration = child first? > > In other words: If I setup an own log4j.properties file in a deployed bean: > has this special log4j.properties > priority over the general default log4j.propertoes? > > If not: Where exactly can setup ActiveMQ for child-first (instead of parent > first) ? > > Ben > > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
