Scenario execution with log level Zero

I am executing the scenarios with log level zero, but it purges the operator logs on successful execution. With log level Zero, is it possible to stop the automatic purge of the operator logs on successful execution?

I just get "SnpSession does not exist" error on this, this error is generated if we don't have an entry for that scenario in SNP_Session table. However, ODI if is provided with log level 0 deletes corresponding entries from SNP_Session table on successful completion of a scenario. Which is also happening in my case and entries are being deleted from table for Scen B and Scen C, but since Scen fails it remains in the table. Again, Once I have gotten the log_level in a variable in Scen A i am just making use of that variable in the subsequent scenarios. Also, when executed with log level 1, 2, 3, 4, 5 it works jolly good.

Similar Messages

  • Log Levels

    Hi,
    In my application I use a lot of info/debug printouts with the method log which writes to the appservers (sun appserver 8) log file (server.log). Log method called with a string (log("message")) seems to give Log Level INFO in server.log. Now I want to get rid of the info messages without actually removing them from the source code. Easy, I thought, just to change Log Level from INFO to WARNING for module Web Container in the appserver (with admin console) because the help page says "The default level is INFO, meaning that messages at that level or higher (WARNING, SEVERE) will appear in the log". The result was not what I expected, the log posts did not disappear, instead the log level changed from INFO to WARNING!!!
    In my next try, I used System.out.println for my info messages instead of method log. This also writes log posts, with log level INFO, to server.log with logger name javax.enterprise.system.stream.out. To turn off the logs the help page says "specify the logger name with the value OFF in the Additional Properties area". That is exactly what I did (yes, I also restarted the appserver) but the log posts are still written to server.log.
    No more ideas.
    Am I misunderstanding something, bugs in appserver or what?
    Regards
    Mats

    Maybe you need to implement Java Logging in your application. Check out the below URL for more details :
    http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/
    Once you have implemented Java logging, you need to edit either <jdk_home>/jre/lib/logging.properties and include something like this :
    com.util.level = INFO
    com.servlet.level = SEVERE
    (Assuming com.util and com.servlet and two packages in your application, all Java classes in com.util will log only INFO and above messages and all Java classes in com.servlet will log only SEVERE messages).
    Alternatively, you can also add the above properties in the Logger Settings tab from the admin GUI.
    Hope that helps
    Cheers,
    Vasanth

  • AD "Log on to" restriction causes RDP connections with network level authentication to fail

    I am running a Server 2008 R2 environment and have recently enabled network level authentication for RDP connections. Since the change, users who have their logons restricted to specific servers via AD, now get an error when logging on via RDP:
    An Authentication error has occured
    The Local security authority cannot be contacted
    After investigating this error and reading technet I found that removing the "log on to" restriction within their user object solved the problem even tho they had rights to this server. Adding the users client PC name to the "Log on
    to" list also solves this issue.
    My question is, is there another way around this? We have an environment where some users may require an RDP connection from a client PC not on the same domain (over VPN) as the server. It will not be practical to add many different client PC names
    to the log on to list and I don't understand why client PC's must be specified in the Log on to list and not just the actual server they are logging onto.
    Any pointers appreciated

    I have just come across this problem on one of my client’s domains; they have recently enforced a policy to “Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)”  and users with “Log on To” restrictions
    on their account are no longer able to RDP using their second account.
    After a lot of fiddling around I finally resolved the problem by adding the connecting computer name into “Log on To” list.  Ultimately it appears that Network Level Authentication (NLA) requires authentication to take place on both the host initiating
    the connection and the remote host.

  • 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!

  • Has anyone lost the info from games with the new iOS7? My games reset to level zero! Argh!

    Has anyone lost the info from games with the new iOS7? My games reset to level zero! Argh!

    Restore from your iTune Backup.

  • [svn] 977: Bug: BLZ-93 - When a producer sends a message to a secure destination with no credentials it causes a security exception to get logged with a log level of error .

    Revision: 977
    Author: [email protected]
    Date: 2008-03-27 17:04:59 -0700 (Thu, 27 Mar 2008)
    Log Message:
    Bug: BLZ-93 - When a producer sends a message to a secure destination with no credentials it causes a security exception to get logged with a log level of error.
    QA: Yes
    Doc: No
    Details:
    Updates to catch-all exception logging hinge points on the server to use a new method on MessageException that protects against repeat logging of the same exception as we unwind the call stack on the server, as well as allowing exception subclasses to control the log level, intro text and inclusion of a full stack trace in the logged output. This allows things like SecurityExceptions, which represent common errors like incorrect user credentials, to avoid polluting the log with error-level logging and stack traces. It also consolidates our catch-all handling for MessageExceptions and their subclasses in a single point, avoiding problems with needing to make updates or tweaks to our logging output in multiple places.
    Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-93
    Modified Paths:
    blazeds/branches/3.0.x/modules/common/src/java/flex/messaging/log/Log.java
    blazeds/branches/3.0.x/modules/common/src/java/flex/messaging/util/ExceptionUtil.java
    blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageBroker.java
    blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageException.java
    blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/amf/MessageBrokerFi lter.java
    blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/amf/SuspendableMess ageBrokerFilter.java
    blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/security/SecurityException.ja va
    blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/ServiceException.jav a

    One thing I forgot to add, which may be causing you
    problems: the "mount volume" command is not part of
    the Finder dictionary. It stands alone.
    bill
      Mac OS X
    (10.4.10)   1 GHz Powerbook G4
    I tried the mount command. After executing it in Script Editor, I was prompted with login and password, but it was my Keychain!
    I don't know if you have your keychain unlocked or what else..
    Maybe the original poster (Rick Anderson) has his keychain locked and the prompt is from it.
    Just a guess...
    Ciao,
    Ermanno
    Dual 2 GHz PowerPC G5   Mac OS X (10.4.9)   4.5 GBy SDRAM, 5 external FW disks, 2 Internal SATA disks

  • 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.

  • 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 control listener log levels with log.xml

    I'm running Oracle 11 and I am seeing tons of log.xml files being created, rotated, and renamed. Looking at the log.xml files, I'm seeing what appears to be rather excessive logging. It appears to be logging every single connection. Is there any way to control the logging levels for this file and/or decrease the number of log files kept in the rotation?

    I don't believe it is possible to disable part of the ADR activity. But I would be interested in your definition of "excessive logging."
    Are you seeing a specific performance impact or are you just seeing something different from 10gR2 (meaning the new ADR functionality)?

  • 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.

  • 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 Java VM terminated with a non-zero exit code.

    Hi,expert,
    I have got this error when I am trying to restart the sap Instance use
    command STARTSAP,
    The error log as below:
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 940893 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    trc file: "/usr/sap/J2E/JC00/work/dev_jcontrol", trc level: 1,
    release: "640"
    ERROR => can't retrieve client list (rc=24) [jcntrms_mt.c960]
    May 21, 2010 12:53:14... com.sap.engine.core.Framework [SAP
    J2EE Engi
    ne|MS Socket Listener] Fatal: Critical shutdown was invoked. Reason is:
    Exiting
    Listener Loop. This requires a restart of the node. Possible reason is
    an interr
    upted reconnect session to the message server.
    Thanks and Best regards,
    Michael

    Hi Michael,
    I am also facing the same issue, can you please let me know where to find the ms.hostname and enqu.hostname...It's very urgent.
    Thanks in advance..
    Regards,
    Krishna.M

  • Java VM terminated with a non-zero exit code (-337)

    We are running a J2EE application on NW7.0 and  IBM i5 V5R4.
    The application server restarts itself after the server0 proces terminates with the following messages in the dev_server0.log
    [Thr 2057] Sat Jun 20 09:34:12 2009
    [Thr 2057] JLaunchIExitJava: exit hook is called (rc = -337)
    [Thr 2057]
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 2057] SigISetIgnoreAction : SIG_IGN for signal 20
    [Thr 2057] JLaunchCloseProgram: good bye (exitcode = -337)
    The mentioned Sapnote 943602 refers to Note 940893, which suggest to send the logfiles to Support (which we did).
    But can anyone shed a light on this? What can we learn from the mentioned exit codes?
    Thanks
    Anita

    Hi Sunny,
    Here's the last part of the dev_server0 log:
    Sat Jun 20 09:17:38 2009
    GC 12352: live objects 6177736; collected objects 7188118; collected(KB) 775717.
    GC 12352: queued for finalization 0; total soft references 8982; cleared soft references 0.
    GC 12352: current heap(KB) 2416964; current threshold(KB) 786432.
    GC 12352: collect (milliseconds) 3423.
    GC 12352: current cycle allocation(KB) 317872; previous cycle allocation(KB) 786457.
    GC 12352: total weak references 15151; cleared weak references 0.
    GC 12352: total final references 11901; cleared final references 7466.
    GC 12352: total phantom references 0; cleared phantom references 0.
    GC 12352: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 12352: collection ending 20/06/09 09:17:38
    Sat Jun 20 09:17:41 2009
    GC 12353: starting collection, threshold allocation reached.
    GC 12353: collection starting 20/06/09 09:17:41
    Sat Jun 20 09:17:44 2009
    GC 12353: live objects 6220831; collected objects 7043383; collected(KB) 785764.
    GC 12353: queued for finalization 0; total soft references 8974; cleared soft references 0.
    GC 12353: current heap(KB) 2415944; current threshold(KB) 786432.
    GC 12353: collect (milliseconds) 3003.
    GC 12353: current cycle allocation(KB) 294375; previous cycle allocation(KB) 786464.
    GC 12353: total weak references 15151; cleared weak references 0.
    GC 12353: total final references 10853; cleared final references 6411.
    GC 12353: total phantom references 0; cleared phantom references 0.
    GC 12353: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 12353: collection ending 20/06/09 09:17:44
    Sat Jun 20 09:17:47 2009
    GC 12354: starting collection, threshold allocation reached.
    GC 12354: collection starting 20/06/09 09:17:47
    Sat Jun 20 09:17:54 2009
    GC 12355: starting collection, threshold allocation reached.
    Sat Jun 20 09:18:23 2009
    GC 12355: starting collection, threshold allocation reached.
    Sat Jun 20 09:20:10 2009
    GC 12355: starting collection, threshold allocation reached.
    Sat Jun 20 09:20:23 2009
    GC 12355: starting collection, threshold allocation reached.
    Sat Jun 20 09:20:30 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:31 2009
    GC 12355: starting collection, maximum allocation reached.
    GC 12355: starting collection, maximum allocation reached.
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:32 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:34 2009
    GC 12355: starting collection, maximum allocation reached.
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:35 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:36 2009
    GC 12355: starting collection, maximum allocation reached.
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:38 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:39 2009
    GC 12355: starting collection, maximum allocation reached.
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:45 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:46 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:50 2009
    GC 12355: starting collection, maximum allocation reached.
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:20:58 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:21:00 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:21:21 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:21:50 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:22:40 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:22:42 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:22:50 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:24:46 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:24:47 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:24:50 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:25:06 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:25:51 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:27:04 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:28:28 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:28:42 2009
    GC 12355: starting collection, maximum allocation reached.
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:29:19 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:30:46 2009
    GC 12355: starting collection, maximum allocation reached.
    Sat Jun 20 09:31:08 2009
    GC 12354: live objects 6994240; collected objects 6961336; collected(KB) 789682.
    GC 12354: queued for finalization 0; total soft references 8976; cleared soft references 3.
    GC 12354: current heap(KB) 4194292; current threshold(KB) 786432.
    GC 12354: collect (milliseconds) 801210.
    GC 12354: current cycle allocation(KB) 0; previous cycle allocation(KB) 4242195.
    GC 12354: total weak references 15151; cleared weak references 0.
    GC 12354: total final references 10905; cleared final references 6451.
    GC 12354: total phantom references 0; cleared phantom references 0.
    GC 12354: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 12354: collection ending 20/06/09 09:31:08
    GC 12355: collection starting 20/06/09 09:31:08
    Sat Jun 20 09:31:18 2009
    GC 12356: starting collection, maximum allocation reached.
    Sat Jun 20 09:32:38 2009
    GC 12356: starting collection, maximum allocation reached.
    Sat Jun 20 09:33:48 2009
    GC 12355: collected class sun/reflect/GeneratedMethodAccessor3620979168.
    Sat Jun 20 09:33:59 2009
    GC 12355: live objects 6717156; collected objects 29066552; collected(KB) 3256489.
    GC 12355: queued for finalization 0; total soft references 8973; cleared soft references 89.
    GC 12355: current heap(KB) 4193652; current threshold(KB) 786432.
    GC 12355: collect (milliseconds) 170434.
    GC 12355: current cycle allocation(KB) 75; previous cycle allocation(KB) 0.
    GC 12355: total weak references 15164; cleared weak references 0.
    GC 12355: total final references 32619; cleared final references 28210.
    GC 12355: total phantom references 0; cleared phantom references 0.
    GC 12355: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 12355: collection ending 20/06/09 09:33:59
    GC 12356: collection starting 20/06/09 09:33:59
    Sat Jun 20 09:34:01 2009
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor746382538.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor3780712466.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor168496322.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor980237086.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1886738503.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1251676621.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1433437257.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1328663959.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor3914321935.
    GC 12356: collected class sun/reflect/GeneratedConstructorAccessor333360639.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor3292847473.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor752085389.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor416310187.
    GC 12356: collected class sun/reflect/GeneratedMethodAccessor3620979168.
    GC 12356: collected class sun/reflect/GeneratedMethodAccessor2138604126.
    GC 12356: collected class sun/reflect/GeneratedConstructorAccessor2058455930.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor599442064.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor853421746.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1143931263.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor379179616.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor1925696964.
    GC 12356: collected class sun/reflect/GeneratedSerializationConstructorAccessor57815531.
    GC 12356: collected class sun/reflect/GeneratedMethodAccessor843740711.
    GC 12356: collected class sun/reflect/GeneratedMethodAccessor2093346596.
    GC 12356: collected class sun/reflect/GeneratedConstructorAccessor1446511408.
    GC 12356: collected class sun/reflect/GeneratedConstructorAccessor1446703216.
    GC 12356: collected class sun/reflect/GeneratedConstructorAccessor1522492322.
    Sat Jun 20 09:34:02 2009
    GC 12356: collected class sun/reflect/GeneratedMethodAccessor1786850049.
    GC 12356: collected class sun/reflect/GeneratedMethodAccessor515968301.
    GC 12356: collected class sun/reflect/GeneratedMethodAccessor1786794657.
    GC 12356: collected class sun/reflect/GeneratedMethodAccessor516161133.
    GC 12356: collected class sun/reflect/GeneratedConstructorAccessor2753180717.
    GC 12356: live objects 4366863; collected objects 2655706; collected(KB) 255573.
    GC 12356: queued for finalization 0; total soft references 8976; cleared soft references 0.
    GC 12356: current heap(KB) 3147644; current threshold(KB) 786432.
    GC 12356: collect (milliseconds) 3478.
    GC 12356: current cycle allocation(KB) 25809; previous cycle allocation(KB) 0.
    GC 12356: total weak references 15164; cleared weak references 0.
    GC 12356: total final references 4422; cleared final references 11.
    GC 12356: total phantom references 0; cleared phantom references 0.
    GC 12356: total JNI global weak references 0; cleared JNI global weak references 0.
    GC 12356: collection ending 20/06/09 09:34:02
    [Thr 2057] Sat Jun 20 09:34:12 2009
    [Thr 2057] JLaunchIExitJava: exit hook is called (rc = -337)
    [Thr 2057] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 2057] SigISetIgnoreAction : SIG_IGN for signal 20
    [Thr 2057] JLaunchCloseProgram: good bye (exitcode = -337)
    trc file: "/usr/sap/P01/DVEBMGS01/work/dev_server0", trc level: 1, release: "700"

  • Problem in Aggregate with Multiple level of dimension

    Hi,
    I have a BI repository with a snowflake schema. I have also designed the business model with snowflake, It works with drilling and all but I am facing problem when I am
    creating  a logical column aggregating with a higher level of dimentation. Let me illustrate that :
      I have the Following Hierarchy :
    Tournament(id, Name) ---- > Round (id, name, tournament_id) -------> Match (id, Name, RoundId ) |  Match is fact table and other 2 dimension.
      I also created a logical dimension called tournament with 3 levels.
      Now say I want to create a logical column Total Number of Matches , aggregating  to the dimension level of Tournament. The result gives counts a 0 for every tournament. However
      it is working perfectly when the dimension level is Round (which is the immediate next level after fact).
      The Logical request generated (in case of Tournament level) :
       MatchId:[DAggr(Measure1.MATCHID by [ Matches$.TournamentId]  SB Tournament)] as c1 GB.   
        There is no such column as TournamentId in Matches$ table. How does the BI server got this ?
       The execution plan  evaluate this:
         cast(NULL as  INTEGER )  as c1 GB [for database 0:0,1]
       Can someone please explain why is this happening, is it because of the snowflake schema, but I guess if BI server can handle a snowflake schema it should work the Aggregate
       properly in multiple levels of dimensions, or it is something I am doing wrong.
       Execution Environment:
         Windows XP ,  OBI 10g on OC4J.  Data source : MS Excel (ODBC 3.5)
      Regards,
      Ru

    Hi,
    With reference to your question.
    Can any operator perform this task..I don't think any single operator will help you.
    I suggest using an intermediate (staging) table by using a PL SQL procedure with output port to store the values of account number provided the number of accounts are limited. Else use an array variable for account of an employee.
    In short no simple solution because of the bad source design else the pivot/unpivot operator would have helped you.
    Cheers
    - Mohammed

  • SOAP Adapter with Security Levels - HTTP & HTTPS

    We have a successfully working interface scenario where SAP XI is hosting a web service and the partner systems calling it using SOAP Adapter URL http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel with Security Level HTTP on the SOAP Sender Communication channel.
    Going forward, for other similar interfaces (SAP XI hosting Web Service and partner systems calling it), we would like to use HTTPS and/or certificates.
    If we enable HTTPS on XI J2EE server as per the guide How to configure the [SAP J2EE Engine for using SSL - Notes - PDF|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/964f67ec-0701-0010-bd88-f995abf4e1fc]....
    can partner systems still use the URL http://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel or should they switch to https://host:port/XISOAPAdapter/MessageServlet?channel=:service:channel?
    can we continue to have the existing interface working using HTTP Security Level i.e. partners not having to send the certificate with each message?
    If we use HTTPS security level, is it mandatory for the partner system need to send the certificate? Is it possible to have an HTTPS scenario w/o certificates?
    What is the difference between Security Levels  'HTTPS Without Client Authentication' & 'HTTPS with Client Authentication'?
    I appreciate your inputs on this.
    thx in adv
    praveen
    PS: We are currently on SAP PI 7.0 SP17

    Hi Praveen,
    There is no need to change the interface and It is manditory for the partners to send certificates in order to validate each other. Use the https in url.
    HTTPS With Client authentication:
    The HTTPS client identifies itself with a certificate that is to be verified by the server. To validate the HTTPS clientu2019s certificate, the HTTPS server must have a corresponding CA certificate that validates this certificate. After validation of the clientu2019s certificate, the server maps the certificate to an actual system user executing the HTTP request.
    and check this link.
    http://help.sap.com/saphelp_nw04/helpdata/en/14/ef2940cbf2195de10000000a1550b0/frameset.htm
    Regards,
    Prasanna

Maybe you are looking for

  • How to pass variable in a function

    I would like to ask how to pass the value "char" into the "onSoundComplete" function? many thanks! many thanks! _root.playVO = function(pageNum, char){ var myVO:Sound = new Sound(); myVO.loadSound("vo/vo" + pageNum + ".mp3", true); _root.myVO.onSound

  • Can Contact Sheet II work in Photoshop CS5?

    I was able to download the Contact sheet II for Photos hop CS4 64 bit. Can it work in CS5? I can't find a dow nload for it.

  • Help!! Illustrator won't open

    Hi Wondering if someone could please help me, I have just downloaded and installed Illustrater CS5 Trail Version I then go to open it and click 'start trail' then asks for my Adobe ID - so i enter that and click next It then comes up and says 'could

  • Sync mac to iphone

    help; old macbook pro but with Mountain Lion and iphone latest updates and itunes.  i just want my music library on my phone.  how please???

  • Question about moving system board from domain C to domain B  SF2000

    Hello, i would like to move the system board e this is my configuration: Domain A with Domain B Solaris 10 Sun cluster 3.2 Domain C Solaris 10 no Sun Cluster. I move the sytem board SB7 from domain C to domain B with the command from System Controlle