IBM Support

WebSphere server does not start correctly after deploying CBA extensions that require Java 1.8 when using WAS 8.5.5 FixPack 12



When deploying CBA extensions to a WebSphere server at FixPack level 12, if the CBA manifest specifies Java 1.8 as the required execution environment, the “MDM-operational-server-EBA-E001” Business Level Application will fail to start correctly and the following entry will be found in the SystemOut.log for the WAS server: WSVR0194E: Composition unit in BLA WebSphere:blaname=MDM-operational-server-EBA-E001 failed to start. In addition, there will be an FFDC entry indicating that Java 1.8 could not be found: org.osgi.framework.BundleException: The bundle "]" could not be resolved. Reason: Missing Constraint: Bundle-RequiredExecutionEnvironment: JavaSE-1.8


Errors occur when detecting target runtime level, which prevents the CBD bundle from being initialized and cause the BLA to fail to start correctly.

Resolving The Problem

To work around this issue, change the bundle manifest in the CBA to require only Java 1.7 before it is deployed. This setting can be found in the following file:


Change the following line:

Bundle-RequiredExecutionEnvironment: JavaSE-1.8

As follows:

Bundle-RequiredExecutionEnvironment: JavaSE-1.7

It will be necessary to ensure that code generated in the CBA complies with JDK 1.7 specification.
use of Java 1.8 features will not be possible and any code that makes use of such features should be adjusted to comply with 1.7

[{"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"","Edition":"Advanced Edition","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 April 2022