Explanation | The injection engine service for the specified server is not available. |
Action | The injection engine service is started as a singleton service on all application server processes. Check that the application server started without any errors. |
Explanation | 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 registered with the injection engine. |
Action | Ensure that the injection processors are being registered after the application server is started. |
Explanation | The method for the injection target must be a setter property method. |
Action | Ensure that the annotation or injection target XML is specifying the intended method. |
Explanation | There was an error when processing the meta data in the deployment descriptor. |
Action | Ensure that the XML contained in deployment descriptor is correct. |
Explanation | The injection engine was unable to properly set up the injection targets for the specified class. |
Action | Ensure that the correct annotations are contained within the class and within the XML in the deployment descriptor. |
Explanation | The bindings and injection information contain errors. |
Action | Ensure that the annotations contained in the class and XML contained in deployment descriptor is correct. |
Explanation | The processor failed to initialize. |
Action | Ensure that the processor is available and properly registered with the injection engine. |
Explanation | The container cannot process an environment entry due to a NumberFormatException exception. |
Action | Ensure that the value for the environment entry is a valid string representation for the specified type. |
Explanation | 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. |
Action | Change the java:comp/env context environment entry of the Boolean type to either a true or false value. |
Explanation | The injection engine encountered an exception when it attempted to create a java:comp/env entry. |
Action | Take action based upon message associated with exception. |
Explanation | The injection engine encountered a type that is not valid for an environment entry. |
Action | Ensure that you use one of following environment entry types: String, Character, Byte, Short, Integer, Long, Boolean, Double, Float, Class, and any subclass of Enum. |
Explanation | 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. |
Action | 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. |
Explanation | 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. |
Action | Change the annotation injection target to match the previously defined XML injection target of the same field or property method. |
Explanation | According to the EJB specification, an injection target field must not be declared final. |
Action | Correct either the field name or field signature to specify one of the non-private class fields. |
Explanation | The injection engine did not have the proper security credentials to access the member. |
Action | Take action based on the message that is associated with exception. |
Explanation | The field type indicated on the injection target is not correct. |
Action | Ensure that the annotation or injection target XML is specifying the intended field. |
Explanation | The class does not have a method or field with the configured injection target property name. |
Action | Ensure that the configured injection target property name is spelled correctly and that the class contains the corresponding field or property method. |
Explanation | The injection engine encountered an error when it attempted to use the injection target information that is specified in the XML code. |
Action | Ensure that the XML, which exists in the deployment descriptor, is correct. |
Explanation | The injection engine failed to load and instantiate the specified object class. |
Action | Ensure that the class is available and that the constructor is visible and accessible. |
Explanation | The information annotation or injection target is incorrect or incomplete. |
Action | Ensure that the annotation or injection target XML for the enterprise bean is correct. |
Explanation | The home and remote, or local-home and local elements, are either missing or cannot be resolved. |
Action | Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor. |
Explanation | The injection engine encountered an exception when it attempted to bind . |
Action | Take action based upon message associated with exception. |
Explanation | The type specified is not injectable into the class specified. |
Action | Ensure that the annotation or injection target XML for the enterprise bean is correct. |
Explanation | Only EJBContext or TimerService objects may be injected directly into an enterprise bean. |
Action | Ensure that the type specified is a EJBContext or TimerService object. |
Explanation | An object instance could not be obtained for the specified reference. |
Action | See the exception message text for further explanation. |
Explanation | A problem was encountered creating a reference to be found into the global Java Naming and Directory Interface (JNDI) namespace. |
Action | Ensure the reference specified is correct. |
Explanation | The XML for the specified reference is incorrect or incomplete. |
Action | Ensure that the XML, which exists in the deployment descriptor, is correct. |
Explanation | The interface class either is missing or cannot be found. |
Action | Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor and that the class is available. |
Explanation | The information annotation or injection target is incorrect or incomplete. |
Action | Ensure that the annotation or injection target XML for the enterprise bean is correct. |
Explanation | The application declared a reference to an object which could not be found. |
Action | Look for a previous message that indicates why the referenced object could not be found, and verify the configuration for the reference is correct. |
Explanation | The object specified is incorrect. |
Action | Ensure the object is set to a type Reference. |
Explanation | The factory was incorrectly specified. |
Action | Specify a factory for the binding object being used. |
Explanation | A name of the RefAddr for the Reference was not specified. |
Action | Specify a RefAddr for the Reference. |
Explanation | The interface class either is missing or cannot be found. |
Action | Ensure that the <ejb-ref> or <ejb-local-ref> tags are specified correctly in the XML deployment descriptor and that the class is available. |
Explanation | When multiple injection targets are configured for the same field or method, the injection engine is not able to determine which target to inject. |
Action | Do not configure the same field or method with multiple injection targets. |
Explanation | 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. |
Action | Verify that the enterprise beans, which are being referenced, exist in the same application. |
Explanation | Duplicate env-entry statements with the same name are not allowed. |
Action | Do not configure an env-entry with the same name. |
Explanation | The Enterprise JavaBeans (EJB) specification requires that the UserTransaction interface is unavailable to enterprise beans with container-managed transaction demarcation. |
Action | Do not to inject a UserTransaction interface into a container managed transaction bean. |
Explanation | A binding for the resource reference may have been omitted or specified incorrectly. |
Action | A resource reference is defined for a component with the @Resource annotation in a component class file, or one of the following XML stanzas in the deployment descriptor : resource-env-ref, resource-ref, message-destination-ref. Ensure that a binding is defined for the resource reference in the ibm-ejb-jar-bnd file if the component is an enterprise Java bean (EJB) module, ibm-web-bnd file if the component is a web application module, or ibm-application-client-bnd file if the component is a client module. |
Explanation | A value for an env-entry must be specified if the injection-target value is not set. |
Action | Specify a value, injection-target, or both for the env-entry. |
Explanation | The type of the resource identified by the resource reference binding cannot be checked for compatibility with the type defined on one of the following XML stanzas in the deployment descriptor : resource-env-ref, resource-ref, message-destination-ref. |
Action | Change the type declared for the resource reference in the deployment descriptor to a type that may be loaded. |
Explanation | The application will not function properly if the specified class is used. |
Action | The class should either be removed from the application, or the cause of the exception corrected. |
Explanation | The application will not function properly if the specified class is used. |
Action | The class should either be removed from the application, or the cause of the exception corrected. |
Explanation | The application will not function properly if the specified class is used. |
Action | The class should either be removed from the application, or the cause of the exception corrected. |
Explanation | The application will not function properly if the specified class is used. |
Action | The class should either be removed from the application, or the cause of the exception corrected. |
Explanation | When multiple resource references are defined in the XML deployment descriptor for the same component namespace with the same name, the type of the resource must be the same. A typical scenario where this may occur is when defining resource references for an Enterprise Java Bean (EJB) and for a corresponding interceptor class. Both the EJB and the interceptor share the same component namespace, so resource references that are common between the two must be the same type. |
Action | In the XML deployment descriptor, change the name of one of the resource references, or change the type of one of the references to match the other one. |
Explanation | When multiple resource references are defined in the XML deployment descriptor for the same component namespace with the same name, all attributes of the resource must either be the same, or one must be assignable to the other. A typical scenario where this may occur is when defining resource references for an Enterprise Java Bean (EJB) and for a corresponding interceptor class. Both the EJB and the interceptor share the same component namespace, so resource references that are common between the two must be compatible. |
Action | In the XML deployment descriptor, change the name of one of the resource references, or change one of the conflicting values so they are the same value or one is assignable to the other. |
Explanation | When multiple resource references are defined in the XML deployment descriptor and in source code annotations for the same component namespace with the same name, some attributes of the resource must either be the same, or one must be assignable to the other. |
Action | In the XML deployment descriptor or source code annotations, change the name of one of the resource references, or change one of the conflicting values so they are the same value or one is assignable to the other. |
Explanation | When multiple resource references are defined in source code annotations for the same component namespace with the same name, all attributes of the resource must either be the same, or one must be assignable to the other. |
Action | In the source code annotations, change the name of one of the resource references, or change one of the conflicting values so they are the same value or one is assignable to the other. |
Explanation | The scope of AutoLink is limited to the application in which the message destination reference occurs, and to servers that are not members of an Application Server cluster. |
Action | Verify that the message destination, which is being referenced, exists in the same application. Or, define a binding for the message destination. |
Explanation | Requesting injection of a resource into both a property instance variable and its corresponding set method is an error. |
Action | Remove one of the annotations from either the field or method. Either the field or the method could request injection of a resource of a different (non-default) name. By explicitly specifying the JNDI name of a resource, a single resource may be injected into multiple fields or methods of multiple classes. |
Explanation | According to the EJB specification, an injection target may only be declared static if it exists in the client container. |
Action | Either change the code for the injection target to be non-static, choose a different injection target, or remove the injection target and populate it manually. |
Explanation | According to the EJB specification, an injection target in the client container must be declared static. |
Action | Either change the code for the injection target to be static, choose a different injection target, or remove the injection target and populate it manually. |
Explanation | A cyclic or recursive injection occurs when the injection of one object requires another injection of the same object. For example, this scenario can occur when a stateful session bean attempts to inject an instance of the same type into itself. |
Action | Modify the application code or configuration so that injection targets do not depend on themselves either directly or indirectly. |
Explanation | The class was configured to have a UserTransaction instance injected into it, which is not allowed. If the class is a bean, then the bean is not configured for bean-managed transactions. If the class is an interceptor or Web service handler, then it is used by one or more beans that are not configured for bean-managed transactions. |
Action | Change the class to stop injecting a UserTransaction instance, or change the bean configuration to allow bean-managed transactions. If this class is an interceptor or Web service handler class that is used by multiple beans, some of which are configured for bean-managed transactions and others which are not, then create a new interceptor or Web service handler class that does not inject a UserTransaction instance and use it with the beans that are configured for container-managed transactions. |
Explanation | The class was configured to have method injection, but multiple methods are compatible with the type of the object to be injected. |
Action | Change the bean configuration to specify the exact type of one of the methods, change the class to have a method with a parameter type that is exactly the same as the type of the injection configuration, or change the class by removing or renaming one of the ambiguous methods. |
Explanation | When a reference with the same name is defined by several components that share a component namespace, all binding and extension properties of the reference must be the same. |
Action | In the binding or extension file of the module, change one of the conflicting values so they are the same. |
Explanation | A simple environment entry for an enterprise module of the Enum type must be assigned a valid Enum identifier value. |
Action | Change the simple environment entry of the Enum type to a valid Enum identifier value. |
Explanation | A simple environment entry for an enterprise module might be one of the following Java types: String, Character, Byte, Short, Integer, Long, Boolean, Double, Float, Class, and any subclass of Enum. |
Action | Change the simple environment entry to one of the supported types. |
Explanation | Reference names must either be relative to java:comp/env or start with java:global, java:app, java:module, or java:comp. |
Action | Change the reference name in the deployment descriptor and source code annotations. |
Explanation | The format for properties specified in the annotation is name=value. |
Action | Change the properties attribute in the source code annotation to have the name=value format. |
Explanation | The isolationLevel must be one of the following constants from the java.sql.Connection class: TRANSACTION_NONE, TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ, or TRANSACTION_SERIALIZABLE. |
Action | Change the isolationLevel attribute in the source code annotation to one of the valid values. |
Explanation | 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. |
Action | Verify that the enterprise beans, which are being referenced, exist in the same application. |
Explanation | Injection methods must follow the conventions of JavaBeans property set methods. |
Action | Either change the code for the injection method to have exactly one parameter, choose a different injection target, or remove the injection target and populate the value manually. |
Explanation | The application class loader or an application server class loader has loaded an annotation class that should have been loaded by a product class loader. This occurs when a class loader has been configured to load classes with the local class loader first (parent last). The annotation will only be recognized if it is loaded by a product class loader. |
Action | Remove the annotation class from the application or application server class path. |
Explanation | The specified attribute must either be unspecified or have the default value. |
Action | Remove the attribute from the source code annotation or deployment descriptor. |
Explanation | The Java Enterprise Edition specification states that if multiple components declare a reference in a shared namespace, the attributes of all declarations must be consistent. |
Action | Modify the attributes of the declarations so they are consistent. |
Explanation | A JNDI must be specified for class-level annotations. |
Action | Specify a JNDI name in the source code class-level annotation. |
Explanation | An object instance used for injection must match the type of the field or method parameter. |
Action | Verify that reference binding is correct for the reference. |
Explanation | The injection target could not be found because a class loading error occurred while obtaining a list of fields or methods for the class. |
Action | Ensure the application packaging and class loader settings are correct. |
Explanation | JNDI operations on a java:comp/env name are only supported on threads associated with a Java EE application component. |
Action | Modify the application so that the JNDI operation occurs on a thread associated with a Java EE application component. |
Explanation | An error occurred creating an instance of the object reference by the specified JNDI name. |
Action | See the nested exception or a prior error for more information about the error. |
Explanation | References declared in the META-INF/application.xml file can only use names in the java:global or java:app contexts. |
Action | Remove the reference, or update the reference name to have a java:global/ or java:app/ prefix. |
Explanation | The server was unable to find a binding with the specified name and type. |
Action | Define a resource with the specified name, or configure the application bindings to use a resource that is already defined. |
Explanation | The server was unable to find a binding with the specified name and type. The binding name was not specified by the application, so a default binding name was used. |
Action | Define a resource with the specified name, or configure the application bindings to use a resource that is already defined. |
Explanation | The server was unable to find a binding with the specified name and type. |
Action | Contact the service provider. |
Explanation | The server found a binding with the specified name and type, but an error occurred while accessing it. |
Action | See the exception message text for further explanation. |
Explanation | The application declares a reference to a session EJB, but the server is not configured with a feature that supports session EJBs. |
Action | Modify the server configuration to enable a feature that supports session EJBs. For example, enable the ejbLite-3.1 feature. |
Explanation | The binding contains an indirect lookup that refers to itself. For example, if the incorrect @Resource(name="jdbc/ds", lookup="java:comp/env/jdbc/ds") annotation is used, then the name has an implicit java:comp/env/ prefix, so the lookup string refers to the resource reference, which creates an infinite loop. |
Action | Change the lookup or binding-name to the target resource. For example, if the incorrect @Resource(name="jdbc/ds", lookup="java:comp/env/jdbc/ds") annotation is used, then the lookup could be changed to jdbc/ds, which will locate the resource in the default namespace. |
Explanation | This informational message is not translated. |
Action | See message for details. |
Explanation | This warning message is not translated. |
Action | See message for details. |
Explanation | This error message is not translated. |
Action | See message for details. |