Error starting OAM on IBM AIX : AMInitServlet : failed to preload on startup oam java. lang. Exception InInitializer Error

If you are starting OAM 11g server and it fails with error like below (start up errors are logged on WebLogic managed server for OAM i.e. oam_server1 under $DOMAIN_HOME/ servers/ [oam_server1]/ logs) then verify that JDK (java version) you are using is certified with OAM 11g version.

_________
####<05-May-2011 13:58:03 o’clock BST> <Error> <HTTP> <servername> <oam_server1> <[ACTIVE] ExecuteThread: ‘1’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1304600283378> <BEA-101216>

<Servlet: “AMInitServlet” failed to preload on startup in Web application: “oam”.
java.lang.ExceptionInInitializerError at java.lang.ExceptionInInitializerError.<init>(ExceptionInInitializerEr
ror.java:72)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:130)
        at oracle.security.am.engines.sso.adapter.SMEAdapter.<init>(SMEAdapter.java:81)
        at oracle.security.am.engines.sso.adapter.SMEAdapter.<clinit>(SMEAdapter.java:96)
        at java.lang.J9VMInternals.initializeImpl(Native Method)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
____________

Issue : In my case java version was 1.6 release 4 (on IBM AIX)
Fix : Upgrade JDK to certified version i.e. IBM 1.6 release 7 or higher

____________
java -version
java version “1.6.0”
Java(TM) SE Runtime Environment (build pap6460sr4ifix-20090617_02(SR4+IZ51489+IZ45701+IZ52413+IZ52880))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr4ifx-20090601_36519 (JIT enabled, AOT enabled)
J9VM – 20090601_036519_BHdSMr
____________

How to find certified JDK version with Oracle Identity and Access Management ?

For certified JDK/JVM with Oracle Access Manager 11g, check Identity and Access Management certification matrix click here (sheet “Current System Certification“)

For Fusion Middleware 11g certification matrix click here

How to find which JAVA (JDK) OAM server is using ?

There could be multiple JDK (Java 1.6_10 or 1.6_17 or 1.5_XX) installed on same machine under different directories. To find out JDK used by running server on Unix run command “ps -ef | grep java”

Note down output like below
____________
idam11g 22441 22391 2 May09 ? 02:54:08 /oracle/apps/java/bin/java-jrockit -Xms512m -Xmx1024m -Dweblogic.Name=AdminServer -Djava.security.policy=/oracle/apps/idam11g/mw_home/wlserver_10.3/serve…….
___________

To find JDK version for above server run
“/oracle/apps/java/bin/java -version”

Output like below indicates that Server (Dweblogic.Name=AdminServer) is using JRockit 28 which is equivalent to JAVA 1.6 update 17
_____
java version “1.6.0_17”
Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
Oracle JRockit(R) (build R28.0.0-679-130297-1.6.0_17-20100312-2128-linux-ia32, compiled mode)
_____

About the Author Atul Kumar

Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Specialising in Design, Implement, and Trainings.

follow me on:

Leave a Comment:

5 comments

Ramasamy says August 30, 2011

I am also getting the same problem…

We are using the latest version of IBM JDK SR9 FP2 (build pap6460sr9fp2-20110627_03(SR9 FP2), but still we are getting…

I also tried with SR8, SR9FP1, but no success.

Any solution?

Thanks
Ramasamy

Atul Kumar says August 31, 2011

@ Ramasamy

Try with SR8 FP1

java version “1.6.0”
Java(TM) SE Runtime Environment (build
pap6460sr8fp1ifix-20101215_02(SR8 FP1+IZ80785+IZ83273))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64
jvmap6460sr8ifx-20101214_70794 (JIT enabled, AOT enabled)
J9VM – 20101214_070794
JIT – r9_20100401_15339ifx4
GC – 20100308_AA)
JCL – 20100624_01

Ramasamy says August 31, 2011

Atul,

I tried with SR8FP1 also, but no success.

$java -version
java version “1.6.0”
Java(TM) SE Runtime Environment (build pap6460sr8fp1ifix-20101215_02(SR8 FP1+IZ80785+IZ83273))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr8ifx-20101214_70794 (JIT enabled, AOT enabl
ed)
J9VM – 20101214_070794
JIT – r9_20100401_15339ifx4
GC – 20100308_AA)
JCL – 20100624_01
$

Ramasamy says August 31, 2011

Atul,

It looks like we are hitting the Bug 10097234 as we are experiencing all the issues listed in the bug… Waiting for the resolution from Oracle Support.

– Ramasamy

Aspi E says September 7, 2011

Sharing my experiences.

We are installing OAM/OIM 11.1.1.5.0 on RHEL 5.5 with Sun JDK 1.6.0_26

We were able to install the entire suite of products successfully. This includes OAM, OIM, SOA, OVD and ODSEE.

Now we are in the process of setting up a completely separate middleware home and installing a completely separate region on the same physical server. The first problem that we ran into was when starting up the Admin Server

#### <> <2011-09-01 12:22:42.468/67.363 Oracle Coherence GE 3.5.3/465p2 (thread=[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’, member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service “Cluster” (ServiceState=SERVICE_STOPPED, STATE_ANNOUNCE)
at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:38)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:38)
at com.tangosol.coherence.component.net.Cluster.onStart(Cluster.CDB:366)
at com.tangosol.coherence.component.net.Cluster.start(Cluster.CDB:11)
at com.tangosol.coherence.component.util.SafeCluster.startCluster(SafeCluster.CDB:3)
at com.tangosol.coherence.component.util.SafeCluster.restartCluster(SafeCluster.CDB:7)

…

#### <> <Exception on bootstrap of component Config.
java.lang.ExceptionInInitializerError
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at oracle.security.am.admin.config.util.GenericFactory.getManager(GenericFactory.java:317)
at oracle.security.am.admin.config.util.GenericFactory.getManager(GenericFactory.java:305)
at oracle.security.am.admin.config.util.GenericFactory.readObject(GenericFactory.java:220)
at oracle.security.am.admin.config.util.GenericFactory.validateAndGetObjectForMap(GenericFactory.java:115)
at oracle.security.am.admin.config.util.GenericFactory.getInstance(GenericFactory.java:103)
…

This seems to indicate that coherence could not start-up cleanly since we already had a OAM server running on the same node. Keep in mind that all our WL instances are non-clustered.

Subsequently, when we try to startup the OAM managed server, we get:
<Servlet: “AMInitServlet” failed to preload on startup in Web application: “oam”.
java.lang.ExceptionInInitializerError
at oracle.security.am.engines.sso.adapter.AbstractSessionAdapterImpl.checkAndInit(AbstractSessionAdapterImpl.java:90)
at oracle.security.am.engines.sso.adapter.AbstractSessionAdapterImpl.(AbstractSessionAdapterImpl.java:73)
at oracle.security.am.engines.sso.adapter.MultipleUserSessionAdapterImpl.(MultipleUserSessionAdapterImpl.java:56)
at oracle.security.am.engines.sso.adapter.MultipleUserSessionAdapterImpl.(MultipleUserSessionAdapterImpl.java:45)
at oracle.security.am.engines.sso.adapter.SessionManagementAdapterFactory.getAdapter(SessionManagementAdapterFactory.java:46)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at oracle.security.am.engines.common.adapters.ConfigServiceHelperImpl.getServerInstanceDetails(ConfigServiceHelperImpl.java:713)
at oracle.security.am.engines.sso.adapter.OAMSessionConfiguration.(OAMSessionConfiguration.java:52)
at oracle.security.am.engines.sso.adapter.OAMSessionConfiguration.(OAMSessionConfiguration.java:47)
at oracle.security.am.engines.sso.adapter.AbstractSessionAdapterImpl.checkAndInit(AbstractSessionAdapterImpl.java:90)
at oracle.security.am.engines.sso.adapter.AbstractSessionAdapterImpl.(AbstractSessionAdapterImpl.java:73)
Truncated. see log file for complete stacktrace

After reading the details of Bug 10097234, it seems that the bootstrap process can fail for a variety of reasons, and when it does do so, you get a partially configured OAM server.

I have no solutions at this time.

Thanks
Aspi Engineer
Putnam Investments

Add Your Reply