Identity Management (MOSC)

MOSC Banner

OAM Custom Authentication Plugin Fails to Activate in Java 7

edited Jan 15, 2016 10:04AM in Identity Management (MOSC) 1 commentAnswered

We upgraded the version of Java from jdk1.6.0_101 to jdk1.7.0_80 on our OAM WebLogic 10.3.6 servers. This caused an existing, custom OAM Authentication Plugin to no longer activate. It was working fine in Java version jdk1.6.0_101. The ONLY change we made to the system that caused the plugin to fail was the Java upgrade. Reverting the system back to the older version of Java fixes the problem. Does anyone know why the Plugin would work with Java 1.6 but not with Java 1.7?

When we try to start the WL managed OAM servers, we receive this error in the WL log:

<Warning> <oracle.oam.extensibility.lifecycle> <BEA-000000> <Activation failed due to felix bundle exception while installing and starting the bundle.null

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center