Configuration of logging severity

Hello everyone,
I am trying to use the weblogic Admin console to modify the logging severity at runtime. I have an application deployed on the AdminServer.
In the web console, I go to the AdminServer Settings page and navigate to the Logging tab. I click the "Advanced" link to show the "Logger severity properties". In this box I have tried entering many different values. I save. There is no change to the logs. I restart the server, there is still no change to the logs.
Some values I've attempted to use:
com.mycompany.level=Trace
com.mycompany.level=Debug
com.mycompany=Trace
com.mycompany=Debug
.level=Trace
.level=Debug
I am using weblogic 10.3.2.0 with jdk logging.
Does anyone know if these configuration changes are supposed to affect the log files? Am I using this configuration parameter incorrectly?
Note that I have found a way to configure the logging severity using a logging.properties file, by calling:
LogManager.getLogManager().readConfiguration(EventDAOEJBImpl.class.getResourceAsStream("/logging.properties"));
However, this does not allow me to configure the application from the weblogic console. Is there a way to configure the logging severity using the weblogic console?

You may want to ask in the WebLogic Server - Diagnostics / WLDF / SNMP forum. They own logging.
I asked them to reply to this message.

Similar Messages

How to configure the logging and tracing in J2EE-Server

Hi,
when I've been using the SAP Logging and Tracing Framework before from more or less "standalone" Applications I always used a property file which configured the levels of severity etc.. During application startup I've read this file and configured the logging properly.
In a J2EE-Environment (SAP WEB AS JAVA) I cannot read a file from a file - system. So I'm wondering where are those handlers and severity levels are configured ?
Any help is greatly appreciated.
Thanks in advance,
Frank

Hi Frank,
well, first of all, your application provides log configuration information using an XML file at deployment time. This file is called log-configuration.xml (you can see the DTD description here: http://help.sap.com/saphelp_nw04/helpdata/en/48/ef8748caed894bb4b3ae953a60c592/frameset.htm). There you can set configure log controllers, which could be two types: location and category. So, you can specify your location and severity there. This is described here: http://help.sap.com/saphelp_nw04/helpdata/en/35/671c0136b4714c9e1b16b68211287b/frameset.htm.
Then, after the application is deployed, the log configurations you provided for it are registered with the Log Configuration tool I mentioned about. Using this tool you can later on modify your configurations at runtime (for example, change the severity level) without having to redeploy the application.
I hope it's clearer now? I guess it was me not getting your first question correctly that caused your confusion.
Greetings,
Ivo

Set logging severity level for clustered servers

How can I set the logging severity level for clustered servers just once at the cluster level rather than one at a time at the server level?

I know the logging is server by server, but surely there is a way to configure the multiple servers with one change rather than one by one. We have 40 some servers in the cluster.

How to configur log4j logging for weblogic 10.1

Hi,
I am tried to set log4j logging for my application running in weblogic 10.1. I set a log4j.properties file and loaded the properties by a servlet. Where its load the properties files and configure it by PropertyConfigurator.
The same logic has worked out in websphere. But in weblogic, it is not working. I set the server logging and domain logging to Log4j in Admin console. Now it is writing all the log statements.
If i write a property for a package to Error level and root level is Debug. Its not working, all debug statements are getting written.
Can you please tell me the steps to configure log4j logging in weblogic 10.1.
Thanks & Regards,
Nasrin.N

Did you manage to get this working?
If yes ... what did you do?
I am having the same problem implementing commons-logging with log4j

Configuration Change log in Production

Hi all
Some configuration changes have been directly made in production at our client. How can we find out what changes are made? Going into SCC4 > Change logs, I could find out who made all the changes. But it does not show what configuration changes are made.
Thanks
Vamsi

Dear Vamsi,
I'm not sure whether in a single report you can fetch all the changes related to configuration for a particular module.
But I'm sure in most of the nodes the configuration change logs gets recorded.Check these links,
Re: How to find when a new Material type is created
Configuration change Log
Regards
Mangalraj.S

Configure diagnostic logging

when i select configure diagnostic logging in central admin i get the following error
error file not found
in uls logs i see the following
07/01/2014 13:25:12.93 w3wp.exe (0x1998) 0x0844 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (GET:http://vsrsp10qaapp:9999/_admin/metrics.aspx) 6c6d233a-fb35-491e-87c2-ba4ab41afeb1
07/01/2014 13:25:12.93 w3wp.exe (0x1998) 0x0844 SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ 6c6d233a-fb35-491e-87c2-ba4ab41afeb1
07/01/2014 13:25:12.95 w3wp.exe (0x1998) 0x0844 SharePoint Foundation Runtime tkau Unexpected System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Practices.ServiceLocation, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. at Microsoft.Opex.Rkm.Common.Logging.DiagnosticsService.ProvideAreas() at Microsoft.SharePoint.Administration.SPDiagnosticsServiceBase.EnsureAreas()
at Microsoft.SharePoint.Administration.SPDiagnosticsServiceBase.get_Areas() at Microsoft.SharePoint.ApplicationPages.MetricsPage.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6c6d233a-fb35-491e-87c2-ba4ab41afeb1
07/01/2014 13:25:12.96 w3wp.exe (0x1998) 0x0844 SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://vsrsp10qaapp:9999/_admin/metrics.aspx)). Execution Time=29.7579720327584 6c6d233a-fb35-491e-87c2-ba4ab41afeb1
07/01/2014 13:25:14.94 w3wp.exe (0x1998) 0x0814 SharePoint Foundation Topology e5mc Medium WcfSendRequest: RemoteAddress: 'http://vsrsp10qaapp:32843/9283a893bbd8454982688fd214f2cf85/MetadataWebService.svc' Channel: 'Microsoft.SharePoint.Taxonomy.IMetadataWebServiceApplication'
Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:6657c8c4-fd07-4545-984a-5d9121ad29f5'
07/01/2014 13:25:14.94 w3wp.exe (0x0C18) 0x1450 SharePoint Foundation Topology e5mb Medium WcfReceiveRequest: LocalAddress: 'http://vsrsp10qaapp.southerntrust.local:32843/9283a893bbd8454982688fd214f2cf85/MetadataWebService.svc'
Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/taxonomy/soap/IDataAccessReadOnly/GetChanges' MessageId: 'urn:uuid:6657c8c4-fd07-4545-984a-5d9121ad29f5' b1d3864d-60a0-4625-bb4c-7644b54846b4
07/01/2014 13:25:14.94 w3wp.exe (0x0C18) 0x1450 SharePoint Foundation Monitoring nasq Medium Entering monitored scope (ExecuteWcfServerOperation) b1d3864d-60a0-4625-bb4c-7644b54846b4
i have carried out an iisreset and restart of the server problem still exists.
health analyser is report an error
Could not load file or assembly 'Microsoft.Practices.ServiceLocation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

If you still have the WSP for that solution, use 7-Zip to open it. See if it had Microsoft.Practices.ServiceLocation.dll
in it, or if you have the developers on staff, ask.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

C:\Program Files\Microsoft Configuration Manager\Logs not updating

Hi,
Anybody exprienced the scenario where logfiles in C:\Program Files\Microsoft Configuration Manager\Logs don't update anymore?
F.e. wsyncmgr.log is of beginning of April, no recent logs there except for 7 items: smsprov.smspxe, smsdpusage (date from Today).
Pls advise.
J.
Jan Hoedt

Open ConfigMgr Service Manager and check the logging options (is logging for each component enabled at all? Is it really logging to the directory you examined?) You can also open the logs using notepad. cmtrace.exe sometimes does not display the entire
content if there are malformated lines.
Having installed ConfigMgr on the C:\ drive is not the best setup BTW.
Torsten Meringer | http://www.mssccmfaq.de

Configure commons-logging formatting

I've managed to configure commons-logging to work with WebLogic but now I'd like to configure the log-output format.
Does anyone know how to change the output format?

Yes, but the simplest thing to do is to not include
log4j.jar
If you don't want to use it, don't inlcude it.It's not possible. Our client wants a callendar. We have purchased dotj library which has a calendar. Unfortunately their library includes log4j.
But the application I have written uses commons logging and it should use jdk 1.4 logging otherwise logging doesn't work properly with SUN AS.

Configuration change Log

Hi,
I need to find the configuration change log in development system. Do we have any transaction/report/program from which we can track all the configuration changes for a perticular object.
Thanks,
Vijay

for almost all customizing you can find the change history in menu tools within the cuistomizing.

Adobe Document Services - http Response 500 - How to configure the logging?

We are building an application in Web Dynpro Java that fetches data from an R/3 system via an RFC connection and is then supposed to show said data in a pdf within an iview. For that task we want to use the InteractiveForm UIElement. We bind the data to its pdfSource in the iViewu2019s context. Currently the form only consists of a text field bound to one attribute element of the pdfSource context node.
The ADS webservice is configured according to the manuals found here:
http://help.sap.com/saphelp_nw70/helpdata/en/fa/0b700d6cfd4e03a8ec2186ba6ff4af/frameset.htm
and tested successfully under the following link
http://<portal_host>:<port>/AdobeDocumentServices/Config?style=document
However, when we execute the application, an error occurs in the webservice generating the pdf, namely Invalid Content-Type:text/html. The error occurs when the iView containing the form is shown for the first time, even before the attributes of the pdfSource context are filled with data (we expect to see an empty form).
As it seems the webservice is expected to return a MIME type of either application/pdf or text/xml (we donu2019t know for sure since the SAP manuals and forums are inconclusive here), but instead we get text/html. This seems to be due to the fact that the webservice exits with an http response 500 Internal Server Error (we used several network monitoring tools to confirm that such a response is sent). Since such http responses are but html files with an empty body, yet not xml or pdf, the aforementioned error does make sense to us, but we do not know what Internal Error has caused it.
The only help that SAP seems to provide for an error u201CInvalid Content-Type:text/htmlu201D in context with ADS points to an expiring password or otherwise poor configuration of the ADSUser, which (most certainly) is not our case here since, and as said above, the configuration was and can be tested successfully.
We then tried to view the logs for this error on the machine where the J2EE engine is running with ADS installed according to this (not very comprehensible) guide:
http://help.sap.com/saphelp_nw70/helpdata/de/97/ccfc3f0ac2c642e10000000a1550b0/frameset.htm
We cannot find anything relevant in the server.log of the Visual Administrator except this message (it is generated exactly when our error occurs u2013 the trace severity is set to ALL for all Adobe application elements according to manual):
Date , Time , Message , Severity , Category , Location , Application , User
12/08/2010 , 13:50:46:511 , application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.adobe.pdfdocument.base.core.PDFDocumentRuntimeException: Failed to GENERATEPDF
Exception id: [0800274DA7ED00850000005B00000900000496E5919E28BA] , Error , /System/Server/WebRequests , com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl , sap.com/tcwddispwda , Guest
There is no error.pdf to be found on the file system and since neither have we known nor are we told by the error message, whether the underlying cause is is a render error or connection error or configuration error or what not, we donu2019t know whether the error.pdf is supposed to be generated at all.
Or could there be any other reason why generation didnu2019t take place?
Furthermore we canu2019t seem to be able to find any logs more verbose or detailed about this issue - at least not within the Visual Administrator or the portalu2019s nwa.
How is it possible to properly debug the webservice for pdf-generation or at least to retrieve a fully detailed log containing all notifications and exception stack traces etc.?
I am assuming that we are making some basic mistakes regarding the logging configuration - but what?
Our goal is to know what causes the 500 Internal Server Error response that causes the Incorrect Content-Type exception.
We are using a NetWeaver 7.01 portal installation with Adobe Document Services 7.01 installed on a Windows Server 2003 platform.
Any help is highly appreciated!
Serg

Have you tried restarting the Java PDF object in Visual Administrator? Once you do all of your config, you have to restart the PDF object (sao.com/tcwdpdfobject) for the changes to take place. I am assuming you've run all of the test programs in SAP (FP_TEST_00, FP_TEST_03, etc.). Is there any chance that the ADSUSER is locked somehow?

How to configure NFS logging

I'm pretty new to NetApp, so excuse the lack of knowledge.That said, I need to figure out what servers are using an NFS export as we are doing some maintenance and need to take these exports down. Prior to doing so however, I'd like to know definitively which servers are accessing which shares so i can inventory the affected customers. I've been directed to Data_ONTAP_81_File_Access_and_Protocols.pdf pg 278 which says: Enabling NFS auditingYou can enable NFS auditing by performing several tasks.About this taskFor more information about the options described in these steps, see the options(1) man page.StepsIn the /etc/log directory on the storage system, create a file called nfs-audit.File sharing between NFS and CIFS | 279Note: Steps 1 and 2 are mandatory for auditing in a UNIX security style qtree but optional forauditing in NTFS or mixed security style qtrees.To identify the NFS log filter file, enter the following command:options cifs.audit.nfs.filter.filename /etc/log/nfs-auditTo enable auditing of file access events, enter the following command:options cifs.audit.file_access_events.enable onNote: Auditing of file access and logon events is turned off by default.To enable NFS auditing, enter the following command:options cifs.audit.nfs.enable onConfigure audit log management.On the Windows administration host, set the filter file’s system access control list (SACL)I've done steps 1-4 without issue. But when it comes to step 5, it gives no directives or links on how to do this. Not to mention i have no idea how to set up a SACL on the nfs-audit file. Can i get some assistance with this?

Hi Francios,
In JPDK Framework, LogManager is the configurable logging service that allows you to log messages on 7 different levels. Thus, if you would want to log messages to the application.log file, you can directly make use of the static methods in this class. The LogManager internally makes use of oracle.webdb.log.* classes.
For more details on LogManager, you can refer to the JPDKv2 API docs that come bundled along with any PDK release. The source code for LogManager also comes with the JPDK download.
As regards the oracle.webdb package, the source files are not publicly available.
Hope that helps.
Regards,
Abhinav

Receiver Adapter configuration to put several file

Hi Experts,
I want to treat several file in one « step ». For that I configured sender file adapter to pick several file by check Additional file(s).
Additional file appear in payload correctly but I donu2019t know how to configure receiver adapter to add them to output directory.
How can I configure Receiver Adapter to do that?
Thank you.

In sender adapter it works fine, but I don't know how to add them in the receiver adapter.
As per documentation, you need a receiver that supports attachments to make use of this functionality.
For example you can send the additional files from file sender as attachments to mail receiver.
Unfortunately, the attachments are supported only for file sender and you can't add attachments in file receiver.
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm
Check the 'attachment' column to know the adapters that supports attachments.

How to configure weblogic log file?

HI
How do i configure Weblogic server log file to log weblogic related information as well as my application?
I need to maintain one log file for weblogic and my application.
Thanks,

Then glassfish instance is either not configured yet or installed somewhere else. Try looking under your user's home directory like C:\Documents and Settings\<username>\Application Data\glassfish\domains\domain1\logs

"...installer has been mis-configured" issues - LOG INCLUDED

Hi all,
I have an Acer Aspire laptop running Windows 7 Home Premium 64 bit.
I am trying to udate Picaboo X and everytime I open the application I get this error message:
"Sorry an error has occured.
This application cannot be installed because this installer has been mis-configured. Please contact the application author for assistance."
Here is my installation log from Adobe AIR:
[2013-11-21:11:33:35] Runtime Installer begin with version 3.9.0.1210 on Windows 7 x86
[2013-11-21:11:33:35] Commandline is:
[2013-11-21:11:33:35] No installed runtime detected
[2013-11-21:11:33:40] Relaunching with elevation
[2013-11-21:11:33:40] Launching subprocess with commandline c:\users\michael\appdata\local\temp\aire10d.tmp\adobe air installer.exe -ei
[2013-11-21:11:33:44] Runtime Installer begin with version 3.9.0.1210 on Windows 7 x86
[2013-11-21:11:33:44] Commandline is: -stdio \\.\pipe\AIR_6088_0 -ei
[2013-11-21:11:33:44] No installed runtime detected
[2013-11-21:11:33:44] Starting silent runtime install. Installing runtime version 3.9.0.1210
[2013-11-21:11:33:45] Installing msi at c:\users\michael\appdata\local\temp\aire10d.tmp\setup.msi with guid {52E225FC-FCB4-41F7-837B-6E37FB05BD7B}
[2013-11-21:11:33:49] Runtime Installer end with exit code 0
[2013-11-21:11:33:49] Elevated install completed
[2013-11-21:11:33:52] Launching subprocess with commandline c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Resources\Adobe AIR Updater -installupdatecheck
[2013-11-21:11:33:52] Runtime Installer end with exit code 0
[2013-11-21:11:33:53] Runtime Installer begin with version 3.9.0.1210 on Windows 7 x86
[2013-11-21:11:33:53] Commandline is: -installupdatecheck
[2013-11-21:11:33:53] Installed runtime (3.9.0.1210) located at c:\Program Files (x86)\Common Files\Adobe AIR
[2013-11-21:11:33:55] Performing pingback request
[2013-11-21:11:33:55] Starting runtime background update check
[2013-11-21:11:33:55] Begin Background update download from http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.9.0.1210/update
[2013-11-21:11:33:55] Unpackaging http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.9.0.1210/update to C:\Users\Michael\AppData\Roaming\Adobe\AIR\Updater\Background
[2013-11-21:11:33:55] Runtime update not available
[2013-11-21:11:33:55] Unpackaging cancelled
[2013-11-21:11:33:55] Runtime Installer end with exit code 0
[2013-11-21:11:34:22] Application Installer begin with version 3.9.0.1210 on Windows 7 x86
[2013-11-21:11:34:22] Commandline is: -update "c:\program files (x86)\picaboo x\picaboo x.exe" "C:\Users\Michael\AppData\Roaming\com.picaboo.Picaboo.A382D4714709B456C4E0088DFC1F7243AF9 EBF75.1\Local Store\#ApplicationUpdater\update.air" 11.0P
[2013-11-21:11:34:22] Installed runtime (3.9.0.1210) located at c:\Program Files (x86)\Common Files\Adobe AIR
[2013-11-21:11:34:23] Installed app (com.picaboo.Picaboo.A382D4714709B456C4E0088DFC1F7243AF9EBF75.1) located at c:\program files (x86)\picaboo x\picaboo x.exe
[2013-11-21:11:34:24] Unpackaging file:///C:/Users/Michael/AppData/Roaming/com.picaboo.Picaboo.A382D4714709B456C4E0088DFC1F 7243AF9EBF75.1/Local%20Store/%23ApplicationUpdater/update.air to C:\Users\Michael\AppData\Local\Temp\flaC025.tmp
[2013-11-21:11:34:25] Application signature verified
[2013-11-21:11:34:25] Unpackaging/validation complete
[2013-11-21:11:34:25] The certificate of the installed app fails to match either the signature or migration signature of the AIR file
[2013-11-21:11:34:41] Launching subprocess with commandline c:\program files (x86)\picaboo x\picaboo x.exe
[2013-11-21:11:34:41] Application Installer end with exit code 9
I wasn't sure if it was AIR messing up or Picaboo X messing up. Any help would be much appreciated.

Turns out it was the Picaboo. I uninstalled and reinstalled and things are working properly.

Configuring Kodo logging ...

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

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

Configuration of logging severity

Similar Messages

Maybe you are looking for