WebSphere Management Subsystem messages

BNDE0000E: Could not bind EJBs: {0}
Explanation: An error occurred while generating default bindings for all EJBs contained in the application.
User Response: Validate your application using Application Assembly Tool.

BNDE0001E: Could not bind EJB references: {0}
Explanation: An error occurred while generating bindings for all EJB references in the application.
User Response: Validate your application using Application Assembly Tool.

BNDE0002E: Could not bind resource references: {0}
Explanation: An error occurred while generating bindings for all resource references in the application.
User Response: Validate your application using Application Assembly Tool.

BNDE0003E: Could not bind resource-env references: {0}
Explanation: An error occurred while generating bindings for all resource-env reference in the application.
User Response: Validate your application using Application Assembly Tool.

BNDE0004E: Could not bind virtual host(s): {0}
Explanation: An error occurred while generating virtual host bindings for all web modules in the application.
User Response: Validate your application using Application Assembly Tool.

BNDE0005W: Duplicate encountered: {0}
Explanation: An EJB with the same name already exists in the application.
User Response: none if the same name is used in an EJB belonging to different ejb jar file. If same name is used in the same ejb jar file, then validate your application using Application Assembly Tool.

BNDE0006W: could not be resolved: {0}
Explanation: An EJB with the name as specified in the ejb-link does not exist in the application.
User Response: Validate your application using Application Assembly Tool.

BNDE0007W: EJB reference could not be resolved: {0}
Explanation: An EJB with the home interface as specified by the EJB reference does not exist in the application.
User Response: Validate your application using Application Assembly Tool.

BNDE0008W: ambiguous EJB reference to {0} - use to clarify
Explanation: There is more than one matching EJB with the same home interface as specified by the EJB reference
User Response: Add ejb link element including the path name of the ejb jar that contains the reference enterprise bean. Validate your application using Application Assembly Tool.

BNDE0009W: CMP Bean {0} does not have a connection factory binding
Explanation: There is no connection factory binding for both the specified CMP bean and in the JAR which it belongs.
User Response: Rerun default bindings by providing the JNDI name for default connection factory or specify the connection factory binding during application install.

BNDE0010W: CMP Bean {0} does not have a data source binding
Explanation: There is no data source binding for both the specified CMP bean and in the JAR which it belongs.
User Response: Rerun default bindings by providing the JNDI name for a default data source or specify the data source binding during applicaiton install.


WebSphere Application Server  Last updated:  Thu Oct 21 12:17:05 EDT 2004
Library | Support | Trademarks | Feedback