Deprecated log level constants

Hi,
In my DB class I have the following:
sssn.setLogLevel(DefaultSessionLog.FINE);
where sssn is a Server session. In Eclipse I'm getting the warning:
The field SessionLog.FINE is deprecated
I can see in the javadoc that that is the case but as far as I can tell there are no other constants defined and I should just use int:s to avoid the warnings.
I'm reluctant to do that since that is not as descriptive as the constant and what if the int:s representinh the desired level change in a future relase?
Am I missin something here or did Oracle miss something when they deprecated the level constants and not just the methods of the class?
Regards,
Andrei

Andrei,
We did miss something here. When SessionLog (oracle.toplink.sessions) was deprecated and the new SessionLog (oracle.toplink.logging) was introduced we ensured backwards compatibility through inheritance.
I have also seen the issue within JDeveloper when I use SessionLog (oracle.toplink.logging) statics. The warning shows in the code editor but I do not get any compiler warning for the deprecation.
The issue is that in this case we did not replicate the statics to the non-deprecated classes. This issue has been logged and will be addressed in a future release.
Doug

Similar Messages

How do I set the logging level with the plug-in 1.4

I am writing an applet that will be hosted in the plug-in version 1.4. I'd like to set up some logging statements using the java.util.logging API. I have successfully got it to print out log messages, but it is not printing anything below level INFO. How can I set it up to print out log statements at the FINEST level?

If you are using the default logger for logging from the applet, the default log level from the logging.properties file in your JRE lib directory is the place. There is an entry
.level= INFO In this file. You can modify this entry.
This is a a roundabout way of achieving it. since we are modifying the default log level here, it will be used by other java applications as well. I am looking for a better solution.

Error while Changing log level in Agentry 6.0.44.1

Hi ,
I am trying to change the log level from the Agentry Administration client, but i am getting the below error message.
And it is showing any option to change the log levels for users. How can I change log level for users also.
How can I resolve this error.
Regards,
Shyam

Shyam,
This is fixed or planned fixed in 6.0.46 Agentry Server (supposed to be available anytime soon in the Service Marketplace - it was submitted already to the SMP team). The fix was in SMP 2.3 and SMP 3.0 but it was ported back to the Agentry 6.0.X release. If you have no access to the Agentry 6.0.X patches this means that your SAP License is preventing you from downloading it. You may need to contact the SAP CIC (customer interaction center) group.
Or you can do the manual setup for a workaround for now.
SAP KBA article: 2048202 - AgentryGUI does not allow to change log settings - Not all setttings were successfully changed.
Regards,
Mark Pe
SAP Senior Support Engineer (Mobility)

Setting log level of an appender

I have 2 appenders in my logger.
mergeLogger.addAppender( consoleAppender );
mergeLogger.addAppender( fileAppender );
to set the log level I use logger.setLevel( XX ) but this applies to all appenders
Is it possible to set the logging level for each appender to different levels?

Have you read the log4j documentation?

Setting logging level

Hello folks;
Is there a way to set the logging threshold for log messages sent to
the weblogic log? I see where to adjust logging threshold for the
standard out, but this level doesn't seem to affect the threshold for
messages getting to the physical logfile. Unlike the log4j classes
that seem to back up weblogic's logging ( I checked this out by
looking in the weblogic.jar file); there are no methods for setting
the logging threshold on weblogic's log classes.
Cheers-

I was mistaken about the log4j stuff being used under the covers.
However, changing the logging threshold does not seem to affect
messages sent to the log for my server. I just tested this again by
setting the log level to "CRITICAL" in the console. Sure enough the
messages sent to the standard out console are affected, but the
messages sent to the physical log are not affected. I still get Info,
Notice, etc messages there--- but nearly no messages to the standard
out console.
This was done on version 7.0 of weblogic.
Cheers--
"Jane Sampson" <[email protected]> wrote in message news:<3e5a84b4$[email protected]>...
Hi Steve,
If you set the logging level in the Logging tab on Server Configuration, it
DOES affect the level of messages that are logged to both stdout and the
physical log. Are you sure you are looking at the correct log file?
Also, none of the weblogic classes use log4j. What version did you find
log4j classes included in the weblogic.jar??
Jane
BEA Support

Could you tell me what's the meaning of the logfile-path and log-level?

we are running an productive xml database. but it is not stable now. Sometime it would report resource conflict error while you access xmldb via http protocol. I read the database logs and listener logs, but no abnormal message could be found. So, I want to find more information from the xmldb logs. While I run select DBMS_XDB.cfg_get().getclobval() from dual, I found that there are several logfile-path and log-level tags and I guess that these would be xmldb logs. Does anyone know what's the meaning of these tags?

I wondered about that one often too. I didn't have a chance yet to investigate (but maybe Mark will elaborate a little here), my guess is that it / or will be a possibility to enable tracing regarding the protocols or servlets.
Though It look like if you enable it it will trace to the XML file defined in the xdbconfig.xml. I also guess that (because there is also a XSD counterpart) that one could create an resource that streams the errors into a XDB ftp or http or ... xmltype table based on these settings.
This would be great because it would mature the protocol server regarding functionality. You could enable the tracing and see what happens. Until now the documentation doesn't give much extra insight...

<element name="ftpconfig">
<complexType><sequence>
<element name="ftp-port" type="unsignedShort" default="2100"/>
<element name="ftp-listener" type="string"/>
<element name="ftp-protocol" type="string"/>
<element name="logfile-path" type="string" default="/sys/log/ftplog.xml"/>
<element name="log-level" type="unsignedInt" default="0"/>
<element name="session-timeout" type="unsignedInt" default="6000"/>
<element name="buffer-size" default="8192">
<simpleType>
<restriction base="unsignedInt">
<minInclusive value="1024"/> 
<maxInclusive value="1048496"/> 
</restriction>
</simpleType>
</element>
<element name="ftp-welcome-message" type="string" minOccurs="0"
maxOccurs="1"/>
</sequence></complexType>
</element>

<element name="httpconfig">
<complexType><sequence>
<element name="http-port" type="unsignedShort" default="8080"/>
<element name="http-listener" type="string"/>
<element name="http-protocol" type="string"/>
<element name="max-http-headers" type="unsignedInt" default="64"/>
<element name="max-header-size" type="unsignedInt" default="4096"/>
<element name="max-request-body" type="unsignedInt" default="2000000000"
minOccurs="1"/>
<element name="session-timeout" type="unsignedInt" default="6000"/>
<element name="server-name" type="string"/>
<element name="logfile-path" type="string"
default="/sys/log/httplog.xml"/>
<element name="log-level" type="unsignedInt" default="0"/>
<element name="servlet-realm" type="string" minOccurs="0"/>
...etc...

ODI Log Level

Hi,
I am looking for a description of ODI Log Levels.
I know that the log level controls the details of the log output in ODI operator, but does exists some more detailed documentation about it?
I would need information like what details are shown in which log level.
Thanks in advance!
Cheers,
H.

It is important to understand that the way odi works, it uses the "log" to drive all executuions. When you start a scenario, it copies eachof the steps of the scenarios into the execution log with the session ID, and wih a status of Waiting. As it executes each, it marks it as being executed, and when complete, marks it as completed (in or or successfully). When it has executed all the steps, it will go back to the log and selectively delete the entries there. When you execute the scenario, you execute it with a log-level of 0-5, and ODI will basically delete all entries in the log with a level > your chosen level. If you inspect the steps of a KM, Procedure etc, you will see that each has a log-level associated with it. This is what will decide if it is to be kept or not.
If the session ends in failure, it will keep all the entries.

Eclipselink log levels issue with weak references

Hi all,
Is it possible to get null pointer exceptions if the log level in eclipselink is set to FINEST and you are logging a weak reference probably in a IdentityWeakReferenceMap and getting a null pointer exception because the weak ref has been garbage collected ?
-Prashanth.

I am getting Nullpointer exception when I set log level to FINER or FINEST in persistence.xml.
DisRootEntityRef entity which is seen in below log has week reference in erml.
Here is the exception full trace:
EL Warning: 2010-05-31 17:06:52.328--UnitOfWork(19025200)--Thread(Thread[)--java.lang.NullPointerException
at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.getRootEntity(DisRootEntityRefDAO.java:300)
at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.getToString(DisRootEntityRefDAO.java:591)
at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.toString(DisRootEntityRefDAO.java:584)
at java.text.MessageFormat.subformat(MessageFormat.java:1246)
at java.text.MessageFormat.format(MessageFormat.java:836)
at java.text.Format.format(Format.java:140)
at java.text.MessageFormat.format(MessageFormat.java:812)
at org.eclipse.persistence.internal.localization.EclipseLinkLocalization.buildMessage(EclipseLinkLocalization.java:77)
at org.eclipse.persistence.internal.localization.TraceLocalization.buildMessage(TraceLocalization.java:30)
at org.eclipse.persistence.logging.AbstractSessionLog.formatMessage(AbstractSessionLog.java:801)
at org.eclipse.persistence.platform.server.ServerLog.log(ServerLog.java:71)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:2571)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3664)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3636)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3612)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3534)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.logDebugMessage(UnitOfWorkImpl.java:5397)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerExistingObject(UnitOfWorkImpl.java:3874)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerExistingObject(UnitOfWorkImpl.java:3844)
at org.eclipse.persistence.queries.ObjectBuildingQuery.registerIndividualResult(ObjectBuildingQuery.java:362)
at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildWorkingCopyCloneNormally(ObjectBuilder.java:588)
at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObjectInUnitOfWork(ObjectBuilder.java:549)
at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:489)
at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:441)
at org.eclipse.persistence.queries.ObjectLevelReadQuery.buildObject(ObjectLevelReadQuery.java:635)
at org.eclipse.persistence.queries.ReadAllQuery.registerResultInUnitOfWork(ReadAllQuery.java:838)
at org.eclipse.persistence.queries.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:464)
at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:997)
at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:670)
at org.eclipse.persistence.queries.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:958)
at org.eclipse.persistence.queries.ReadAllQuery.execute(ReadAllQuery.java:432)
at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:1021)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2858)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1225)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1207)
at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiate(QueryBasedValueHolder.java:85)
at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiate(QueryBasedValueHolder.java:75)
at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:83)
at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiateImpl(UnitOfWorkValueHolder.java:161)
at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiate(UnitOfWorkValueHolder.java:230)
at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:83)
at org.eclipse.persistence.indirection.IndirectList.buildDelegate(IndirectList.java:237)
at org.eclipse.persistence.indirection.IndirectList.getDelegate(IndirectList.java:397)
at org.eclipse.persistence.indirection.IndirectList$1.(IndirectList.java:525)
at org.eclipse.persistence.indirection.IndirectList.listIterator(IndirectList.java:524)
at org.eclipse.persistence.indirection.IndirectList.iterator(IndirectList.java:488)
at oracle.communications.platform.persistence.impl.PomsArrayList.iterator(PomsArrayList.java:598)
at oracle.communications.platform.entity.impl.DisResultGroupDAO.getRootEntities(DisResultGroupDAO.java:765)
at oracle.communications.integrity.scanCartridges.sdk.RootEntityLoaderImpl.(RootEntityLoaderImpl.java:37)
at oracle.communications.integrity.scanCartridges.sdk.BaseDiscrepancyDetectionController.init(BaseDiscrepancyDetectionController.java:71)
at oracle.communications.integrity.scanCartridges.sdk.BaseDiscrepancyDetectionController.invoke(BaseDiscrepancyDetectionController.java:41)
at oracle.communications.integrity.cartridges.ciscoextensioncartridge.detectionplugins.ciscodiscrepancydetectionsample.CiscoDiscrepancyDetectionSampleMessageDrivenBean.onMessage(CiscoDiscrepancyDetectionSampleMessageDrivenBean.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy343.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
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)
oracle.communications.integrity.cartridges.ciscoextensioncartridge.detectionplugins.ciscodiscrepancydetectionsample.CiscoDiscrepancyDetectionSampleMessageDrivenBean
java.lang.NullPointerException
at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.getRootEntity(DisRootEntityRefDAO.java:300)
at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.getToString(DisRootEntityRefDAO.java:591)
at oracle.communications.platform.entity.impl.DisRootEntityRefDAO.toString(DisRootEntityRefDAO.java:584)
at java.text.MessageFormat.subformat(MessageFormat.java:1246)
at java.text.MessageFormat.format(MessageFormat.java:836)
at java.text.Format.format(Format.java:140)
at java.text.MessageFormat.format(MessageFormat.java:812)
at org.eclipse.persistence.internal.localization.EclipseLinkLocalization.buildMessage(EclipseLinkLocalization.java:77)
at org.eclipse.persistence.internal.localization.TraceLocalization.buildMessage(TraceLocalization.java:30)
at org.eclipse.persistence.logging.AbstractSessionLog.formatMessage(AbstractSessionLog.java:801)
at org.eclipse.persistence.platform.server.ServerLog.log(ServerLog.java:71)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:2571)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3664)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3636)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3612)
at org.eclipse.persistence.internal.sessions.AbstractSession.log(AbstractSession.java:3534)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.logDebugMessage(UnitOfWorkImpl.java:5397)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerExistingObject(UnitOfWorkImpl.java:3874)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerExistingObject(UnitOfWorkImpl.java:3844)
at org.eclipse.persistence.queries.ObjectBuildingQuery.registerIndividualResult(ObjectBuildingQuery.java:362)
at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildWorkingCopyCloneNormally(ObjectBuilder.java:588)
at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObjectInUnitOfWork(ObjectBuilder.java:549)
at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:489)
at org.eclipse.persistence.internal.descriptors.ObjectBuilder.buildObject(ObjectBuilder.java:441)
at org.eclipse.persistence.queries.ObjectLevelReadQuery.buildObject(ObjectLevelReadQuery.java:635)
at org.eclipse.persistence.queries.ReadAllQuery.registerResultInUnitOfWork(ReadAllQuery.java:838)
at org.eclipse.persistence.queries.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:464)
at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:997)
at org.eclipse.persistence.queries.DatabaseQuery.execute(DatabaseQuery.java:670)
at org.eclipse.persistence.queries.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:958)
at org.eclipse.persistence.queries.ReadAllQuery.execute(ReadAllQuery.java:432)
at org.eclipse.persistence.queries.ObjectLevelReadQuery.executeInUnitOfWork(ObjectLevelReadQuery.java:1021)
at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2858)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1225)
at org.eclipse.persistence.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1207)
at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiate(QueryBasedValueHolder.java:85)
at org.eclipse.persistence.internal.indirection.QueryBasedValueHolder.instantiate(QueryBasedValueHolder.java:75)
at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:83)
at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiateImpl(UnitOfWorkValueHolder.java:161)
at org.eclipse.persistence.internal.indirection.UnitOfWorkValueHolder.instantiate(UnitOfWorkValueHolder.java:230)
at org.eclipse.persistence.internal.indirection.DatabaseValueHolder.getValue(DatabaseValueHolder.java:83)
at org.eclipse.persistence.indirection.IndirectList.buildDelegate(IndirectList.java:237)
at org.eclipse.persistence.indirection.IndirectList.getDelegate(IndirectList.java:397)
at org.eclipse.persistence.indirection.IndirectList$1.(IndirectList.java:525)
at org.eclipse.persistence.indirection.IndirectList.listIterator(IndirectList.java:524)
at org.eclipse.persistence.indirection.IndirectList.iterator(IndirectList.java:488)
at oracle.communications.platform.persistence.impl.PomsArrayList.iterator(PomsArrayList.java:598)
at oracle.communications.platform.entity.impl.DisResultGroupDAO.getRootEntities(DisResultGroupDAO.java:765)
at oracle.communications.integrity.scanCartridges.sdk.RootEntityLoaderImpl.(RootEntityLoaderImpl.java:37)
at oracle.communications.integrity.scanCartridges.sdk.BaseDiscrepancyDetectionController.init(BaseDiscrepancyDetectionController.java:71)
at oracle.communications.integrity.scanCartridges.sdk.BaseDiscrepancyDetectionController.invoke(BaseDiscrepancyDetectionController.java:41)
at oracle.communications.integrity.cartridges.ciscoextensioncartridge.detectionplugins.ciscodiscrepancydetectionsample.CiscoDiscrepancyDetectionSampleMessageDrivenBean.onMessage(CiscoDiscrepancyDetectionSampleMessageDrivenBean.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy343.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
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)

How to change log level in log4j at runtime

Hi,
I have a small requirement where the default log level is info, but if the user wants to invoke the Java program with debug level, the Debug should start off. I am trying to achieve this using this code..
          Logger root = Logger.getRootLogger();
          root.setLevel(Level.DEBUG);
          log.debug("This is debug");When I do this, the debug statement at the end does not print.
Then I thought may be the root logger level is not propagated after the initialization at start up, so I tried this
          log.setLevel(Level.DEBUG);
          log.info("This is info");
          log.debug("This is debug");
          log.info("Log level is " + log.getLevel());
          log.info(log.isDebugEnabled());The info statement prints "this is info" then the next info statement prints "log level is DEBUG" the next statement prints true but the intermediate debug statement does not print.
I have done this before in a Web app and it works just fine. I do not understand what is going on. Can someone please help me understand this.

I am not really familiar with Log4J, but in java.util.logging you define both a loglevel on the logger and the Handler that is actually responsible for outputting. A quick look on the Log4J sites shows that those are called 'appenders' in Log4J. So you might want to look if your appender is actually configured to output DEBUG-level statements.

How to set more detail log level for http

Hi,
With Java Enterprise System 2003 I want to see when a user login to the Messenger Express in the http log. How could I set a log level so I can see this?
I do not know the the default log level for http and I would like to set a log level that show me more information
could this be the command?
configutil -o logfile.http.loglevel -v level Information

configutil -o logfile.http.loglevel -v Information
would be the correct command to set the log level to "information".
Other valid levels include, "debug", "notice" (this is the default), "warning".
You have t restart the webmail daemon to make this take effect.
stop-msg http; start-msg http

Logging Level

hi,
I have been following the below perf tuning url:
http://www.oraclebidwh.com/2010/02/performance-tuning-in-obiee/
I have been reviewing section3, regarding turing off logging, it states the following:
+3) Turning off Logging+
Logging can affect in performance of Oracle BI Server and can create large log files. Logging can be used in problem solving and trouble shooting problematic queries. So when it is necessary then only set logging level to 0 to 2. Set log level greater than 2 is not recommended by Oracle.
investigating via the admin tool, using security manager
Manage > Security > Security manager
We have some OBIEE users that have logging levels set at 2, some set at 3, some set at 4, and some set at 5.
As an example, PUBLIC user is set at 4, Administrator is set at 5.
Also, in the 10.1.3.4 docs http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf , on page 216 it states:
NOTE: Logging levels greater than 2 should be used only with the assistance of Technical Support.
So with having logging levels of 3, 4 , & even 5 will it cause performance issues?
I'd be very grateful of the advice.
& thanks in advance

>
So with having logging levels of 3, 4 , & even 5 will it cause performance issues?
I'd be very grateful of the advice.
& thanks in advanceYes, the BI-server will have to a lot of write actions to the server disk. This means it will have to 'wait' several times during the execution until the logbuffer is written to disk
regards
John
http://obiee101.blogspot.com/
http://obiee11g.com/

The problem about the Log Level

Hi everyone,
The Log Level of Oracle Application Server includes NULL,Severe,Warning,Info,Config,fine,finer,finest.
Which log level is the highest ?
I want to get more message about My Esb instances,How to set the log level ?

finest is the highest level logging and can either be turned on for all logs or just specific logs within the Enterprise manager.

Is it possible to set a log level for ID and/or IDS when opening an IDML?

We're finding that it's taking an excessive amount of time (30-45 minutes) to open somewhat larger files (~100 pages) with many hyperlinks (~10,000). Is anyone aware of a way to add a command line parameter to either Indesign.exe or IndesignServer.exe (as we use both) to set, for example, a more detailed log level to allow for seeing what is taking so long to process when opening a file? The output would presumably go to the Event Viewer or stdout / stderr in a Command Prompt.

On a Mac you either use the Activity Monitor or the Instruments application (part of the Xcode IDE) for various performance analysis down to the system calls (dtrace) and their invocation stack frames. I assume Windows provides similar tools, or you might just reproduce your problem on a spare Mac with a trial or developer license.
Let me see - yup, the technology exists on Windows - Trace Provider
Btw, InDesign (Server and Desktop) has separate "debug" builds for plugin developers with plenty internal consistency checks "assert" and debug output. For speed reasons these are stripped out from release builds, it might be worth a try if you have access to those builds. Of course they will take even longer... The above mentioned analysis via the OS may also benefit from more symbols on such development versions.
InDesign Server (even release build) also has some performance metrics available via scripting (somewhere on the app object), have you tried these?
On the other hand it could also be something unrelated - do you have any extra software (plugin, startup scripts, scripted event handlers) that could interfere? E.g. a link event handler that waits for a timeout on every $.write without connected ESTK? On one client's InDesign server farm I reduced restart times down from minutes to barely noticable just by optimizations of the startup process, before I tracked down and eliminated the bugs (in the SOAP interface and in XPath) that caused all those crashes ;-) . Of course such problems are beyond the scope of a forum, they take several days to analyze and solve, especially if they require changes of the binaries from Adobe.
Dirk

Change default log level when calling a scenario

Hi,
we are looking to an easy way to change log level default value instead of having to transfer a variable to each sub-scenario.
By default log level is set to 5, which is too much. Is this value stored in a repository ? Can we easily change it ?
Thanks in advance
Pierre-Henri

Just submitted it. Thanks!

Audit log level

Hello there,
When i update an attribute to be multi-value in the schema section of DSCC, i want to see update in audit log. Now with default audit log level, i can see only the following but it does not show what attribute and what value is being modified. Is there audit log level i should set to ?
dn: cn=schema
changetype: modify
replace: modifiersname
modifiersname: cn=admin,cn=administrators,cn=dscc

Hi,
You hit defect 6997464 due to the fact in-memory schema entry is managed differently from the other entries.
Please contact your local Oracle support representative to get a relief if needed.
Regards
Sylvain

Deprecated log level constants

Similar Messages

Maybe you are looking for