Custom Auditor And Custom Authenticator Not Working In SOA 12.2.1.2 (Doc ID 2248277.1)

Last updated on APRIL 04, 2017

Applies to:

Oracle SOA Suite - Version 12.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

A custom auditor and custom authenticator is used in a SOA domain that was upgraded from 12.1.3 to 12.2.1.2. 


After configuring the new domain to use the custom providers, the servers won't start up anymore.
The providers have been recompiled using java 8 and the mbean maker tools from weblogic 12.2.1.2.0 and are building fine.
These providers worked fine with the former domain.

1. java.lang.NoClassDefFoundError: Could not initialize class weblogic.diagnostics.instrumentation.InstrumentationManager$InstrumentationManagerInitializer
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.t3.srvr.FinalThreadLocalService

A MultiException has 2 exceptions. They are:
1. java.lang.NoClassDefFoundError: Could not initialize class weblogic.diagnostics.instrumentation.InstrumentationManager$InstrumentationManagerInitializer
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.t3.srvr.FinalThreadLocalService

at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:391)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:471)



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms