NullPointerException: Changing Oim Logging Levels via EM
(Doc ID 1443600.1)
Last updated on JANUARY 31, 2019
Applies to:
Identity Manager - Version 11.1.1.3.0 to 11.1.1.5.9 [Release 11g]Information in this document applies to any platform.
**Checked for Relevance on 02-Dec-2013**
Symptoms
After logging into Enterprise Manager to try setting OIM XELLERATE loggers to TRACE:32,one may start to see the following types of errors when provisioning a resource with a prepopulate adapter:
===
java.lang.NullPointerException
at com.thortech.util.logging.Logger.isInfoEnabled(Logger.java:610)
at com.thortech.xl.dataobj.rulegenerators.tcBaseRuleGenerator.run(tcBaseRuleGenerator.java:178)
===
===
[2012-01-04T14:55:48.947+01:00] [oim_server1] [NOTIFICATION] [IAM-0080006] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: oiminternal] [ecid: 984b1f975f3e686b:-71849d4c:133f9934386:-8000-00000000000231d3,0] [APP: oim#11.1.1.3.0] Organiseringsprosessen er flyttet til mislykket fase, og den tilhørende feilen er - {0}[[
java.lang.NullPointerException
at com.thortech.util.logging.Logger.isDebugEnabled(Logger.java:599)
at com.thortech.xl.dataobj.tcDataObj.save(tcDataObj.java:466)
===
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |