Wednesday 1 April 2015

java.lang.NoClassDefFoundError: weblogic/security/SecurityLogger during admin server restart.

=======================================================================
Applies To:
SOA Product Type: BPEL - version 11.1.1.6.7
Oracle Database: Enterprise Edition - Version 11.2.0.3

========================================================================
Problem:
Admin Server is not able to start because of java.lang.NoClassDefFoundError: weblogic/security/SecurityLogger.

[INFO ][mgmnt  ] JDP autodiscovery started at address XXX.XXX.X.XXX:7001
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/security/SecurityLogger
        at weblogic.security.utils.SecurityUtils.turnOffCryptoJDefaultJCEVerification(SecurityUtils.java:81)
        at weblogic.Server.main(Server.java:67)
<Mar 30, 2015 12:49:40 PM> <FINEST> <NodeManager> <Waiting for the process to die: 18009>
<Mar 30, 2015 12:49:40 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Mar 30, 2015 12:49:40 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
========================================================================
Cause:
Security logger Jar files from the modules directory is corrupted/missing. This can be caused because of improper file transfer.

com.bea.core.weblogic.security.logger_1.5.0.0.jar
com.bea.core.weblogic.security.logger.ja_1.5.0.0.jar

========================================================================
Solution:
1.       If this domain is shared across multiple host, copy the missing modules directory jars from another host to the corrupted host.
 Or
 If this domains isn't shared across multiple hosts, you can copy jar files from another BPEL domain.
2.       Location of modules directory will be $ORACLE_HOME/modules.
3.       Make sure you have all required files and with the same size.
4.       Once done, restart admin server and it should come up fine.

No comments:

Post a Comment