Configuring Kodo logging ...

Question

Hi Guys,
Can somebody help me on this one? I have been banging my head against wall
for quite a while.
I am basically trying to limit the amount of logging Kodo produces by
providing log4j.properties (attached bellow).
We have Kodo (2.4.2) deployed on Websphere (WAS 5.0) server. For some
reason, Kodo libraries need to be deployed via Websphere extension
classloader (../websphere/AppServer/lib/ext).
To eliminate the classloader issues, I have tried heaps of locations for
the log4j.properties and to my surprise, none of it worked. Tested
locations included:
log4j.properties in (../websphere/AppServer/lib/ext
log4j.properties inside of jar file in (../websphere/AppServer/lib/ext
log4j.properties in kodo.jar (desperate)
log4j.properties in ../Websphere/AppServer/properties
log4j.properties on classpath when starting the server (java -cp
xxx;log4j.properties ... )
and a few others.
As you may guess, no luck. I can get the properties file myself as shown
bellow(that is, 'log4j.properties' loads fine, '/log4j.properties' returns
null). Does Kodo look for log4j.properties or '/log4j.properties'?
The test code was classloaded from the same location as Kodo.jar etc
(../websphere/AppServer/lib/ext)
Anyway, it may be just that I am a bit fuzzy on what is exactly happening
when common-loggings/log4j initialize andI would definitelly appretiate a
pointer in the right direction if that is the case.
Kodo should use log4j as long as the log4j.1.2.7.jar file is present on
the classpath, right?
Thank you for your help!
Petr
Testing code loading the properties:
URL ps = getClass().getClassLoader().getResource("log4j.properties");
          URL ps2 = getClass().getClassLoader().getResource("/log4j.properties");
          URL sps =
               getClass().getClassLoader().getSystemClassLoader().getResource("log4j.properties");
          URL sps2 =
               getClass().getClassLoader().getSystemClassLoader().getResource("/log4j.properties");
          System.out.println("CheckClassPath - log4j.properties: " + ps);
          System.out.println("CheckClassPath - /log4j.properties: " + ps2);
          System.out.println("CheckClassPath system - log4j.properties: " + sps);
          System.out.println("CheckClassPath system - /log4j.properties: " + sps2);
Output snippet:
[1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath -
log4j.properties:
file:/C:/Program%20Files/WebSphere/AppServer/properties/log4j.properties
[1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath -
/log4j.properties: null
[1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath system
- log4j.properties:
file:/C:/Program%20Files/WebSphere/AppServer/properties/log4j.properties
[1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath system
- /log4j.properties: null
log4j.properties:
# Set root logger level to DEBUG and its only appender to A1.
log4j.rootCategory=ERROR, console
#Subsystem level settings
log4j.logger.servicenet.core =DEBUG
log4j.logger.servicenet.core.test =FATAL
#KODO - disabled
log4j.rootCategory=ERROR, console
log4j.category.com.solarmetric.kodo = ERROR, console
log4j.category.com.solarmetric.kodo.impl.jdbc.SQL=FATAL, console
log4j.category.com.solarmetric.kodo.impl.jdbc.JDBC=FATAL, console
log4j.category.com.solarmetric.kodo.impl.jdbc.Schema=ERROR, console
log4j.category.com.solarmetric.kodo.Performance=ERROR, console
log4j.category.com.solarmetric.kodo.MetaData=ERROR, console
log4j.category.com.solarmetric.kodo.Enhance=ERROR, console
log4j.category.com.solarmetric.kodo.Query=ERROR, console
log4j.category.com.solarmetric.kodo.Runtime=ERROR, console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.layout=org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n

Answer 1

I'm afraid I don't get it. Can someone tell me specifically, what to
do, to prevent kodo from logging anything to stdout (or anywhere else,
really)
I do not want to adjust my log4j root logging verbosity, as I use that
for my application too.
Preferably I should be able to do this from the kodo.properties file
itself, rather than play
guess-where-in-the-classpath-is-the-proper-log4j.properties file.
Petr Bulanek wrote:
Hi Stephen,
That was it. Man, I would like to buy you a drink!!! :-))))
I should not forget Marc, you guys are all great!
Thank you!!!
Petr
Stephen Kim wrote:
I think the property you are looking for is:
org.apache.commons.logging.LogFactory
See further documentation on Jakarta's logging page at:
http://jakarta.apache.org/commons/logging/api/org/apache/commons/logging/package-frame.html
Petr Bulanek wrote:
Hi Stephen,
Thank you for your reply.
I have tried the following combinations in my startServer.bat script:
SET LOG4J=-Dlog4j.configuration=file:/c:/log4j.properties
and
SET LOG4J=-Dlog4j.configuration=/log4j.properties
"%JAVA_HOME%binjava" %LOG4J% %WAS_TRACE% %DEBUG% %CONSOLE_ENCODING%
"%CLIENTSAS%" "-classpath" "%WAS_CLASSPATH%;/log4j.properties;"
"-Dws.ext.dirs=%WAS_EXT_DIRS%;c:/log4j.properties;" %USER_INSTALL_PROP%
"-Dwas.install.root=%WAS_HOME%" "com.ibm.ws.bootstrap.WSLauncher"
"com.ibm.ws.management.tools.WsServerLauncher" "%CONFIG_ROOT%"
"%WAS_CELL%" "%WAS_NODE%" %*
and none of them made any difference. I wonder if it could be the case
that Kodo is not using log4j, but some other logging method instead.
Could just having jdk 1.4 installed make any difference? Is there anything
I can do to force Kodo to use log4j instead of relying on default
initialization of common-loggings?
Thank you,
Petr
You might want to set the system property explicity:
from log4j's docs:
Set the resource string variable to the value of the log4j.configuration
system property. The preferred way to specify the default initialization
file is through the log4j.configuration system property. In case the
system property log4j.configuration is not defined, then set the string
variable resource to its default value "log4j.properties".
Petr Bulanek wrote:
Hi Guys,
Can somebody help me on this one? I have been banging my head against wall
for quite a while.
I am basically trying to limit the amount of logging Kodo produces by
providing log4j.properties (attached bellow).
We have Kodo (2.4.2) deployed on Websphere (WAS 5.0) server. For some
reason, Kodo libraries need to be deployed via Websphere extension
classloader (../websphere/AppServer/lib/ext).
To eliminate the classloader issues, I have tried heaps of locations for
the log4j.properties and to my surprise, none of it worked. Tested
locations included:
log4j.properties in (../websphere/AppServer/lib/ext
log4j.properties inside of jar file in (../websphere/AppServer/lib/ext
log4j.properties in kodo.jar (desperate)
log4j.properties in ../Websphere/AppServer/properties
log4j.properties on classpath when starting the server (java -cp
xxx;log4j.properties ... )
and a few others.
As you may guess, no luck. I can get the properties file myself as shown
bellow(that is, 'log4j.properties' loads fine, '/log4j.properties' returns
null). Does Kodo look for log4j.properties or '/log4j.properties'?
The test code was classloaded from the same location as Kodo.jar etc
(../websphere/AppServer/lib/ext)
Anyway, it may be just that I am a bit fuzzy on what is exactly happening
when common-loggings/log4j initialize andI would definitelly appretiate a
pointer in the right direction if that is the case.
Kodo should use log4j as long as the log4j.1.2.7.jar file is present on
the classpath, right?
Thank you for your help!
Petr
Testing code loading the properties:
URL ps = getClass().getClassLoader().getResource("log4j.properties");
          URL ps2 = getClass().getClassLoader().getResource("/log4j.properties");
          URL sps =
               getClass().getClassLoader().getSystemClassLoader().getResource("log4j.properties");
          URL sps2 =
               getClass().getClassLoader().getSystemClassLoader().getResource("/log4j.properties");
          System.out.println("CheckClassPath - log4j.properties: " + ps);
          System.out.println("CheckClassPath - /log4j.properties: " + ps2);
          System.out.println("CheckClassPath system - log4j.properties: " + sps);
          System.out.println("CheckClassPath system - /log4j.properties: " +sps2);
Output snippet:
[1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath -
log4j.properties:
file:/C:/Program%20Files/WebSphere/AppServer/properties/log4j.properties
[1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath -
/log4j.properties: null
[1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath system
- log4j.properties:
file:/C:/Program%20Files/WebSphere/AppServer/properties/log4j.properties
[1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath system
- /log4j.properties: null
log4j.properties:
# Set root logger level to DEBUG and its only appender to A1.
log4j.rootCategory=ERROR, console
#Subsystem level settings
log4j.logger.servicenet.core =DEBUG
log4j.logger.servicenet.core.test =FATAL
#KODO - disabled
log4j.rootCategory=ERROR, console
log4j.category.com.solarmetric.kodo = ERROR, console
log4j.category.com.solarmetric.kodo.impl.jdbc.SQL=FATAL, console
log4j.category.com.solarmetric.kodo.impl.jdbc.JDBC=FATAL, console
log4j.category.com.solarmetric.kodo.impl.jdbc.Schema=ERROR, console
log4j.category.com.solarmetric.kodo.Performance=ERROR, console
log4j.category.com.solarmetric.kodo.MetaData=ERROR, console
log4j.category.com.solarmetric.kodo.Enhance=ERROR, console
log4j.category.com.solarmetric.kodo.Query=ERROR, console
log4j.category.com.solarmetric.kodo.Runtime=ERROR, console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.layout=org.apache.log4j.PatternLayout
log4j.appender.console.layout.ConversionPattern=%-4r [%t] %-5p %c %x -%m%n
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com