Express (Distributed operating systems), v8.0 > Reference > Messages
CHKW
CHKW4500E: An internal error has occurred. Please check the log files for more information on the error occurred.
Explanation An error occurred performing the binding validation for the enterprise Java bean (EJB). This is an internal implementation error. Partial validation has been performed. Action Visit the product support web site for information on problem determination.
CHKW4510E: Invalid null EJB jar reference in EJB jar binding.
Explanation There is JAR reference value for the enterprise Java bean (EJB) that is null and not valid in the JAR binding for the EJB. Action Update the binding information for the EJB to correct the specified problem.
CHKW4511E: An EJB binding with an invalid or null EJB reference has been detected in the EJB bindings.
Explanation An enterprise Java bean (EJB) reference to an EJB binding is null or not valid. Action Update the EJB binding information to correct the specified problem.
CHKW4512W: No binding information has been specified for EJB, {0}. Binding information such as JNDI names must be specified for all EJB in an EJB jar before the module may be started in the application server.
Explanation No binding information has been specified for the enterprise Java bean (EJB). Binding information such as JNDI names must be specified for all the beans in an JAR file for the EJB before the module can be started in the Application Server. Action Update the information for the EJB binding to correct the specified problem.
CHKW4513W: No JNDI name has been specified for EJB, {0}. JNDI names must be specified for all EJB in an EJB jar before they can be started in the application server.
Explanation No binding information has been specified for the enterprise Java bean (EJB). Binding information such as JNDI names must be specified for all the beans in an JAR file for the EJB before the module can be started in the Application Server. Action Update the information for the EJB binding to correct the specified problem.
CHKW4514E: An EJB binding with an invalid or null EJB reference has been detected in the EJB bindings under EJB {0}.
Explanation An enterprise Java bean (EJB) binding with a EJB reference that is null or not valid has been detected in the EJB bindings. Action Update the EJB binding information to correct the specified problem.
CHKW4515W: No JNDI name has been specified for the EJB ref for home {0} under EJB {1}. JNDI names must be specified for all EJB refs in the EJB jar before the module may be started in the application server.
Explanation No JNDI name has been specified for the enterprise Java bean (EJB) reference for the home. JNDI names must be specified for all the EJB references in the JAR file for the EJB before the module can be started in the application server. Action Update the EJB binding information to correct the specified problem.
CHKW4516E: An EJB binding with an invalid or null resource reference has been detected in the EJB bindings under EJB {0}.
Explanation An enterprise Java bean (EJB) binding with a resource reference that is null or not valid has been detected in the EJB bindings under the EJB listed in the message text. Action Update the information for the EJB binding to correct the specified problem.
CHKW4517W: No JNDI name has been specified for the resource ref for resource of name {0} and type {1} under ejb {2}. JNDI names must be specified for all resource refs in the ejb jar before the module may be started in the application server.
Explanation No JNDI name has been specified for the resource reference. JNDI names must be specified for all the resource references in the JAR file for the EJB before the module can be started in the Application Server. Action Update the information for the EJB binding to correct the specified problem.
CHKW4518W: No data source has been specified for the container managed entity bean {0}. The default data source specified for the EJB jar will be used.
Explanation No data source has been specified for the container-managed entity bean. The default data source specified in the JAR file for the enterprise Java bean (EJB) will be used. Action Update the information for the EJB binding to correct the specified problem.
CHKW4519W: No JNDI name for a data source has been specified for the container managed entity bean {0}. The default data source specified for the ejb jar will be used.
Explanation No JNDI name for a data source has been specified for the container managed entity bean. The default data source specified in the JAR file enterprise Java bean (EJB) will be used. Action Update the information for the EJB binding to correct the specified problem.
CHKW4520W: No default CMP data source has been specified for this ejb jar, and some container managed entity beans do not have CMP data source JNDI names specified. The default CMP data source of the EJB Container will be used for all container managed entity beans with no CMP data source specified.
Explanation No default container-managed persistence (CMP) data source has been specified for this JAR file for the enterprise Java bean (EJB), and some container managed entity beans do not have CMP data source JNDI names specified. The default CMP data source of the EJB Container will be used for all the container-managed entity beans with no CMP data source specified. Action Update the information for the EJB binding to correct the specified problem.