Any issue with CA-Web Viewer and JDK 1.8?

Document ID : KB000100929
Last Modified Date : 12/06/2018
Show Technical Document Details
Issue:
Web Viewer runs under WebSphere. The WAS group updated their server to Java 1.8. Then Web Viewer took a long time to logon and move around. It didn't build a repository list and timed out doing a repository status. The WAS team could not find many errors.
The following error occurred: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider incompatible with javax.persistence.spi.PersistenceProvider
Resolution:
both of the exceptions that were stopping Web Viewer from starting have been corrected. the persistence errors have been resolved by adding the Custom Property to the JPA, but that error is unchanged. To correct this error. For Tomcat you need to add the VM property: -Dsun.lang.ClassLoader.allowArraySyntax=true For WebSphere.
Example definitions are attached to this document.
Additional Information:
Research for the error revealed:
The following error occurred: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider incompatible with javax.persistence.spi.PersistenceProvider
…is consistent with a setting for disabling the JPA defaulting to OpenJPA. For other Java errors you may need to adjust the JAVA_HOME variable being used, or gather a dump of what is occurring to provide to Customer Support.
Start by checking settings and work on getting documentation towards resolving your issues with Web Viewer 12.1 and WebSphere/Tomcat with Java JDK 1.8.
When using Java 1.8 - For the JPA persistence errors, we found that the recommended Custom setting to exclude our CAWebViewer12 EAR from WebSphere JPA processing was not set. After setting this, WebSphere still comes up with errors pertaining to the “java.lang.ClassNotFoundException: [Ljava.lang.String;”, which is the exact same error that came out previously. You can open a PMR with IBM, since there seems to be a disconnect between the browser code for:
com.sun.faces.config.ConfigureListener
and the remaining stack trace information for com.ibm.ws.webcontainer for the webapp. The persistence errors have been resolved by adding the Custom Property to the JPA.
In looking at the “java.lang.ClassNotFoundException: [Ljava.lang.String;” error, you'll see that it is exactly the same as what was occurring before, so the persistence errors have been resolved by adding the Custom Property to the JPA, but that error is unchanged.
For Tomcat we know we need to add the VM property:
-Dsun.lang.ClassLoader.allowArraySyntax=true
Where that would be set in WebSphere? The customer knew where that would be added.
Examples attached within the JPA.zip file.
Customer asked about why the -Dsun option was added and what it meant. This was explained, but the important thing is that both of the exceptions that were preventing Web Viewer from starting have been corrected and subsequent testing was successful.
File Attachments:
JPA.zip