11G ASDK Application Fails If The Agent Configuration Is Changed In The OAMCONSOLE (Doc ID 1582188.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Access Manager - Version 11.1.2.0.0 to 11.1.2.1.0 [Release 11g]
Information in this document applies to any platform.

Symptoms

An 11G ASDK application works until the ASDK agent configuration is changed in the OAMCONSOLE.

A new execution of the application shows the error message:

 

oracle.security.am.asdk.AccessClient initialize
 SEVERE: Oracle Access SDK initialization failed.
 java.lang.NullPointerException
         at
 oracle.security.am.asdk.impl.ConfigXMLHandler.configuration2JAXBObjec
 t(ConfigXMLHandler.java:1063)
         at
 oracle.security.am.asdk.impl.ConfigXMLHandler.writeConfigurationToFil
 e(ConfigXMLHandler.java:173)
         at
 oracle.security.am.asdk.AccessClient.initializeHelper(AccessClient.ja
 va:1218)
         at
 oracle.security.am.asdk.AccessClient.initialize(AccessClient.java:134
 7)
         at oracle.security.am.asdk.AccessClient.<init>(AccessClient.java:912)
         at
 oracle.security.am.asdk.AccessClient.createDefaultInstance(AccessClie
 nt.java:338)
         at ASDKSample11.main(ASDKSample11.java:77)
 Exception in thread "main" oracle.security.am.asdk.AccessException:
 OAMAGENT-020

 

The obAccessClient.xml file shows a size of zero bytes after the failure.

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