Configure JDK logging per EAR

I try to find out how to configure the JDK logging for one application (EAR). You can't initialize it your own because you don't have a main method or something similar. Is there any configuration option to set environment settings for an application, or how to configure logging for one application.

Hi Jan,
thanks for your answer. I've already read these, but I can't exactly see how it helps me, so I redefine my needs:
- the application already has some logging implemented (using various log levels),
- I don't have admin access to the target OC4J(s),
- I'd like to define default logging levels per package, so that after deployment no configuration will be needed.
Is it possible, e.g. by packaging j2ee-logging.xml into the EAR? (I've already tried that without success.)
Thanks,
Patrik

Similar Messages

JDK Logging configuration

Hi ,
trying to configure logging for an EAR application.
Environment:
============
Oracle fustion middlware 11g (Weblogic 10.3)
OS: 64bit RH linux
Deployment target for the application is the AdminServer in the ECM domain. This domain constains the managed server UCM_server1 and IBR_server1.
WL Startup params for logging:
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger
-Djava.util.logging.config.file=/opt/oracle/middleware/user_projects/domains/ecm_domain/logging.properties
admin console settings:
==============================
Environment->Servers->AdminServer->Logging the logging implementation is set to JDK
logging.properties
==================
handlers=weblogic.logging.ServerLoggingHandler,java.util.logging.FileHandler
.level=INFO
#default file output is in user's home directory.
java.util.logging.FileHandler.pattern = /opt/oracle/middleware/user_projects/domains/ecm_domain/cust.log
java.util.logging.FileHandler.limit = 50000
java.util.logging.FileHandler.count = 1
java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
# Limit the message that are printed on the console to INFO and above.
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter
weblogic.logging.ServerLoggingHandler.level=FINE
# set 3rd party libs to SEVERE
org.apache.commons.level=SEVERE
org.apache.commons.httpclient.level=SEVERE
httpclient.wire.level=SEVERE
org.apache.struts2.level=SEVERE
# com.opensymphony.level=SEVERE
com.opensymphony.level=SEVERE
org.apache.tiles.level=SEVERE
org.apache.axis.level=SEVERE
org.apache.tiles.level=SEVERE
freemark.level=SEVERE
com.<our own package>.level=FINE
com.<our other package>.level=INFO
jar file setup: (according to doc http://download.oracle.com/docs/cd/E14571_01/web.1111/e13739/config_logs.htm#i1015532)
===============
placed
com.bea.core.apache.commons.logging_1.1.0.jar (found this file in modules, although the docs say wl does not ship these . . . )
com.bea.core.weblogic.commons.logging_1.4.0.0.jar (the documentation specified 1.3.0.0 but i couldn't find that one)
checked that the wlcommons-logging.jar exists in /opt/oracle/middleware/wlserver_10.3/server/lib
The deployment unit is a standard EAR file with WEB and EJB modules. Packages within APP-INF/lib and WEB-INF/lib
are various thirdparty jars (commons, struts, tiles etc.)
Unfortunately, I don't see any of the FINE (commons.Logger.debug) messages. All messages from the 3rd party packages seem to be ignored, when the severity levels were set to INFO, FINE etc.
What am i missing something in the configuration ? Are the messages (debug,info, 3rd party messages) written to another logfile ? I've checked
the console, the AdminServer.log and the cust.log files.
thanks
Michael

Hi,
i gave up on jdk logging and attepted log4j.
Found an interesting article: http://www.theserverlabs.com/blog/2010/04/22/dynamically-changing-log-level-with-weblogic-log4j-jmx-and-wlst/
and forcing JCL and log4j to read from the app classpath worked.
in the weblogic-application.xml
     <wls:prefer-application-packages>
<wls:package-name>org.apache.commons.logging.*</wls:package-name>
          <wls:package-name>org.apache.log4j.*</wls:package-name>
     </wls:prefer-application-packages>
basically this works (haven't tried the dynamic changing of loglevels). But this led to further problems.
I'm using struts2 (2.2.1) with tiles (2.0.6) plus various other 3rd party libraries. One of these libs depends on an XML implementation (xerces). When deploying with the above configuration deployment failed when the tiles container tried to initialise the definitions while reading the tiles.xml file. The problem was that it was loading the xercesImpl.jar shipped for one of the 3rd party apps.
Removing xercesImpl.ja from APP-INF/lib fixed that problem but caused the 3rd party app to fail. Upgrading the xercesImpl caused the deployment to fail (stacktrace below)
I guess i'm delving into the reamlms of classloading within weblogic. What i don't quite understand yet is if the packages org.apache.commons, and log4j where specified as those to be preferred from the local classpath why would that effect the loading of the XML parser ?
I would have thought that the instructiosn above mean 'only prefer those packages from the APP-INF/lib dir' ...
any help in this matter would be greatly appreciated.
thanks,
Michael
weblogic.management.DeploymentException: javax.xml.stream.XMLStreamException: Premature end of file encountered
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:188)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
     Truncated. see log file for complete stacktrace
Caused By: javax.xml.stream.XMLStreamException: Premature end of file encountered
     at weblogic.xml.stax.XMLStreamReaderBase.prime(XMLStreamReaderBase.java:69)
     at weblogic.xml.stax.XMLStreamReaderBase.setInput(XMLStreamReaderBase.java:99)
     at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:316)
     at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:49)
     at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:111)
     Truncated. see log file for complete stacktrace
>
<09.05.2011 10:17 Uhr MESZ> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1304929068317' for task '0'. Error is: 'weblogic.management.DeploymentException: javax.xml.stream.XMLStreamException: Premature end of file encountered'
weblogic.management.DeploymentException: javax.xml.stream.XMLStreamException: Premature end of file encountered
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:188)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:89)
     Truncated. see log file for complete stacktrace
Caused By: javax.xml.stream.XMLStreamException: Premature end of file encountered
     at weblogic.xml.stax.XMLStreamReaderBase.prime(XMLStreamReaderBase.java:69)
     at weblogic.xml.stax.XMLStreamReaderBase.setInput(XMLStreamReaderBase.java:99)
     at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:316)
     at weblogic.xml.stax.XMLStreamInputFactory.createXMLStreamReader(XMLStreamInputFactory.java:49)
     at weblogic.application.descriptor.BasicMunger2.<init>(BasicMunger2.java:111)

How to configure WL 10.3 to used log4j instead of jdk logging

Hi,
How can I configure WL 10.3 to use log4j instead of jdk default logging. I did changed the logging to log4j through the console for the AdminServer and one of the Managed Instance. I try to deploy axis2.war but it fails and complains about apache logger class not found. So wondering what other settings do I need. I even copied log4j-1.2.15.jar & wllog4j.jar in WL_DOMIAN\lib and restaretd the server but still gets the following error is
'weblogic.application.ModuleException: [HTTP:101216]Servlet: "AxisServlet" failed to preload on startup in Web application: "axis".
java.lang.ExceptionInInitializerError
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at java.lang.Class.newInstance0(Class.java:355)
     at java.lang.Class.newInstance(Class.java:308)
     at weblogic.servlet.internal.WebComponentContributor.getNewInstance(WebComponentContributor.java:223)
     at weblogic.servlet.internal.WebComponentContributor.createServletInstance(WebComponentContributor.java:247)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:255)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1913)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1887)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1805)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3041)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1374)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:452)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:629)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:206)
     at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:40)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: org.apache.commons.logging.LogConfigurationException: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@70b01a for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Logger) (Caused by org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@70b01a for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Logger))
     at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:543)
     at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
     at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
     at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
     at org.apache.axis2.transport.http.AxisServlet.<clinit>(AxisServlet.java:83)
     ... 50 more
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log constructor [Ljava.lang.Class;@70b01a for org.apache.commons.logging.impl.Log4JLogger (Caused by java.lang.NoClassDefFoundError: org/apache/log4j/Logger)
     at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:413)
     at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
     ... 54 more
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
     at java.lang.Class.getDeclaredConstructors0(Native Method)
     at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
     at java.lang.Class.getConstructor0(Class.java:2699)
     at java.lang.Class.getConstructor(Class.java:1657)
     at org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:410)
     ... 55 moreThanks

Go to Environments >> servers>> adminServer >> logging >> advanced
change the default JDK logging to log4j
by default weblogic provides two types of logging JDK and log4j

Error in ESS Personal information on deployment of ess/per.ear

Dear Gurus,
we have configure NWDI on our development server. we successfully checkout ess/in/bank application and made changes to a lable UI element to notice it on our server. since it refers to ess/per application, we check-out that too and deployed by right click--> deploy on the sandbox server(not dev server by normal route of check-in).
after successful deployment all personal information services address, bank e.t.c are not working properly.
Please suggest what to do.
shall I copy the ess/per.ear file from dev to sandbox ?
regards,
Ankur

Detailed error log is:
Exception occured during processing of Web Dynpro application sap.com/essinfam/Per_Family_IN. The causing exception is nested.
[EXCEPTION]
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.sap.xss.hr.per.in.family.overview.VcPerFamilyINOverview. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:51)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:382)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createVACComponentUsage(FPMComponent.java:747)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:867)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:712)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(AccessController.java:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:44)
at java.lang.reflect.Constructor.newInstance(Constructor.java:315)
at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)
... 57 more
Caused by: java.lang.UnsupportedClassVersionError: (com/sap/xss/per/model/mac/Hrxss_Per_Subtype_Info) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:254)
at com.sap.engine.services.deploy.server.ApplicationLoader.defineClassWithInterception(ApplicationLoader.java:168)
at com.sap.engine.services.deploy.server.ApplicationLoader.loadLocalClass(ApplicationLoader.java:140)
at com.sap.engine.frame.core.load.ReferencedLoader.loadRefClass(ReferencedLoader.java:573)
at com.sap.engine.core.classload.impl0.LoaderInfo.loadClassByReference(LoaderInfo.java:34)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClassByReference(ReferencedLoader.java:301)
at com.sap.engine.frame.core.load.ResourceLoader.loadClass(ResourceLoader.java:119)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:365)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:119)
at com.sap.xss.hr.per.in.family.overview.wdp.InternalVcPerFamilyINOverview.<init>(InternalVcPerFamilyINOverview.java:47)
... 62 more

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.

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.

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

Please can someone help me out. I initial configure my bluetooth stereo ear piece with my iphone 4 and it was working but I mistakenly forget the bluetooth device and I cannot reconfigure it again with my iphone 4.

please can someone help me out. I initial configure my bluetooth stereo ear piece with my iphone 4 and it was working but I mistakenly forget the bluetooth device and I cannot reconfigure it again with my iphone 4?

place the device in pairing mode and re-pair.
If you don't know how to do this, go to the manufacturer's website and download the user guide for your device.

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

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.

New handlers for JDK Logging

Does anyone know of any OpenSource Handlers for JDK Logging such as a JMS Handler, JDBC Handler, SMPT Handler or Daily Rolling File Handler? I would love to use JDK instead of Log4J, but the latter supplies these handlers (appenders) out of the box.

Huh?
If you are looking for open source anyways then why not just use log4j?

Jdk logging api

iam using jdk logging api. I've a scenario,
where there are two subclasses for a parent one.
is it suffice to use Logger.getLogger("packagename.superclass");
in the parent class, for all the subclasses to use the same logging medium.
Thanks

What happened when you tried that?

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

How or where can I configure characters match per row in photoshop touch?

how or where can I configure characters match per row in photoshop touch?

You should ask that question over in the companion app forum http://forums.adobe.com/community/photoshop/touchapps?view=all

Configure JDK logging per EAR

Similar Messages

Maybe you are looking for