Problem | |
User response |
Problem | The injection engine service for the specified server is not available. |
User response | The injection engine service is started as a singleton service on all application server processes. Check that the application server started withut any errors. |
Problem | The injection engine initializes a set of default injection processors during startup. The injection engine service must be started and initialized before additional injection processors can be registed with the injection engine. |
User response | Ensure that the injection processors are being registered after the application server is started. |
Problem | The method for the injection target must be a setter property method. |
User response | Ensure that the annotation or injection target XML is specifying the intended method. |
Problem | There was an error when processing the meta data in the deployment descriptor. |
User response | Ensure that the XML contained in deployment descriptor is correct. |
Problem | The injection engine was unable to properly set up the injection targets for the specified class. |
User response | Ensure that the correct annotations are contained within the class and within the XML in the deployment descriptor. |
Problem | The bindings and injection information contain errors. |
User response | Ensure that the annotations contained in the class and XML contained in deployment descriptor is correct. |
Problem | The container cannot process an environment entry due to a NumberFormatException exception. |
User response | Ensure that the value for the environment entry is a valid string representation for the specified type. |
Problem | A java:comp/env context environment entry for an enterprise bean of the Boolean type should be assigned either a true or false value. Any other value results in false value, but it might indicate a configuration problem. The application might not behave as expected. |
User response | Change the java:comp/env context environment entry of the Boolean type to either a true or false value. |
Problem | The injection engine encountered an exception when it attempted to create a java:comp/env entry. |
User response | Take action based upon message associated with exception. |
Problem | The injection engine encountered a type that is not valid for an environment entry. |
User response | Ensure that you use one of following environment entry types: String, Integer, Boolean, Double, Byte, Short, Long, or Float. |
Problem | The injection engine cannot link between the name that is declared in the java:comp/env namespace and the name of the target resource in the global Java Naming and Directory Interface (JNDI) namespace. |
User response | Ensure that the name that is declared on the injection, using @Resource annotation or resource-ref declaration, matches the same name in the binding XML file. |
Problem | The following information is stated in the EJB specification overriding rules: When an injection target is already present and is specified using XML, the annotation injection target must specify the same field or property method. |
User response | Change the annotation injection target to match the previously defined XML injection target of the same field or property method. |
Problem | According to the EJB specification, an injection target field must not be declared final. |
User response | Correct either the field name or field signature to specify one of the non-private class fields. |
Problem | The injection engine did not have the proper security credentials to access the member. |
User response | Take action based on the message that is associated with exception. |
Problem | The field type indicated on the injection target is not correct. |
User response | Ensure that the annotation or injection target XML is specifying the intended field. |
Problem | The class does not have a field value with the specified member name. |
User response | Ensure that the field is spelled correctly and that the class contains the field. |
Problem | The injection engine encountered an error when it attempted to use the injection target information that is specified in the XML code. |
User response | Ensure that the XML, which exists in the deployment descriptor, is correct. |
Problem | The injection engine failed to load and instantiate the specified object class. |
User response | Ensure that the class is available and that the constructor is visible and accessible. |
Problem | The information annotation or injection target is incorrect or incomplete. |
User response | Ensure that the annotation or injection target XML for the enterprise bean is correct. |
Problem | The home and remote, or local-home and local elements, are either missing or cannot be resolved. |
User response | Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor. |
Problem | The injection engine encountered an exception when it attempted to bind . |
User response | Take action based upon message associated with exception. |
Problem | The type specified is not injectable into the class specified. |
User response | Ensure that the annotation or injection target XML for the enterprise bean is correct. |
Problem | Only EJBContext or TimerService objects may be injected directly into an enterprise bean. |
User response | Ensure that the type specified is a EJBContext or TimerService object. |
Problem | The object factory specified is incorrect for the binding object. |
User response | Ensure the factory has an object bound correctly. |
Problem | A problem was encountered creating a reference to be found into the global Java Naming and Directory Interface (JNDI) namespace. |
User response | Ensure the reference specified is correct. |
Problem | The XML for the specified reference is incorrect or incomplete. |
User response | Ensure that the XML, which exists in the deployment descriptor, is correct. |
Problem | The interface class either is missing or cannot be found. |
User response | Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor and that the class is available. |
Problem | The information annotation or injection target is incorrect or incomplete. |
User response | Ensure that the annotation or injection target XML for the enterprise bean is correct. |
Problem | The reference object was specified incorrectly. |
User response | Ensure that the injection object specified is correct. |
Problem | The object specified is inccorrect. |
User response | Ensure the object is set to a type Reference. |
Problem | The factory was incorrectly specified. |
User response | Specify a factory for the binding object being used. |
Problem | A name of the RefAddr for the Reference was not specified. |
User response | Specicfy a RefAddr for the Reference. |
Problem | The interface class either is missing or cannot be found. |
User response | Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor and that the class is available. |
Problem | When multiple injection targets are configured for the same field or method, the injection engine is not able to determine which target to inject. |
User response | Do not configure the same field or method with multiple injection targets. |
Problem | The scope of AutoLink is limited to the application in which the EJB reference occurs, and to servers that are not members of a Application Server cluster. |
User response | Verify that the enterprise beans, which are being referenced, exist in the same application. |
Problem | Duplicate env-entry statements with the same name are not allowed. |
User response | Do not configure an env-entry with the same name. |
Problem | The Enterprise JavaBeans (EJB) specification requires that the UserTransaction interface is unavailable to enterprise beans with container-managed transaction demarcation. |
User response | Do not to inject a UserTransaction interface into a container managed transaction bean. |