SSISDB Verbose Logging Level and Unexpected Terminiation

If we set the SSISDB Logging Level to Verbose, will we get more details on Unexpected Termination events?
With basic logging level, the reports for Unexpected Termination do not provide any useful information to what happened.
--- Ryan
Ryan P. Casey • <a href="http://www.R-P-C-Group.com">www.R-P-C-Group.com</a>

Hi Ryan,
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Similar Messages

SNARE Logging Levels and CS-MARS

If you install SNARE on a Windows 2003 Server to push events to CS-MARS, what is the default logging level of SNARE. Somone told me that the default level of SNARE is lower then the log level that we currently have set on our Windows 2003 Server. I was under the impression that SNARE converts the string format of the event log record to text format and simply pushed the events to CS-MARS regardless of logging levels on Windows. What would happen if you did no select Allow SNARE to automatically set audit configuration and Allow SNARE to automatically set file audit configuration?. would CS-MARS still get events from windows devices?

Snare converts the binary Windows event log messages into syslog messages. I don't think the logging level (I assume you are referring to the syslog priority) is relevant to MARS. MARS sets the severity based on how it maps the event, and it doesn't consider the syslog priority AFAICT. So, you can set it to whatever you want. By default, it appears to be NOTICE.
The "Allow SNARE to automatically set file audit configuration" has nothing to do with this really. The Windows audit policy settings determine what events get logged, even to the local security event log. If an event isn't in the windows event log, it can't be sent by Snare. The audit policy settings in a domain (i.e. on a member server) are almost always done via Group Policy and Snare shouldn't be required to automatically set the configuration. That's more for standalone Windows servers.
See this link for a discussion on Windows audit policy (it's for 2000, but still relevant):
http://www.microsoft.com/technet/security/prodtech/windows2000/w2kccadm/localpol/w2kadm11.mspx

Java Runtime parameters- setting trace/log levels and enabling by default

Hi,
I have a user reporting that a Java app that I support is unexpectedly quitting, and our developers are having trouble tracking down exactly what's causing the problem.
I'm trying to enable the maximum possible logging/tracing for this user, but I don't want to have to rely on them remembering to hit '5' on the console window to enable tracing on everything. Having read through the runtime documentation, I have added the following to my JRE runtime parameters:
-Xdebug -Djavaplugin.trace=true -Djavaplugin.trace.option=basic|net|security|ext|liveconnect -Djavaplugin.outputfiles.overwrite=falseHowever, I still get nothing in the log file until I manually hit '5' on the Java console, then everything I do after that gets added to the log.
Does anyone know how can I get the maximum logging/tracing enabled by default as soon as the JRE is loaded?

>>
-Xdebug -Djavaplugin.trace=true-Djavaplugin.trace.option=basic|net|security|ext|livec
onnect
-Djavaplugin.outputfiles.overwrite=false
One problem is that -Djavaplugin.trace.option=basic
OR net etc ... pick one of the options which are
separated with pipe symbols or use "all" without
quotes.
I'm having a similar problem with Java 6 - it seem
that nothing I put in the runtime parameters takes
effect. I had to edit
/home/USERNAME/.java/deployment/deployment.properties
and add deployment.trace=true.On second thought, I could be wrong about the trace options. I really don't know if you can combine options but I did see "all" somewhere.

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

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

Schema level and table level supplemental logging

Hello,
I'm setting up bi- directional DML replication between two oracle databases. I have enabled supplemental logging database level by running this command-
SQL>alter database add supplemental log data (primary key) columns;
Database altered.
SQL> select SUPPLEMENTAL_LOG_DATA_MIN, SUPPLEMENTAL_LOG_DATA_PK, SUPPLEMENTAL_LOG_DATA_UI from v$database;
SUPPLEME SUP SUP
IMPLICIT YES NO
-My question is should I enable supplemental logging table level also(for DML replication only)? should I run the below command also?
GGSCI (db1) 1> DBLOGIN USERID ggs_admin, PASSWORD ggs_admin
Successfully logged into database.
GGSCI (db1) 2> ADD TRANDATA schema.<table-name>
what is the deference between schema level and table level supplemental logging?

For Oracle, ADD TRANDATA by default enables table-level supplemental logging. The supplemental log group includes one of the following sets of columns, in the listed order of priority, depending on what is defined on the table:
1. Primary key
2. First unique key alphanumerically with no virtual columns, no UDTs, no functionbased
columns, and no nullable columns
3. First unique key alphanumerically with no virtual columns, no UDTs, or no functionbased
columns, but can include nullable columns
4. If none of the preceding key types exist (even though there might be other types of keys
defined on the table) Oracle GoldenGate constructs a pseudo key of all columns that
the database allows to be used in a unique key, excluding virtual columns, UDTs,
function-based columns, and any columns that are explicitly excluded from the Oracle
GoldenGate configuration.
The command issues an ALTER TABLE command with an ADD SUPPLEMENTAL LOG DATA clause that
is appropriate for the type of unique constraint (or lack of one) that is defined for the table.
When to use ADD TRANDATA for an Oracle source database
Use ADD TRANDATA only if you are not using the Oracle GoldenGate DDL replication feature.
If you are using the Oracle GoldenGate DDL replication feature, use the ADD SCHEMATRANDATA command to log the required supplemental data. It is possible to use ADD
TRANDATA when DDL support is enabled, but only if you can guarantee one of the following:
● You can stop DML activity on any and all tables before users or applications perform DDL on them.
● You cannot stop DML activity before the DDL occurs, but you can guarantee that:
❍ There is no possibility that users or applications will issue DDL that adds new tables whose names satisfy an explicit or wildcarded specification in a TABLE or MAP
statement.
❍ There is no possibility that users or applications will issue DDL that changes the key definitions of any tables that are already in the Oracle GoldenGate configuration.
ADD SCHEMATRANDATA ensures replication continuity should DML ever occur on an object for which DDL has just been performed.
You can use ADD TRANDATA even when using ADD SCHEMATRANDATA if you need to use the COLS option to log any non-key columns, such as those needed for FILTER statements and KEYCOLS clauses in the TABLE and MAP parameters.
Additional requirements when using ADD TRANDATA
Besides table-level logging, minimal supplemental logging must be enabled at the database level in order for Oracle GoldenGate to process updates to primary keys and
chained rows. This must be done through the database interface, not through Oracle GoldenGate. You can enable minimal supplemental logging by issuing the following DDL
statement:
SQL> alter database add supplemental log data;
To verify that supplemental logging is enabled at the database level, issue the following statement:
SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
The output of the query must be YES or IMPLICIT. LOG_DATA_MIN must be explicitly set, because it is not enabled automatically when other LOG_DATA options are set.
If you required more details refer Oracle® GoldenGate Windows and UNIX Reference Guide 11g Release 2 (11.2.1.0.0)

Logging HTTP and/or SOAP packets in standalong OC4J v10.1.3.2

I'm running OC4J standalone v10.1.3.2 on RH5 linux. I'd like to know how to turn on logging so that all incoming HTTP data can be viewed.
I've basically got a Web Service which is failing to execute from some clients (but not all) due to a SOAP11 version mismatch problem. If I could see the incoming HTTP and/or SOAP request then I could determine where the inconsistency is coming from.
Here's an extract of the returned SOAP error:
<faultcode>env:VersionMismatch</faultcode>
<faultstring>Version Mismatch</faultstring>
<faultactor>http://schemas.xmlsoap.org/soap/actor/next</faultactor>
I've tried editing j2ee-logging.xml and set the logging level to FINEST and TRACE but it's still not logging out the HTTP traffic.
Any ideas welcomed,
Thanks

Andy,
Which log files are you looking at? There is a server.log that will be impacted when you set the logging level to FINEST. Since you want to look at http requests, have you considered using Fiddler on the client side? It's pretty verbose but you can see all sorts of info including data posted to forms.
-Michael
PS
URL:
http://www.oracle.com/technology/tech/java/oc4j/htdocs/oc4j-logging-debugging-technote.htmlTake a look at the "Debug Options in OC4J" section. There are several HTTP debugging options listed.
Edited by: Michael F. Hardy on Dec 17, 2008 9:40 AM

How to increase log level for SUNW.oracle_listener resource type

I understand that i can increase logging level for a resource with "clrs set -p "Debug_level=$LEVEL", but the SUNW.oracle_listener resource type doesn't seem to have this property. Is there some other way of increasing log data to debug an issue with a listener resource? I ask because we have a strange situation where our database listener is being restarted every once in a while. With the log data I have, it appears that the listener is being stopped or dies, and then the monitor restarts it when it detects the fault, however our DBA's believe that it is the cluster that is actually the one cycling it because the monitor fails or is unable to connect because it is too busy to respond in time or something along those lines.
Maybe I am incorrect and it is the cluster, but I'd expect to see something before a "Attempting to restart listener" log entry, something along the lines of the monitor failing or a "no response in given time" before the resource says it is restarting.
Here are the logs from when this first happens, if anyone can advise, I would really appreciate it.
Sep 28 14:17:48 SC[SUNWscor.oracle_listener.monitor]:oracle:oraclels: Attempting to restart listener oracle.
Sep 28 14:17:50 SC[SUNWscor.oracle_listener.monitor_stop]:oracle:oraclels: Stopping fault monitor using pmfadm tag ORALSNR_MON_oraclels
Sep 28 14:17:52 SC[SUNWscor.oracle_listener.stop]:oracle:oraclels: Stopping listener oracle.
Sep 28 14:17:52 SC[SUNWscor.oracle_listener.stop]:oracle:oraclels: Using method 'run_setuid_prog' to execute shutdown commands
Sep 28 14:18:00 SC[SUNWscor.oracle_listener.stop]:oracle:oraclels: Listener oracle stopped successfully
Sep 28 14:18:02 SC[SUNWscor.oracle_listener.start]:oracle:oraclels: Starting listener oracle.
Sep 28 14:18:02 SC[SUNWscor.oracle_listener.start]:oracle:oraclels: Using method 'run_setuid_prog' to execute start commands
Sep 28 14:18:06 SC[SUNWscor.oracle_listener.start]:oracle:oraclels: Listener oracle started.
Sep 28 14:18:08 SC[SUNWscor.oracle_listener.monitor_start]:oracle:oraclels: Starting monitor

Thanks for the reply Thorsten. The logs I included in the original post are actually from /var/opt/SUNWscor/oracle_listener/messages_log.$RESOURCE. I'd like to bump up the verbosity on the oracle_listener logs like I can with the oracle_server logs, but for whatever reason there is no debug_level parameter for the oracle_listener resource type. Sounds like I may be SOL, but thought I'd check with the forum and verify.

Logging open and close of documents?

I'd like to have a record of when I open and close documents, so that I can support my diary notes of jobs I've been working on. So I need to have the filename recorded. I can find an app' to log application usage; is there one for file usage ?
regards, alan

Hi, alan.
This search of VersionTracker reveals two apps that track document time. Of the two, T3, looks exactly like what you want, but it is expensive. Check out the developer's site
Active Timer may be more to your liking: it can track time at the application window level and is free.
You can investigate other solutions by searching MacUpdate or Version Tracker. The user-submitted reviews accompanying the listings can be helpful in sorting the wheat from the chaff. Try searches for time track and look at the various options each provides.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

Troubleshooting Mail using the Mail.crash.log file and TN2123 CrashReporter

This morning, for apparently no reason at all, Mail began to consistently crash each time I attempted to send or reply to a message. By observing what occured in mail, opening the crash log [mail.crash.log] located here…
Macintosh HD:Users:<username>:Library:Logs:CrashReporter
…and parsing the information with the help of the Apple Developer Technical Note linked below, I was able to quickly determine that my last action just prior to sending the message—appending a signature to it—resulted in the application crashing. Simply by deleting the existing signature and recreating it, I was able to resolve the problem in only a matter of minutes.
This demonstrates how useful crash logs can be, and why they should likely be the very first place you look for an indication of trouble when an application unexpectely quits.
Here is a very short, relevent section of my Mail crash log which you can examine using the instructions linked below:
Host Name: Michael-Lafferty
Date/Time: 2006-05-15 09:37:57.885 -0700
OS Version: 10.4.6 (Build 8I127)
Report Version: 4
Command: Mail
Path: /Applications/Mail.app/Contents/MacOS/Mail
Parent: WindowServer [64]
Version: 2.0.7 (746.2)
Build Version: 2
Project Name: MailViewer
Source Version: 7460200
PID: 1662
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 com.apple.WebCore 0x956065d4 khtml::CompositeEditCommand::insertNodeAfter(DOM::No
1 com.apple.WebCore 0x956b0b34 khtml::DeleteSelectionCommand::moveNodesAfterNode()
2 com.apple.WebCore 0x956b1640 khtml::DeleteSelectionCommand::doApply() + 688
3 com.apple.WebCore 0x955ff41c khtml::EditCommand::apply() + 52
4 com.apple.WebCore 0x955ff9c8 khtml::CompositeEditCommand::applyCommandToComposite
5 com.apple.WebCore 0x956a75c4 khtml::CompositeEditCommand::deleteSelection(khtml::…
This is the most significant section of a very long, multi-threaded log, because it shows the detail of the thread which crashed, the actual step at which it crashed, and the particular crash type: in this case, a EXCBADACCESS (0x0001) - KERNPROTECTIONFAILURE, indicating an attempt to write to a read-only memory location.
Here is a link to the Apple Developer documentation you can use to troubleshoot such issues:
http://developer.apple.com/technotes/tn2004/tn2123.html
Technical Note TN2123
CrashReporter

This morning, for apparently no reason at all, Mail began to consistently crash each time I attempted to send or reply to a message. By observing what occured in mail, opening the crash log [mail.crash.log] located here…
Macintosh HD:Users:<username>:Library:Logs:CrashReporter
…and parsing the information with the help of the Apple Developer Technical Note linked below, I was able to quickly determine that my last action just prior to sending the message—appending a signature to it—resulted in the application crashing. Simply by deleting the existing signature and recreating it, I was able to resolve the problem in only a matter of minutes.
This demonstrates how useful crash logs can be, and why they should likely be the very first place you look for an indication of trouble when an application unexpectely quits.
Here is a very short, relevent section of my Mail crash log which you can examine using the instructions linked below:
Host Name: Michael-Lafferty
Date/Time: 2006-05-15 09:37:57.885 -0700
OS Version: 10.4.6 (Build 8I127)
Report Version: 4
Command: Mail
Path: /Applications/Mail.app/Contents/MacOS/Mail
Parent: WindowServer [64]
Version: 2.0.7 (746.2)
Build Version: 2
Project Name: MailViewer
Source Version: 7460200
PID: 1662
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 com.apple.WebCore 0x956065d4 khtml::CompositeEditCommand::insertNodeAfter(DOM::No
1 com.apple.WebCore 0x956b0b34 khtml::DeleteSelectionCommand::moveNodesAfterNode()
2 com.apple.WebCore 0x956b1640 khtml::DeleteSelectionCommand::doApply() + 688
3 com.apple.WebCore 0x955ff41c khtml::EditCommand::apply() + 52
4 com.apple.WebCore 0x955ff9c8 khtml::CompositeEditCommand::applyCommandToComposite
5 com.apple.WebCore 0x956a75c4 khtml::CompositeEditCommand::deleteSelection(khtml::…
This is the most significant section of a very long, multi-threaded log, because it shows the detail of the thread which crashed, the actual step at which it crashed, and the particular crash type: in this case, a EXCBADACCESS (0x0001) - KERNPROTECTIONFAILURE, indicating an attempt to write to a read-only memory location.
Here is a link to the Apple Developer documentation you can use to troubleshoot such issues:
http://developer.apple.com/technotes/tn2004/tn2123.html
Technical Note TN2123
CrashReporter

[svn] 3120: When you point Flex Builder at a local sandbox trunk build, it couldn' t generate the html-templates folder correctly for new projects so we moved all the html templates up one level and removed the html-templates directory and adjusted build

Revision: 3120
Author: [email protected]
Date: 2008-09-05 10:44:10 -0700 (Fri, 05 Sep 2008)
Log Message:
When you point Flex Builder at a local sandbox trunk build, it couldn't generate the html-templates folder correctly for new projects so we moved all the html templates up one level and removed the html-templates directory and adjusted build.xml's to accommodate the directory change
Modified Paths:
flex/sdk/trunk/build.xml
flex/sdk/trunk/webapps/webtier/build.xml
Added Paths:
flex/sdk/trunk/templates/client-side-detection/
flex/sdk/trunk/templates/client-side-detection/AC_OETags.js
flex/sdk/trunk/templates/client-side-detection/index.template.html
flex/sdk/trunk/templates/client-side-detection-with-history/
flex/sdk/trunk/templates/client-side-detection-with-history/AC_OETags.js
flex/sdk/trunk/templates/client-side-detection-with-history/history/
flex/sdk/trunk/templates/client-side-detection-with-history/history/history.css
flex/sdk/trunk/templates/client-side-detection-with-history/history/history.js
flex/sdk/trunk/templates/client-side-detection-with-history/history/historyFrame.html
flex/sdk/trunk/templates/client-side-detection-with-history/index.template.html
flex/sdk/trunk/templates/express-installation/
flex/sdk/trunk/templates/express-installation/AC_OETags.js
flex/sdk/trunk/templates/express-installation/index.template.html
flex/sdk/trunk/templates/express-installation/playerProductInstall.swf
flex/sdk/trunk/templates/express-installation-with-history/
flex/sdk/trunk/templates/express-installation-with-history/AC_OETags.js
flex/sdk/trunk/templates/express-installation-with-history/history/
flex/sdk/trunk/templates/express-installation-with-history/history/history.css
flex/sdk/trunk/templates/express-installation-with-history/history/history.js
flex/sdk/trunk/templates/express-installation-with-history/history/historyFrame.html
flex/sdk/trunk/templates/express-installation-with-history/index.template.html
flex/sdk/trunk/templates/express-installation-with-history/playerProductInstall.swf
flex/sdk/trunk/templates/metadata/
flex/sdk/trunk/templates/metadata/AC_OETags.js
flex/sdk/trunk/templates/metadata/readme.txt
flex/sdk/trunk/templates/no-player-detection/
flex/sdk/trunk/templates/no-player-detection/AC_OETags.js
flex/sdk/trunk/templates/no-player-detection/index.template.html
flex/sdk/trunk/templates/no-player-detection-with-history/
flex/sdk/trunk/templates/no-player-detection-with-history/AC_OETags.js
flex/sdk/trunk/templates/no-player-detection-with-history/history/
flex/sdk/trunk/templates/no-player-detection-with-history/history/history.css
flex/sdk/trunk/templates/no-player-detection-with-history/history/history.js
flex/sdk/trunk/templates/no-player-detection-with-history/history/historyFrame.html
flex/sdk/trunk/templates/no-player-detection-with-history/index.template.html
Removed Paths:
flex/sdk/trunk/templates/html-templates/

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

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

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)

SSISDB Verbose Logging Level and Unexpected Terminiation

Similar Messages

Maybe you are looking for