Activation Failed for Custom plugin in OAM

Activation Failed for Custom plugin in OAM

In this blog I am going to cover a common issue faced during the deployment of any custom plugin in OAM(Oracle Access Manager).

Issue:-   When someone is trying to deploy any custom or New plugin( having size > 2MB> in OAM through OAM console , the deployment of plugin failed with error message <BEA-000000> <Action failed due to inconsistent status of plugin in different managed servers.>

Steps to Reproduce :- 

·         Login to OAM Console and navigate to Application security -> Authentication Plugins 

·         Select any out of the box plugin that you want to deploy.

·         scroll down and click on 'Activation status'. You will see the following error message as shown in screenshot.

·         Also In  AdminServer logs , you will noticed the below error message.

<Aug 15, 2016 7:41:27 PM EDT> <Error> <oracle.oam.extensibility.lifecycle

<BEA-000000> <Action failed due to inconsistent status of plugin in different

managed servers.>

Reason:- This is due to improper loading of the configuration of plugins information in from oam-config.xml or due to the over size of the plugin which, cause uneven distribution of plugin information in clustered environment. 

Workaround :- In order to resolve the issue, you can directly update the “activation status” of plugin to true in oam-config.xml. To do so, follow the steps mentioned below:

·         Go to <OAMDomain_Home>/config/fmwconfig/

·         Edit oam-config.xml 

·         Search for failed plugin name in oam-config.xml file. In my case, it is 'AdaptiveAuthenticationPlugin'. you will find the below section

·         Now make sure the 'activated' status as  'true'.

·          Now increment the oam-config.xml version number by 1 in the below section. This should be in the beginning sections of oam-config.xml

·                   Save the file and restart Admin Server in OAM domain

After restart check the  Activation status of the plugin. It should be now load properly and will show the managed servernames as given below. 

  Hope this will be helpful for you. Please check my other posts and follow me to get more updates  on OAM and Weblogic related issue and simple workarounds.