WLS Servers In OPAM 11.1.2.3.0 Domain Fails To Start Via Weblogic Console / Node Manager (Doc ID 2034715.1)

Last updated on FEBRUARY 21, 2017

Applies to:

Oracle Privileged Account Manager - Version 11.1.2.3.0 and later
Information in this document applies to any platform.

Symptoms

Once the Installation is completed, the servers can be started independently using the $DOMAIN_HOME/bin/startWebLogic.sh and $DOMAIN_HOME/bin/startManagedWebLogic.sh commands.  However, when attempting to start the servers using the weblogic console or via WLST / NodeManager, The following error is generated in the Admin and Managed server logs:


<Jul 19, 2015 12:06:38 AM CDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: java.lang.NoClassDefFoundError: oracle/security/jps/service/trust/token/TokenException.
weblogic.security.service.SecurityServiceException: java.lang.NoClassDefFoundError: oracle/security/jps/service/trust/token/TokenException
       ....
Caused By: java.lang.NoClassDefFoundError: oracle/security/jps/service/trust/token/TokenException
       at java.lang.Class.forName0(Native Method)
       ....



The issue can be reproduced at will with the following steps:
1. Install and configure OPAM 11.1.2.3.0
2. Configure the WLS domain.
3. Install Nodemanager.
4. Attempt to start the WLS admin and managed servers via the Weblogic console or WLST Nodemanager command.


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