An error occurs in WebSphere eXtreme Scale (WXS) profile creation after upgrading to 126.96.36.199 (or) later. The following error message is received when creating a new profile after the WebSphere eXtreme Scale product is upgraded to 188.8.131.52 or later in a WebSphere Application Server (WAS) V8.5.5.x integrated setup.
<message>java.lang.UnsupportedClassVersionError: JVMCFRE003 bad
major version;class=com/ibm/websphere/models/config/catalogservice/impl/CatalogservicePackageImpl, offset=6
WebSphere eXtreme Scale 184.108.40.206 (or) later doesn't support Java 6. Thus, if a profile is using Java 6, no server with WXS installed will start. This is why a profile that is set to use java 6 fails at creation. The profile would be a invalid configuration and isn't allowed. The only way to get the profile creation to work is to create profiles which are using either Java 7, Java 7.1 or Java 8. By default, WebSphere Application Server 8.5.5.x ships with Java 6. When a new profile is created it uses the default Java version. To resolve the issue, the "default" Java version for WAS must be changed so that when the new profile is created it uses a Java version other than Java 6.
This can be done using a command similar to this one:
Example : WAS_HOME\bin>managesdk.sh(bat) -setNewProfileDefault -sdkname 1.7_64
This developerWorks article has more about managing the SDKs:
System administration in WebSphere Application Server V8.5, Part 4: Using pluggable SDK 7 to enable WebSphere Application Server for Java 7
Here are a few details from the above article above:
Enable new profiles to use SDK 7
After enabling new profiles to use SDK 7, all profiles you subsequently create are automatically initially enabled to use SDK 7.
Before beginning, list the available SDKs to determine the SDK name of an available SDK 7 installation, then use the managesdk –setNewProfileDefault command with the -sdkName option to enable new profiles to use SDK 7. The example in Listing 3 assumes that the SDK name of an available SDK 7 installation is 1.7_32.
Listing 3 :
C:\wasInstalls\v85\Base\bin>managesdk.bat -setNewProfileDefault -sdkName 1.7_32 < CWSDK1022I: New profile creation will now use SDK name 1.7_32.
CWSDK1001I: Successfully performed the requested managesdk task.
Note that I set up a WAS 8.5.5 environment with WXS 8.6.1. I had the default JDK set to Java 6 and was able to recreate the profile creation failure. Once I changed the default JDK this was resolved. So, this solution should work for you.
In a nutshell, to use WXS 220.127.116.11 or higher, it is required that you use Java 7 or later. This is a limitation of WXS product and working per design.
This is documented in the following WXS 8.6.1 product documentation and also on the supported software page :
WebSphere eXtreme Scale 8.6.1 Detailed System Requirements
Note: Please go into "Supported software" tab , then check "Java SDK" section.
WebSphere eXtreme Scale 8.6.1 Hardware and software requirements