BEA-000286 : Failed to invoke startup class “JRF Startup Class” oracle.jrf.wls.JRFStartup

I recently created WebLogic service on Windows using steps mentioned here for my Fusion Middleware software. When I started WebLogic from windows service, I couldn’t connect to Admin Server. Error message in Admin Server log file ($DOMAIN_HOME\ servers\ AdminServer\ logs) was


<28-Feb-2011 11:17:25 O’clock GMT> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class “JRF Startup Class”,

java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(

From logs it was clear that issue is because of missing JRF classes in CLASSPATH.

JRF(Java Required Files) includes important libraries and capabilities that provides APIs that many OC4J (Oracle Container for Java, Oracle’s old JVM) applications depend upon.  JRF comes (under $MW_HOME/oracle_common) when you install Fusion Middleware component like SOA, WebCenter or Identity Management. For steps on how to install JRF click here

Simple fix is to re-create service with JRF classes in CLASSPATH. This class (JRFStartUP) is in $MW_HOME\modules\oracle.jrf_11.1.1\jrf.jar

1.Class Path for Service is defined in $WL_HOME\common\bin\commEnv.cmd so add entry $MW_HOME\modules\oracle.jrf_11.1.1\jrf.jar in CLASSPATH
2.Delete/Uninstall existing WebLogic Admin Server service and create again
3. Start Admin Server using service and then try.

For MW_HOME or WL_HOME location in Fusion Middleware click here click here

Share This Post with Your Friends over Social Media!

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: