Add log optimization bit to prove the JIT will still run expensive methods in

parameterized logging methods even though they may be omitted in an uncommon trap.
e.g. if debug is disabled.

Author: manolama

log4j.xml

@@ -0,0 +1,23 @@
+<Configuration name="ConfigTest" status="ERROR" monitorInterval="5">
+  <Appenders>
+ 
+    <SystemPropertyArbiter propertyName="env" propertyValue="dev">
+      <Console name="Out">
+        <PatternLayout pattern="%m%n"/>
+      </Console>
+    </SystemPropertyArbiter>
+    <SystemPropertyArbiter propertyName="env" propertyValue="prod">
+      <List name="Out">
+      </List>
+    </SystemPropertyArbiter>
+ 
+  </Appenders>
+  <Loggers>
+    <Logger name="org.apache.test" level="trace" additivity="false">
+      <AppenderRef ref="Out"/>
+    </Logger>
+    <Root level="error">
+      <AppenderRef ref="Out"/>
+    </Root>
+  </Loggers>
+</Configuration>

logback.xml

@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<configuration>
+  <!--<jmxConfigurator/>-->
+  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
+    <encoder>
+      <pattern>
+        %d{ISO8601} %-5level [%thread] %logger{0}: %msg%n
+      </pattern>
+    </encoder>
+  </appender>
+  
+  <logger name="org.apache.zookeeper" level="INFO"/>
+  <logger name="org.hbase.async" level="INFO"/>
+  <logger name="com.stumbleupon.async" level="INFO"/>
+  
+  <!-- Fallthrough root logger and router -->
+  <root level="INFO">
+    <appender-ref ref="STDOUT"/>
+    <!-- Uncomment to log to file -->
+    <!--<appender-ref ref="FILE"/>-->
+  </root>
+</configuration>