CWOWB

CWOWB0100I: JCDI functionality is enabled.

Explanation

Java EE Context and Dependency Injection functionality is enabled on this server.

Action

No action is required.

CWOWB0101I: The JCDI custom property {0} is set to {1}

Explanation

Message indicates when a custom property is set and recognized by JCDI.

Action

No action is required.

CWOWB0102E: A JCDI error has occurred: {0}

Explanation

A JCDI error has occurred that will prevent normal operation.

Action

Review FFDC logs and exception text to identify the problem.

CWOWB0103E: An error occurred while processing the configuration: {0}

Explanation

An unexpected error has occurred while processing the configuration that prevents normal operation.

Action

Review FFDC logs and exception text to identify the problem.

CWOWB0104E: The EJB lifecycle for the following application could not start: {0}

Explanation

An unexpected error has occurred while processing an EJB

Action

Review FFDC logs and exception text to identify the problem.

CWOWB0105E: Could not locate a classloader to load the following class: {0}

Explanation

The specified class was not visible to the available classloaders.

Action

Review the classloader settings of the specified application class.

CWOWB0106I: JCDI functionality is disabled.

Explanation

Java EE Context and Dependency Injection functionality is disabled on this server.

Action

No action is required.

CWOWB0107I: JCDI functionality is disabled for the following application: {0}

Explanation

Java EE Context and Dependency Injection functionality is disabled for the specified application.

Action

No action is required.

CWOWB0108I: Error chasing runtime manifest classpath entry: {0} Reason: {1}

Explanation

Please examine the manifest classpath of your application module.

Action

No action is required.

CWOWB0109E: " BDA NOT recognized for: {0}

Explanation

JCDI runtime could NOT load classes resulting from a scan of the beans deployment archive.

Action

Please fix the ClassNotFoundException during application start

CWOWB0110W: Warning: {0}

Explanation

An unexpected error has occurred while processing the configuration that prevents normal operation.

Action

Please Review FFDC logs or exception text to identify the problem.

CWOWB1000E: A CDI error has occurred: {0}

Explanation

A CDI error has occurred that will prevent normal operation.

Action

Review FFDC logs and exception text to identify the problem.

CWOWB1001W: Web Application Archive {0} contains more than one beans.xml file. Using {1}. Ignoring {2}.

Explanation

CDI found more than one beans.xml file.

Action

Ensure the application archive contains only one beans.xml file.

CWOWB1002E: WebSphere Application Server internal error occurred. Please contact WebSphere Application Server support with the following data: {0} {1}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support.

CWOWB1003E: WebSphere Application Server internal error occurred. Please contact WebSphere Application Server support with the following data: {0} {1}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support.

CWOWB1004E: WebSphere Application Server internal error occurred. Please contact WebSphere Application Server support with the following data: {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support.

CWOWB1005E: WebSphere Application Server internal error occurred. Please contact WebSphere Application Server support with the following data: {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support.

CWOWB1006E: WebSphere Application Server internal error occurred. Please contact WebSphere Application Server support with the following data: {0}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support.

CWOWB1007E: The producer field, {0}, has type {1}, which does not match the type of the injected object.

Explanation

CDI found a resource producer field where the type of the field did not match the type of the Java EE resource injected into it.

Action

Ensure that the correct Java EE resource is being injected into the resource producer field and that the type of the field matches the type of the resource injected into it.

CWOWB1008E: The member {0} of class {1} cannot be injected as class {1} is not in a bean archive.

Explanation

The injection is not successful as the bean manager of the archive that the class belongs to is null.

Action

Ensure that the archive the class belongs to is a bean archive. Refer to the CDI specification on how to make an archive a bean archive.

CWOWB1009W: Implicit bean archives are disabled.

Explanation

Archives are not scanned for CDI beans unless they have a beans.xml file.

Action

Ensure that every archive that uses CDI has a beans.xml file or re-enable implicit beans scanning in your server.xml file.

CWOWB1010E: Failed to create CDI Extension {0} with SPI because of the exception {1}.

Explanation

CDI failed to invoke the constructor of an extension class that is registered with the getExtensions() method of a CDIExtensionMetadata implementation.

Action

Fix the error that is preventing your extension from instantiating.

CWOWB1011E: A {0} class registered through the CDI Extension SPI is in a different bundle than the CDIExtensionMetadata implementation.

Explanation

The class is ignored because it was registered with the getExtensions() or getBeanClasses() method of a CDIExtensionMetadata implementation and is in a different bundle than the CDIExtensionMetadata implementation.

Action

Move the affected class or create a new CDIExtensionMetadata implementation in the correct bundle.

CWOWB1012E: CDI encountered an exception when it created extensions for the {0} archive. The error was: {1}

Explanation

CDI failed to load or invoke the construction of an extension class.

Action

Fix the error that is preventing the extension from being created.

CWOWB1013E: The {0} BuildCompatibleExtension class cannot not be loaded.

Explanation

The application includes a META-INF/services/jakarta.enterprise.inject.build.compatible.spi.BuildCompatibleExtension file that includes the class, but CDI could not load the class.

Action

Ensure the class is present in the application and can be loaded. If the class is present in the application, an FFDC file might have more information about why the class could not be loaded.

CWOWB1014E: The {0} class does not implement the BuildCompatibleExtension interface.

Explanation

The application includes a META-INF/services/jakarta.enterprise.inject.build.compatible.spi.BuildCompatibleExtension file that includes the class, but the class does not implement jakarta.enterprise.inject.build.compatible.spi.BuildCompatibleExtension

Action

Change the class so that it implements jakarta.enterprise.inject.build.compatible.spi.BuildCompatibleExtension.

CWOWB1015I: The cdi12 configuration element is superseded by the cdi configuration element.

Explanation

The cdi configuration element replaces the cdi12 configuration element and contains all the same options, plus new options.

Action

Change your server.xml configuration to use the cdi configuration element instead of the cdi12 configuration element.

CWOWB1017W: The enableImplicitBeanArchives attribute was set on both cdi12 and cdi configuration elements. The value from the cdi element is used and the value in the cdi12 element is ignored.

Explanation

Although you can set the enableImplicitBeanArchives attribute on both of the cdi12 and cdi configuration element configuration elements, you should not set this attribute with different values in the same server configuration.

Action

Update your server.xml to fix the conflict. The recommended action is to remove the cdi12 configuration element because it is superseded by the cdi configuration element.

CWOWB1018W: Using an unversioned CDI beans.xml file might lead to unexpected behaviour when using CDI 4.0 or later: {0}

Explanation

Prior to CDI 4.0, a non-empty but unversioned beans.xml file meant that the archive was treated as an explicit bean archive (all classes are eligible to be beans). In CDI 4.0 or later, the archive is taken to be an implicit bean archive (only annotated classes are eligible be beans).

Action

Update the beans.xml file within your application to use a newer version of the schema and ensure that the version and bean-discovery-mode attributes are properly set.

CWOWB2000E: The annotation {0} is not allowed on EJB: {1}

Explanation

Annotation transactional cannot be used with EJB

Action

The TransactionAttribute should be used instead of Transactional with EJB's

CWOWB2001E: A {0} lifecycle inteceptor threw an exception: {1}

Explanation

Lifecycle interceptors should avoid throwing checked exceptions

Action

Check the logs to determine the problem

CWOWB2002E: WebSphere Application Server internal error occurred. Please contact WebSphere Application Server support with the following data: {0} {1}

Explanation

This exception is unexpected. The cause is not immediately known.

Action

See the problem determination information on the WebSphere Application Server Support web page: http://www.ibm.com/software/webservers/appserv/was/support.