WebSphere Application Server - Controlling logging and tracing in WAS 6 ND

This is Interesting: Free IT Magazines  
Home > Archive > WebSphere Application Server > January 2006 > Controlling logging and tracing in WAS 6 ND





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Controlling logging and tracing in WAS 6 ND

2006-01-29, 9:47 pm

Hi,
we have migrated an application from WAS 5.1 ND to WAS 6.0 ND.

In our application we are using the JDK 1.4 logging functionality and in WAS 5.1 we were able to set the log levels according to our needs in a logging.properties file and using the java.util.logging.config.file system property to locate it (as specified
in the Java 1.4 api - see http://java.sun.com/j2se/1.4.2/docs...LogManager.html). Using this mechanism we were able to see the log messages at level FINE and lower in the SystemErr.log file.

In WAS 6.0 however, we are not able to use the JDK logging framework in the same way (the java.util.logging.config.file system property is ignored even if it's set as one of the JVM properties at server startup) and we only way we have found to be able to
see the the log messages at level FINE and lower is by enabling the WebSphere trace functionality. Using the WebSphere tracing functionality means that our log messages are stored in the trace.log file together with other messages not generated by our ap
plication but still using log level of FINE or lower. Some examples:

[27/01/06 15:54:34:163 GMT] 0000004c JNDIDataSourc 3 Opening connection: com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@263fd856
[27/01/06 15:54:34:163 GMT] 0000004c JNDIDataSourc 3 Closing connection: com.ibm.ws.rsadapter.jdbc.WSJdbcConnection@263fd856
[27/01/06 15:54:34:163 GMT] 0000004c RWLock 3 Thread[WebContainer : 2,5,main] got writelock, GivenLocks = -1
[27/01/06 15:54:34:163 GMT] 0000004c RWLock 3 Thread[WebContainer : 2,5,main] released lock, GivenLocks = 0
[27/01/06 15:54:34:163 GMT] 0000004c RWLock 3 Thread[WebContainer : 2,5,main] got readlock, GivenLocks = 1

Is there any way in WAS 6.0 ND to force the JVM to use the settings specified in a logging.properties file located using the java.util.logging.config.file system property? If this is not possible and using the WebSphere tracing service is the only mechani
sm available, is it possible to stop it from printing the additional messages listed above?

PS I've tried the approach described in http://www-1.ibm.com/support/docvie...8&cc=uk&lang=en but it didnt help us


Thanks for any help on this

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com