search cancel

arcotadmin war doesnt start due to WAS pointing to unsupported JDK version


Article ID: 199403


Updated On:


CA Advanced Authentication - Strong Authentication (AuthMinder / WebFort) CA Strong Authentication CA Rapid App Security CA Risk Authentication CA Advanced Authentication


Advanced Authentication version  9.x supports both JDK/Java  7 and 8 but not JDK/Java 6. Note JDK/Java 6  which is the default Java version that is provided with many IBM WAS versions will lead to a error like such either in the IBM System Out  logs or Arcot Admin log (arcotadmin.log)

Below is the excerpt from Platform Support Matrix at location  - 


Here is the error message with stack trace one will see in the arcotadmin.log 

2020-08-20 16:37:26,363 ART : [Default : 4] : FATAL : web.init.ArcotAdminInitServlet : [N/A] : [N/A] : [N/A] : [Arcot Admin Console] : [Admin Console] : [N/A] : Application initialization failed, JVMCFRE003 bad major version; class=com/arcot/crypto/api/AccessKey, offset=6
java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=com/arcot/crypto/api/AccessKey, offset=6
 at$400( ~[?:1.7.0]
 at$ ~[?:1.7.0]
 at ~[?:1.7.0]
 at ~[?:1.7.0]
 at java.lang.ClassLoader.loadClassHelper( ~[?:1.7.0]


JDK 6 is being pointed to where Advanced Authentication supports JDK 7 for WAS 8.5.x only /JDK 8 for WAS 9.0.


Release : 9.1

Component : AuthMinder(Arcot WebFort)

Both Windows and Linux


WAS Admin configuration - WAS Java was pointing to non-supported JAVA 6 where Java7 for WAS 8.5.5 or Java 8 for WAS 9.0 was needed. Once a new cluster was built using IBM WAS and Java used was JDK 7 then admin came up without issues. 

Additional Information