Table of Contents

WebSphere log error with Java 8 for Enterprise JavaBeans


Only available versions of this content are shown in the dropdown

For environments that are deployed by using Java 8 on IBM WebSphere Application Server version through the last 8.5.5.x fix pack, the log might report that a class was not found when the application server attempts to start Enterprise JavaBeans. If Java EE functionality is not needed, no further action is required. However, to use Enterprise JavaBeans, you must first deploy Pega Platform with Java 7; you can then run Pega Platform with Java 8 if you prefer.

To prevent this error, do the following steps:

  1. Set the Java edition for WebSphere Deployment Manager (Dmgr) to Java 7 by using the WebSphere managesdk command, for example:

    ./ -enableProfileAll -sdkName 1.7.1_64 –enableServers

  2. Deploy (or redeploy) Pega Platform.
  3. To run Pega Platform with Java 8, set Dmgr back to Java 8.

The following example shows the log message.

Trace: 2017/05/07 15:35:12.545 02 t=5C8A48 c=UNK key=P8 tag= (13007004) SourceId: ExtendedMessage: BBOO0220E: CNTR0075E: The user-provided class "com.pega.pegarules.internal.etier.interfaces.EJSRemoteStatelessEngineBMT_f2439d86" needed by the EnterpriseBean could not be found or loaded. Trace: 2017/05/07 15:35:12.549 02 t=5C8A48 c=UNK key=P8 tag= (13007004) SourceId: ExtendedMessage: BBOO0220E: WSVR0068E: Attempt to start EnterpriseBean prpc_j2ee14_ws73Beta23456#prbeans.jar#EngineBMT failed with exception: Bean class com.pega.pegarules.internal.etier.interfaces.EJSRemoteStatelessEngineBMT_f2439d86 could not be found or loaded

For more information about deploying Pega Platform, see Deployment Guides.

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.