ILearnng - Setting log level

Hi All,
We are trying to read the log files for iLearning. However, after setting the
CURRENT_LOG_LEVEL=5 (Debug) and restarting the IAS server, we are still unable to see any changes in the log files.
We are currently viewing these log files:
<iAS home>/opmn/logs/OC4J~oil~default_island~1
<iAS home>/j2ee/oil/application-deployments/ilearning/oil_default_island_1/application.log
<iAS home>/j2ee/oil/oil_default_island_1/global-application.log
<iAS home>/j2ee/oil/oil_default_island_1/server.log
None of these show any debug level info. Are there any other log files we need to look at?
Thanks

Contact Oracle Support. They will be able to help you.
Regards Anders

Similar Messages

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

Can you set log level

Does weblogic supply any way of setting the level of log messages that
actually get written out to the log. So that if can turn off all my debug
messages (e.g. LogServicesDef log, log.info(), log.debug())
in production. I'm currently doing this with application level code

Hi,
Yes, weblogic does supply a way of setting the level of log messages that actually
get written out to the log.
This can be changed at Admin Console> idbmsDem
o> Servers> myserver> Logging> General> Stdout severity threshold>
Yuan Dai
BEA Adapter Factory Group
InfoGain
408-355-6098
"maurice lowenthal" <[email protected]> wrote:>Does weblogic supply any way
of setting the level of log messages that
actually get written out to the log. So that if can turn off all my debug
messages (e.g. LogServicesDef log, log.info(), log.debug())
in production. I'm currently doing this with application level code

Set Logging level for my application

I've got an web-based application (ADF/EJB) and I'm trying to configure the logging level.
I'm using the Java Logging API and no matter what I change, short of hardcoding a call in to set the global logging level, I can't alter what level it is using. I've tried changing in the WebLogic console and all that does is change the logging level for WebLogic. I've tried adding properties files but they don't seem to be read.
Any Ideas?

Hey Mark,
I have no idea if this will help, but I was wanting to print out only my DML operations on commit and I got this post on my thread.
You could probably do this with -Djbo.debugoutput=adflogger and then fuss with the logging configuration, or perhaps by turning on JDBC loggingDouble-click your View Controller project-> Run/Debug/Profile -> Edit ,and then type the -Djbo.debugoutput=adflogger into your Java Options, but I don't know anything after that.
Good luck.
Will

JDev 10.1.3.3.0: Trouble setting logging level

I have an application that I did not write that has a large amount of "info" level logging using "java.util.logging.Logger".
These logging statements look like this in the code:
log.info("My message");
There are only a few points in the application where I want to log statements for now, so I thought a quick way to suppress all the unwanted logging would be to change the severity of the items I want to see in the log as follows:
log.severe("My message");
Then, I went into the file [JDeveloper Root]\jdev\system\oracle.j2ee.10.1.3.41.57\embedded-oc4j\config\j2ee-logging.xml.
I changed all the level="XYX" statements to level="SEVERE", and restarted the application in JDeveloper.
I did not see my "log.severe" statements in the log.
Then I changed all the level="XYX" statements to level="ERROR:1", and restarted the application in JDeveloper.
I still did not see my "log.severe" statements in the log.
Any ideas on what I'm doing wrong?
Thanks,
Jonathan

Sorry...Operator error.
There was a conditional block around the logging statement that I didn't notice.
The logging is now working as expected.

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)

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/

User log level manage in BIEE11.1.1.5

Hi,
I faced a problem in BIEE11.1.1.5, I have created a user in console,
but I didn't find the user in identity in Administrate manage,
so I can't set log level.
I'd like to ask why the user not exists in identity .
anyone know?
thank you!

Hi,
Its because of your new users are not yet synchronized (globally not yet refreshed). you have do it GUID else you need set "set online filter" via RPD -->identity --> then you can find that users.
steps:
Open Rpd online mode and click on Manage –> Identity-->go to Actions –> Set Online User Filter and enter * in the input box and click Ok and then it will show the newly created user
For more setting online filters and GUID Ref:
http://prasadmadhasi.com/2011/12/01/unable-to-view-log-file-in-obiee-11-1-1-5-0/
http://obiee11gqna.blogspot.sg/2011/10/obiee11g-updating-guids.html
Thanks
Deva

Enable logging level

hi all,
in our company, we are maintaing users for OBIEE in the external table and admin tool.
i am able set logging level for the users in the admin tool. but could not set logging level for users maintained in the external table.
please let me now how to enable loggin level for users maintained in the external table.
thanks

You can set it in your authorisation init_block by setting the LOGLEVEL variable.
regards
John
http://obiee101.blogspot.com/

Turn off log level for Individual Users

Hi,
we want to turn off logging level of individual users. We usually go to Identity and click on the user to set log level '0' but we have LDAP security setup so don't have idea how to do it.
Any Ideas
Thxs
SYK

Ok I will try to Set System Variable LOGLEVEL
As we are using LDAP security we will not have users in RPD so i cant set to'0' in rpd.
New Question: Suppose If I am able to set log level to '0' for a user i.e User1 and when he logs into OBIEE and get's a error while running report like say table or view doesn't exist or non of fact table is compatible or number records exceed etc... and Error will show to user as Error Number and says "Please contact System Administrator for more details".
Me considering as Admin if i want to debug that error that User1 is getting from above scenario and when i open nqquery log file will I be able to see the log for that report which User1 is getting error or will it show NO LOGLEVEL Found.
Thxs
SYK

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.

Java.util.logging - Problem with setting different Levels for each Handler

Hello all,
I am having issues setting up the java.util.logging system to use multiple handlers.
I will paste the relevant code below, but basically I have 3 Handlers. One is a custom handler that opens a JOptionPane dialog with the specified error, the others are ConsoleHandler and FileHandler. I want Console and File to display ALL levels, and I want the custom handler to only display SEVERE levels.
As it is now, all log levels are being displayed in the JOptionPane, and the Console is displaying duplicates.
Here is the code that sets up the logger:
logger = Logger.getLogger("lib.srr.applet");
// I have tried both with and without the following statement
logger.setLevel(Level.ALL);
// Log to file for all levels FINER and up
FileHandler fh = new FileHandler("mylog.log");
fh.setFormatter(new SimpleFormatter());
fh.setLevel(Level.FINER);
// Log to console for all levels FINER and up
ConsoleHandler ch = new ConsoleHandler();
ch.setLevel(Level.FINER);
// Log SEVERE levels to the User, through a JOptionPane message dialog
SRRUserAlertHandler uah = new SRRUserAlertHandler();
uah.setLevel(Level.SEVERE);
uah.setFormatter(new SRRUserAlertFormatter());
// Add handlers
logger.addHandler(fh);
logger.addHandler(ch);
logger.addHandler(uah);
logger.info(fh.getLevel().toString() + " -- " + ch.getLevel().toString() + " -- " + uah.getLevel().toString());
logger.info("Logger Initialized.");Both of those logger.info() calls displays to the SRRUserAlertHandler, despite the level being set to SEVERE.
The getLevel calls displays the proper levels: "FINER -- FINER -- SEVERE"
When I start up the applet, I get the following in the console:
Apr 28, 2009 12:01:34 PM lib.srr.applet.SRR initLogger
INFO: FINER -- FINER -- SEVERE
Apr 28, 2009 12:01:34 PM lib.srr.applet.SRR initLogger
INFO: FINER -- FINER -- SEVERE
Apr 28, 2009 12:01:40 PM lib.srr.applet.SRR initLogger
INFO: Logger Initialized.
Apr 28, 2009 12:01:40 PM lib.srr.applet.SRR initLogger
INFO: Logger Initialized.
Apr 28, 2009 12:01:41 PM lib.srr.applet.SRR init
INFO: Preparing Helper Files.
Apr 28, 2009 12:01:41 PM lib.srr.applet.SRR init
INFO: Preparing Helper Files.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Getting PC Name.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Getting PC Name.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Finished Initialization.
Apr 28, 2009 12:01:42 PM lib.srr.applet.SRR init
INFO: Finished Initialization.Notice they all display twice. Each of those are also being displayed to the user through the JOptionPane dialogs.
Any ideas how I can properly set this up to send ONLY SEVERE to the user, and FINER and up to the File/Console?
Thanks!
Edit:
Just in case, here is the code for my SRRUserAlertHandler:
public class SRRUserAlertHandler extends Handler {
     public void close() throws SecurityException {
     public void flush() {
     public void publish(LogRecord arg0) {
          JOptionPane.showMessageDialog(null, arg0.getMessage());
}Edited by: compbry15 on Apr 28, 2009 9:44 AM

For now I have fixed the issue of setLevel not working by making a Filter class:
public class SRRUserAlertFilter implements Filter {
     public boolean isLoggable(LogRecord arg0) {
          if (arg0.getLevel().intValue() >= Level.WARNING.intValue()) {
               System.err.println(arg0.getLevel().intValue() + " -- " + Level.WARNING.intValue());
               return true;
          return false;
}My new SRRUserAlertHandler goes like this now:
public class SRRUserAlertHandler extends Handler {
     public void close() throws SecurityException {
     public void flush() {
     public void publish(LogRecord arg0) {
          Filter theFilter = this.getFilter();
          if (theFilter.isLoggable(arg0))
               JOptionPane.showMessageDialog(null, arg0.getMessage());
}This is ugly as sin .. but I cannot be required to change an external config file when this is going in an applet.
After much searching around, this logging api is quite annoying at times. I have seen numerous other people run into problems with it not logging specific levels, or logging too many levels, etc. A developer should be able to complete configure the system without having to modify external config files.
Does anyone else have another solution?

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

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

ILearnng - Setting log level

Similar Messages

Maybe you are looking for