CNTR

CNTR0001W: A Stateful SessionBean could not be passivated: {0} {1} {2}
CNTR0002W: Failed to get the wrapper for a home. Home: {0}
CNTR0003W: A Stateful SessionBean could not be activated: {0} {1} {2}
CNTR0004E: An attempt to acquire a lock was interrupted. Lock : {0}
CNTR0005W: An enterprise bean could not be passivated: {0} {1} {2}
CNTR0006W: EJBObject "{0}" could not be connected to the ORB.
CNTR0008W: A passivated Stateful SessionBean could not be removed: {0} {1} {2}
CNTR0009W: An attempt to access bean "{0}" failed because it was not previously installed or problems occurred during its installation.
CNTR0010W: NumberFormatException occurred while converting <env-entry-name> {0} <env-entry-value> {1}: {2}
CNTR0011W: An invalid type was specified for a bean''s java:comp/env context environment entry: <env-entry-name> {0}
CNTR0012W: Collaborator {0} threw unexpected exception - proceeding with remaining collaborators. Exception data:{1}
CNTR0013W: Unable to map exception. {0} {1}
CNTR0014W: StatefulBeanReaper thread was interrupted; terminating. {0}
CNTR0015W: An unexpected exception occurred during stateful bean cleanup. Exception data: {0} {1}
CNTR0016W: Passivated Stateful SessionBean "{0}" could not be removed due to exception: {1}
CNTR0017W: Security collaborator threw unexpected exception. Exception data: {0}
CNTR0018E: EJB threw an unexpected (non-declared) exception. Exception data: {0}
CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "{1}". Exception data: {0}
CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "{1}" on bean "{2}". Exception data: {0}
CNTR0021E: EJB threw an unexpected (non-declared) exception while invoking a method on bean "{1}". Exception data: {0}
CNTR0022E: Transaction coordinator not available. {0}
CNTR0023W: Directory "{0}" does not exist. The EJB Container will use the current directory for passivating beans.
CNTR0024W: Unable to open input stream: {0} {1} {2}
CNTR0025W: Unable to open output stream: {0} {1} {2}
CNTR0026W: DataSource name for CMP bean "{0}" is null. Bean will be unavailable for use.
CNTR0027W: Failed to commit connection: {0}
CNTR0028W: Failed to close connection: {0}
CNTR0031W: Error starting CMP bean {0}: {1}
CNTR0032W: Error creating CMP persister using datasource: {0}
CNTR0033E: EJB container ignoring caught unexpected exception: {0}.
CNTR0034I: ContainerEJBException.getExceptionChain is returning an incomplete list of exceptions.
CNTR0035E: EJB container caught {0} and is throwing {1}.
CNTR0036E: EJB container does not support using the bean instance for finder methods on EJB 1.x container managed persistence and is throwing {0}
CNTR0037E: Prepared statement does not map to connection.
CNTR0038W: The TX attribute needs to be changed to eliminate potential lost updates to bean {0} when used concurrently by multiple transactions. The bean should not be using the TX_NOT_SUPPORTED, TX_NEVER, or TX_SUPPORTS transaction attribute.
CNTR0039E: EJB container caught {0} and is rethrowing the caught exception.
CNTR0040E: Finder failure as a result of exception {0}.
CNTR0041W: Finder result collection exceeded limit. Only the first Integer.MAX_VALUE elements are processed.
CNTR0043E: Bean "{0}" is attempting to use an invalid combination of ActivationPolicy and LoadPolicy on a work load managed server.
CNTR0044W: Bean "{0}" is attempting to use an invalid combination of Activation Policy: Transaction and Load Policy : Activation. Defaulting Load Policy to : Transaction.
CNTR0045W: Unable to convert remote object to stub. Possible reason="{0}".
CNTR0046E: Bean "{0}" did not specify a connection factory binding.
CNTR0047E: Bean is attempting to use interface or method "{0}" in a situation prohibited by the EJB specification.
CNTR0048W: Bean''s finder method "{0}" erroneously specifies a finder collection timeout scope of zero.
CNTR0049E: Bean is attempting to use an invalid combination of Commit Option A and Optimistic Concurrency.
CNTR0050E: Protocol error occurred in container transaction.
CNTR0051E: Transaction has timed out due to no client activity for greater than {1} seconds. Transaction ID: {0}
CNTR0052W: LRU thread was interrupted. Terminating. {0}
CNTR0053W: Caught an exception during LRU sweep {0} {1}.
CNTR0054W: Exception thrown by discard strategy {0} {1}.
CNTR0055W: A Throwable exception was caught while attempting to construct <env-entry-name> {0} <env-entry-value> {1} {2}
CNTR0056W: Failed to get the wrapper for a bean. Bean: {0}
CNTR0057W: Minimum pool size specified for bean {0} not a valid integer: {1}. Default used instead.
CNTR0058W: Maximum pool size specified for bean {0} not a valid integer: {1}. Default used instead.
CNTR0059W: Minimum pool size specified for bean {0} is greater than maximum pool size specified: ({1},{2}) Defaults used instead.
CNTR0060I: (Min,Max) pool size is ({0},{1}) for bean {2}
CNTR0061I: Read-only attribute on findByPrimaryKey method overridden to true for bean: <All>
CNTR0062W: An equals sign was not found in the pool size specification string {0}
CNTR0063W: A reference to an EJB could not be found in the deployment descriptor for the WebApp or EnterpriseBean with the display name {0}. The EJB may have specified binding information that is not valid.
CNTR0064E: A bean instance of type "{0}" with an activity session based activation policy attempted to become involved with multiple concurrent transactions.
CNTR0065E: CMP bean "{0}" attempted to use an unsupported Local Transaction resolution control value.
CNTR0066E: Bean "{0}" attempted to use an invalid Local Transaction boundary value of "activity session".
CNTR0067W: SessionBean "{0}" or its home attempted to use an invalid combination of Bean Managed Transactions and Container Managed method-level transaction attributes. The method-level transaction attributes will be ignored.
CNTR0068W: Bean "{0}" or its home attempted to use an invalid combination of Bean Managed Activity Sessions and method-level Activity Session attributes.
CNTR0069E: Bean "{0}" in an EJB 1.1 module attempted to use an invalid "Activate at" policy of "Activity Session".
CNTR0070E: Bean "{0}" in an EJB 1.1 module attempted to use an invalid Local Transactions Boundary of "Activity Session".
CNTR0071E: Bean "{0}" in an EJB 1.1 module attempted to use an invalid Local Transactions Resolution control of "ContainerAtBoundary".
CNTR0072E: Bean "{0}" attempted to use an invalid "Activate at" policy with a container managed Activity Session.
CNTR0073E: Bean "{0}" attempted to use an invalid Local Transactions Resolution control.
CNTR0074E: Unexpected method call occurred in {0}.
CNTR0075E: The user-provided class "{0}" needed by the EnterpriseBean could not be found or loaded.
CNTR0076W: A reference to an ResourceRef could not be found in the deployment descriptor for the WebApp or EnterpriseBean with the display name {0}.
CNTR0077W: A reference to an ResourceEnvRef could not be found in the deployment descriptor for the WebApp or EnterpriseBean with the display name {0}.
CNTR0078I: Custom Finder access intent support enabled for bean {0}
CNTR0080E: EJB timer service is not available for EJB implementing the javax.ejb.TimedObject interface: {0}.
CNTR0081E: setTranEnlistmentNotNeeded called with an unrecognized reason code of {0}.
CNTR0082E: Cannot enlist XAResource since recovery ID for resource adapter {0} for MDB {1} is not known.
CNTR0083E: Creation of a message endpoint failed: {0}
CNTR0084E: Method {0} of MDB {1} is deployed with an incorrect transaction attribute.
CNTR0085E: MDB {0} must implement method {1} of interface {2}.
CNTR0086E: Transaction recovery setup error occurred for resource adapter {0}, MDB {1}.
CNTR0087E: Resource adapter {0} is not allowed to pass a non null XAResource to createEndpoint method for MDB {1}.
CNTR0088E: The user-provided class "{0}" may not implement the javax.ejb.TimedObject interface.
CNTR0089E: Transaction attribute {0} is not allowed for method "{1}" on EJB {2}.
CNTR0090E: WebServiceRef binding failed for {0} : {1}
CNTR0091W: A reference to a MessageDestinationRef could not be found in the deployment descriptor for the WebApp or EnterpriseBean with the display name {0}.
CNTR0092W: Attempted to access EnterpriseBean {0}, that has not been started.
CNTR0093E: Attempt to start EnterpriseBean {0} failed with exception: {1}
CNTR0094E: Entity bean "{0}" has been configured with a BeanCache LoadPolicy that will reload the Entity at an interval, but the Entity bean is not configured for EJB 2.x container managed persistence".
CNTR0095W: EJB module configuration for session bean "{0}" is missing override of memory-to-memory replication settings.
CNTR0096W: Application configuration for session bean "{0}" is missing override of memory-to-memory replication settings.
CNTR0097W: Memory-to-memory replication settings for EJB container is missing.
CNTR0098I: Container-managed pre-find persistent store synchronization disabled for bean: "{0}".
CNTR0099I: {0} service has initialized successfully.
CNTR0100E: Method {0} caught exception: {1}
CNTR0101E: Method {0} token is null.
CNTR0102E: Method {0} entryKey is null.
CNTR0103E: Method {0} value is null.
CNTR0104E: Method {0} cannot convert entryKey to byte array.
CNTR0105E: Method {0} caught exception: {1} stoken = {2}.
CNTR0106E: Method {0} cannot acquire proxy for stoken = {1}.
CNTR0107E: Method {0} cannot convert token to byte array : stoken = {1}.
CNTR0108E: Method {0} caught exception {1} while acquiring proxy for token = {2}.
CNTR0109E: Method {0} event parameter is null.
CNTR0110E: Method {0} cannot convert value to byte array.
CNTR0111E: Method {0} cannot convert event to byte array : stoken = {1}.
CNTR0112E: The user-provided class "{0}" must implement the "{1}" interface.
CNTR0113I: SfDRSControllerInstance {0} received event REPLICATION_UP.
CNTR0114I: SfDRSControllerInstance {0} received event REPLICATION_DOWN.
CNTR0115I: SfDRSControllerInstance {0} received event IS_CONGESTED.
CNTR0116I: SfDRSControllerInstance {0} received event NOT_CONGESTED.
CNTR0117I: Container-managed ejbStore() call will be bypassed on bean: "{0}" if it has not been modified in the current transaction.
CNTR0118I: Container pre- and post-method processing for all local and local home methods will be bypassed on bean: "{0}".
CNTR0119E: The user-provided class "{0}" may not implement the com.ibm.websphere.ejbcontainer.LightweightLocal interface. Reason code = {1}.
CNTR0120W: EJB java:comp/env context environment entry {0} of type Boolean, not set to a valid boolean value: {1}. Entry assigned a value of "false".
CNTR0121W: XML configuration error in ejb-jar.xml for jar: "{0}". The container-transaction element in error has trans-attribute element: "{1}".
CNTR0123W: XML configuration error in ejb-jar.xml for jar: "{0}". The method-permission element in error for EJB: "{1}".
CNTR0124W: XML configuration error in ejb-jar.xml for jar: "{0}". The exclude-list element in error for EJB: "{1}".
CNTR0125E: Unable to process injection information for class: {0}.
CNTR0126E: The {0} message-driven bean (MDB) class does not define a message listener interface.
CNTR0130E: When a simple Java Naming and Directory Interface (JNDI) binding name is specified for a bean or home, specific JNDI bindings cannot be specified. The {0} bean in The {1} module either must use a simple JNDI binding name or specific JNDI bindings, but not use both options.
CNTR0131E: The {0} bean in the {1} module does not have any configured productive interfaces.
CNTR0132E: The {0} session bean in the {1} module has an interface configured for a message listener or Web service endpoint.
CNTR0133E: The {0} entity bean in the {1} module has an interface configured for a business, message listener, or Web service endpoint.
CNTR0134E: The {0} message-driven bean in the {1} module has an interface configured for a component, business, Web service endpoint, or home.
CNTR0135E: The {0} message-driven bean (MDB) does not have a corresponding binding in the binding file.
CNTR0136E: The specific Java Naming and Directory Interface (JNDI) binding name provided for a local home or bean does not begin with ejblocal:. The {2} local binding name that is specified for the home or {0} bean in the {1} module does not begin with ejblocal:.
CNTR0137E: The specific Java Naming and Directory Interface (JNDI) binding name that is provided for a remote home or bean begins with ejblocal:. The {2} remote binding name that is specified for the home or {0} bean in the {1} module cannot begin with ejblocal:.
CNTR0138E: The {0} bean or home in the {1} module contains a blank string value for the Java Naming and Directory Interface (JNDI) binding name.
CNTR0139E: The {0} bean in the {1} module has multiple Java Naming and Directory Interface (JNDI) binding names specified for the {2} business interface.
CNTR0140E: The {0} bean in the {1} module has specified the {2} business interface, which does not exist for a business interface Java Naming and Directory Interface (JNDI) binding.
CNTR0141E: The {0} bean in the {1} module has specified a home Java Naming and Directory Interface (JNDI) binding. The binding does not have a matching home interface class.
CNTR0142W: The Enterprise JavaBeans (EJB) binding with the {0} Java Naming and Directory Interface (JNDI) name does not contain an enterprise bean stanza.
CNTR0143E: The Enterprise JavaBeans (EJB) binding with the {0} Java Naming and Directory Interface (JNDI) name does not contain a jca-adapter stanza.
CNTR0144E: The Enterprise JavaBeans (EJB) binding with the {0} Java Naming and Directory Interface (JNDI) name has a jca-adapter stanza that does not contain an activation-spec-binding-name value.
CNTR0145E: The Enterprise JavaBeans (EJB) binding with the {0} Java Naming and Directory Interface (JNDI) name has a jca-adapter stanza that does not contain a destination-binding-name value.
CNTR0146E: The {0} bindings file contained in the {1} module has a configuration error at line number: {2}, column number: {3}.
CNTR0147E: The {0} bindings file contained in the {1} module has a configuration error.
CNTR0148E: The {0} Container Managed Persistence (CMP) entity bean is configured to use a CMP Connection Factory with a {1} Java Naming and Directory Interface (JNDI). This Connection Factory resource is not configured.
CNTR0149E: The start up process for the {0} enterprise bean in the {1} module failed with the following exception: {2}
CNTR0150E: The {0} annotation and the {1} annotation cannot both be configured on the {2} method of the {3} enterprise bean class.
CNTR0151E: The {0} role is specified multiple times in the @RolesAllowed annotation on the {1} method of the {2} enterprise bean class.
CNTR0152E: The class-level {0} and {1} annotations cannot be configured on the {2} enterprise bean class at the same time.
CNTR0153E: The {0} role is specified multiple times in the class level @RolesAllowed annotation on the {1} enterprise bean class.
CNTR0154E: Another component is attempting to reference the {0} enterprise bean in the {1} module. This bean does not support an implementation of the {2} interface, which the other component is attempting to reference.
CNTR0155E: Another component is attempting to reference the {0} enterprise bean in the {1} module. This bean supports both local and remote implementations of the {2} interface, which the other component is attempting to reference.
CNTR0156E: The {0} stateful session bean in the {1} module is configured for failover. However, the session bean is also configured to use extended-scope persistence context. These configuration settings conflict.
CNTR0157E: The {0} enterprise bean in the {1} module does not implement the {2} method. This method is part of the bean interface.
CNTR0158E: The {0} session bean in the {1} module has the {2} method configured as a timeout method. This method must have a single parameter of the javax.ejb.Timer type, or take zero parameters.
CNTR0159E: The {0} module has a configuration error in the inheritance relationship that is specified between the {1} parent bean and the {2} child bean.
CNTR0160E: The {0} enterprise bean in the {1} module is configured as timer bean. However, the bean does not implement the following required timeout method: ejbTimeout
CNTR0161E: The {0} enterprise bean in the {1} module has specified the @Timeout annotation on more than one method.
CNTR0162E: The {0} enterprise bean in the {1} module has specified the following timeout method: {2} This method is not implemented by the bean.
CNTR0163E: The {0} enterprise bean in the {1} module has specified the {2} timeout method on a timeout-method tag in XML. Also, the bean has specified the {3} timeout method on an @Timeout annotation in the Java source code. This configuration conflicts.
CNTR0164E: The {0} enterprise bean in the {1} module implements a {2} timeout method, which creates an application exception..
CNTR0165E: The {0} enterprise bean in the {1} module implements a {2} timeout method, which has a non-void return type.
CNTR0166E: The {0} enterprise bean in the {1} module implements a {2} timeout method, which is declared as static or final.
CNTR0167I: The server is binding the {0} interface of the {1} enterprise bean in the {2} module of the {3} application. The binding location is: {4}
CNTR0168W: The {0} enterprise bean in the {1} module within the {2} application is configured with a simple binding name, but has multiple local or remote interfaces. The naming locations that are used to bind these interfaces will differ from the simple binding name that is specified.
CNTR0169E: The {0} enterprise bean, which is specified in the {1} binding within the {2} module, does not exist.
CNTR0170E: The {0} enterprise bean in the {1} module does not have a defined bean type.
CNTR0171E: The {0} enterprise bean in the {1} module of the {2} application, and the {3} enterprise bean in the {4} module of the {5} application, both have the following binding location: {5}
CNTR0172E: The {0} interface of the {1} bean in the {2} module of the {3} application cannot be bound to the {4} name location. The {5} interface of the {6} bean in the {7} module of the {8} application has already been bound to the {4} name location.
CNTR0173E: The {0} interface of the {1} bean in the {2} module of the {3} application cannot be bound to the {4} name location. The {5} interface of the same bean has already been bound to the {4} name location.
CNTR0174I: The {0} bean in the {1} module is an Enterprise Java Beans (EJB) version prior to 3.0, and has no home binding name specified. The following binding name has been manufactured for this bean: {2}.
CNTR0175W: The configured Activation Policy for the {0} bean in the {1} module of the {2} application has been changed from {3} to ONCE. A Stateful Session bean that references an extended persistence context must be configured with an Activation Policy of ONCE.
CNTR0176E: Web service Provider interface conflicts with the configured Web service endpoint interface {0} for the {1} bean in the {2} module of the {3} application.
CNTR0177E: Failure occurred attempting to create a Web service endpoint proxy for the {0} bean in the {1} module of the {2} application : {3}
CNTR0178E: Configured Web service endpoint method {0} is not implemented by the {1} bean in the {2} module of the {3} application.
CNTR0179W: Non-persistent timer maximum number of retries {0} was reached.
CNTR0183E: The timer manager used by the EJB timer service could not be obtained. {0}
CNTR0184W: The ibm-ejb-jar-bnd.xml file contained in the {0} module has more than one {1} stanza with name attribute of {2} for the {3} interceptor class. Only the last {1} stanza is used. The interceptor class is using the java:comp namespace for the {4} enterprise bean.
CNTR0185E: The {0} bean in the {1} module of the {2} application has one or more asynchronous methods configured, but is not a session bean. Asynchronous methods can only be configured on session beans.
CNTR0187E: The {0} method on the {1} bean in the {2} module of the {3} application has a {4} transaction attributed configured. Asynchronous methods only support transaction attributes of type TX_REQUIRED, TX_REQUIRES_NEW, or TX_NOT_SUPPORTED.
CNTR0188E: An unexpected exception was caught. The exception is: {0}
CNTR0189E: The {0} bean class can not be designated as a Startup bean using Java annotations or within the XML deployment descriptor.
CNTR0190E: The {0} startup singleton session bean in the {1} module failed initialization with exception: {2}
CNTR0191E: The option to create a unique timer manager for non-persistent timers was chosen, but the number of timer threads has an unsupported value: {0}
CNTR0192E: The access timeout value {0} is not valid for the enterprise bean {1} method of the {2} class. The value must be -1 or greater and less than java.lang.Long.MAX_VALUE (9223372036854775807).
CNTR0193E: The value, {0}, that is specified for the concurrency management type of the {1} enterprise bean class must be either Bean or Container.
CNTR0194E: The value {0} that is specified in the ejb-jar.xml file for concurrency management type is not the same as the @ConcurrencyManagement annotation value {1} on the {2} enterprise bean class.
CNTR0195E: The work manager associated with the {0} scheduler used by the EJB timer service could not be obtained.
CNTR0196E: The conversion of access timeout value {0} from {1} time unit to milli-seconds time unit resulted in an overflow.
CNTR0197E: The {0} non-singleton enterprise bean has dependency metadata.
CNTR0198E: The {0} singleton session bean in the {1} module depends on {2}, which does not exist.
CNTR0199E: The {0} singleton session bean in the {1} module depends on {2}, which does not uniquely specify an enterprise bean.
CNTR0200E: The {0} singleton session bean in the {1} module depends on the {2} enterprise bean in the {3} module, but the target is not a singleton session bean.
CNTR0201E: The {0} singleton session bean in the {1} module directly or indirectly depends on itself.
CNTR0202E: The {0} asynchronous method on the {1} bean has a return type of void and has the {2} application exception(s) on its throws clause.
CNTR0203E: The ejb-jar.xml declares an asynchronous method for the {0} session bean, but did not declare a method-name.
CNTR0204E: The ejb-jar.xml file declares a parameter on a wildcard asynchronous method element for the {0} session bean. Parameters may not be specified on wildcards.
CNTR0205E: The {0} bean in the ejb-jar.xml contains an async-method element with an invalid method-intf value. This value may only be "Local" or "Remote". "{1}" was specified.
CNTR0206E: The {0} asynchronous method on the {1} bean has a return type of {2}. A return type of void or future<V> is required for asynchronous methods.
CNTR0207E: The {0} stateful session bean in the {1} module has an automatic timer.
CNTR0208E: The {0} enterprise bean in the {1} module has automatic timer metadata in the deployment descriptor for the {2} method, but the method parameter types are not valid for a timeout callback method.
CNTR0209E: The {0} enterprise bean in the {1} module has the {2} timeout callback method that does not have the required method signature.
CNTR0210E: The {0} enterprise bean in the {1} module has automatic timer metadata in the deployment descriptor for the {2} method, but no timeout callback method with that name was found.
CNTR0211E: The {0} enterprise bean in the {1} module has automatic metadata for the {2} method, but the {3} schedule field has a value that is not valid.
CNTR0212E: The {0} enterprise bean in the {1} module has automatic timer metadata for the {2} method, but the {3} schedule field has a value that is out of range for that field.
CNTR0213E: The {0} enterprise bean in the {1} module has automatic timer metadata for the {2} method, but the {3} schedule field has an range bound that is not valid.
CNTR0214E: The {0} enterprise bean in the {1} module has automatic timer metadata for the {2} method, but the {3} schedule field has an interval value that is not valid.
CNTR0215E: The {0} enterprise bean in the {1} module has automatic timer metadata for the {2} method, but the {3} schedule field has a list value that is not valid.
CNTR0216E: The {0} enterprise bean in the {1} module has automatic timer metadata for the {2} method, but the {3} schedule field uses an increment.
CNTR0217E: The {0} enterprise bean in the {1} module has automatic timer metadata for the {2} method, but the {3} schedule field has an ordinal keyword without a day of the week.
CNTR0218E: An error occurred while creating persistent automatic timers for the {0} module: {1}
CNTR0219I: The server created {0} persistent automatic timer or timers and {1} non-persistent automatic timer or timers for the {2} module.
CNTR0220E: CNTR0220E: The {0} interceptor class exists multiple times in the list of interceptors for the {1} enterprise bean. The following is the interceptor list for this bean: {2}
CNTR0221E: The {0} method-level interceptor for the {1} method of the {2} enterprise bean duplicates a name that is in the following class-level interceptor list: {3}
CNTR0222E: The {0} method-level interceptor for the {1} method of the {2} enterprise bean duplicates a name that is in the following default interceptor list: {3}
CNTR0223E: Only one method in the {0} class is allowed to be a {1} interceptor method.
CNTR0224E: The {0} enterprise bean is missing a method-name tag on the exclude-class-interceptors element in the interceptor-binding element of the deployment descriptor.
CNTR0225E: The exclude-default-interceptors element in the deployment descriptor is not valid for a style 1 interceptor-binding element.
CNTR0226E: The {2} enterprise bean specifies a style 4 interceptor-binding element for the {0} method with the {1} signature. A style 4 interceptor-binding cannot be used when a style 3 binding is also used for the same method of the same enterprise bean.
CNTR0227E: The {0} enterprise bean has an interceptor-order element which specifies the following interceptor-order list: {1}. This list is not a total ordering of the class-level interceptors for this bean. It is missing the following interceptor names: {2}
CNTR0228E: The {0} enterprise bean specifies method-level interceptors for the {1} method with the following interceptor-order list: {2}. This list is not a total ordering of the method-level interceptors for this bean. The list is missing the following interceptor names: {3}.
CNTR0229E: The {0} interceptor method must not be declared as final or static.
CNTR0230E: The {0} method does not have the required method signature for a {1} method.
CNTR0231E: The {0} method signature is not valid as a {1} method of an enterprise bean class.
CNTR0232E: The {0} method does not have the required method signature for a {1} method of a interceptor class.
CNTR0233E: The {1} enterprise bean specifies an @Remove annotation on the {0} method. This annotation is not valid because this method is not a business method of this bean.
CNTR0234E: An initialization method for a stateful session bean can be an ejbCreate&lt;METHOD&gt; method only when the bean conforms to the Enterprise JavaBeans (EJB) 2.1 or earlier specification levels. Therefore, it cannot be applied to the {0} method of the {1} enterprise bean.
CNTR0235E: The name of the adapted create&lt;METHOD&gt; method must be specified for either the {0} method or the {1} method of the {2} enterprise bean.
CNTR0236E: The {1} enterprise bean has an init-method element, which specifies the {0} method. This method is not a public method of this bean.
CNTR0237E: The user-provided enterprise bean level 3.0 {0} interceptor class cannot be found or loaded.
CNTR0238E: The {2} interceptor class specifies the {1} method, which is not an {0} method of this class.
CNTR0239E: The method-name element is not valid for a style 1 interceptor-binding element.
CNTR0240E: The {1} enterprise bean specifies the {0} class-level interceptor, which duplicates a name in the following default interceptors list: {2}
CNTR0241E: Because the {0} enterprise bean implements the javax.ejb.SessionBean interface, the {1} method must be a {2} method and not a {3} method.
CNTR0242E: Because the {0} enterprise bean implements the javax.ejb.SessionBean interface, the {1} method must be a {2} method and not a {3} method.
CNTR0243E: Because the {0} enterprise bean implements the javax.ejb.MessageDriven interface, the {1} method must be a {2} method and not a {3} method.
CNTR0244E: The {0} method name is not found in one of the business interfaces of the {1} enterprise bean. A style {2} interceptor-binding element requires the method to be a business method of the enterprise bean.
CNTR0245E: The {0} module of the {1} application has more than one style 1 interceptor-binding in the deployment descriptor. Only one style 1 interceptor-binding is allowed.
CNTR0246E: The {0} module of the {1} application has more than one style 2 interceptor-binding in the deployment descriptor. Only one style 2 interceptor-binding is allowed.
CNTR0247E: More than one style 3 interceptor-binding element is provided in the deployment descriptor for the {0} method of the {1} enterprise bean.
CNTR0248E: More than one style 4 interceptor-binding element is provided in the deployment descriptor for the {0} method with the {1} signature of the {2} enterprise bean.
CNTR0251W: Unable to remove automatic Enterprise Java Bean timers from the scheduler for the {0} application, running on the {1} server. To remove the timers manually, use wsadmin to execute this command: $AdminTask removeAutomaticEJBTimers "-appName {0} -serverName {1} -nodeName {2} "
CNTR0252W: Unable to remove automatic Enterprise Java Bean timers from the scheduler for the {0} application and {1} module, running on the {2} server. To remove the timers manually, use wsadmin to execute this command: $AdminTask removeAutomaticEJBTimers "-appName {0} -moduleName {1} -serverName {2} -nodeName {3} "
CNTR0253W: Unable to find the RemoveBinaries task. As a result, if automatically created EJB timers exist, they are not removed.
CNTR0254W: The application or module that was updated or removed contained automatically created Enterprise Java Bean timers. However, because processing ran in a local mode, the timers were not removed. Use the removeAutomaticEJBTimers command to remove them manually.
CNTR0301E: The {0} enterprise bean in the {1} module of the {2} application has an automatic timer for the {3} method, but an incompatible change was made to the application since the server created the timer.
CNTR0302W: The work manager configuration that is used for asynchronous methods does not comply with the Enterprise JavaBeans (EJB) specification.
CNTR0303W: The work manager configuration that is used for the EJB timer service does not comply with the Enterprise JavaBeans (EJB) specification.
CNTR0304W: The {0} enterprise bean in the {1} module of the {2} application contains the @StatefulTimeout annotation. The StatefulTimeout annotation is only valid on stateful session beans. The Enterprise JavaBean (EJB) container will ignore the annotation on this bean.
CNTR0305W: The {0} business interface contains an @Asynchronous annotation. These annotations are not valid on interface types, and the Enterprise JavaBean (EJB) container ignores them.
CNTR0306W: The {0} business interface contains the @StatefulTimeout annotation. This annotation is not valid on interface types, and the Enterprise JavaBean (EJB) container ignores it.
CNTR0307W: The {0} Enterprise JavaBean (EJB) in the {1} module of the {2} application has a timeout value specified in the StatefulTimeout annotation or stateful-timeout deployment descriptor element which is not a valid integer: {3}. The default value of {4} milliseconds will be used instead.
CNTR0308W: The {0} Enterprise JavaBean (EJB) in the {1} module of the {2} application contains the stateful-timeout deployment descriptor element, but is missing the required timeout element. The Enterprise JavaBean (EJB) container will compute a default value.
CNTR0309E: The {0} Enterprise JavaBean (EJB) in the {1} module of the {2} application contains a stateful timeout value {3} with time unit {4}. The conversion to milliseconds resulted in an overflow.
CNTR0310W: The {0} Enterprise JavaBean (EJB) in the {1} module of the {2} application contains the stateful-timeout deployment descriptor element. stateful-timeout applies only to stateful session beans. The EJB container will ignore the stateful-timeout on this bean.
CNTR0311E: The {0} Enterprise JavaBean (EJB) in the {1} module of the {2} application has a timeout value specified in the StatefulTimeout annotation which is negative: {3}.
CNTR0312E: The {0} Enterprise JavaBean (EJB) in the {1} module of the {2} application has a timeout value specified in the stateful-timeout deployment descriptor element which is negative: {3}.
CNTR0313W: The system property {0} has a timeout value specified which is not a valid integer value: {1}. The default value of {2} minutes will be used instead.
CNTR0314E: The {0} enterprise bean in the {1} module has timer metadata in the deployment descriptor that targets the {2} method, but does not indicate whether the targeted method accepts zero or one parameters. Both a zero parameter and a one parameter version of the {2} method were found in the class hierarchy of the bean.
CNTR0315E: The {0} stateful session bean in the {1} module in the {2} application did not declare a dependency on the {3} persistence reference.
CNTR0316E: A resource reference conflict was detected. {0}
CNTR0317E: The {0} bean is packaged inside a WAR module and has been defined as a JAX-RPC endpoint using the ejb-jar.xml descriptor. The {1} interface is declared as the JAX-RPC endpoint. However, beans packaged in a WAR module are not supported as JAX-RPC endpoints. Package the bean in an EJBJAR module, or remove the service endpoint interface from the deployment descriptor.
CNTR0318E: No ejb-class element was specified for the {0} bean, in the {1} module, of the {2} application.
CNTR0319E: The {0} bean is a startup bean, and is packaged inside of a Web archive (WAR) module, which is not allowed. Startup beans must be packaged inside of a stand-alone Enterprise JavaBean (EJB) module. Start-up behavior for an EJB component packaged inside of a WAR module is obtained by using a singleton session bean that is marked with the @Startup annotation, or the corresponding XML element.
CNTR0320E: The {0} singleton session bean in the {1} module has an interface configured for a component view.
CNTR0321E: The {0} return type for the {1} method of the {2} enterprise bean does not match the {3} return type for the corresponding method on the {4} interface.
CNTR0322W: The {0} return type for the {1} method of the {2} enterprise bean is not compatible with the {3} return type for the corresponding method on the {4} interface.
CNTR0323E: The {0} bean in the {1} module of the {2} application implements the javax.ejb.SessionSynchronization interface and also configures a session synchronization method in the ejb-jar.xml or with an annotation. The configured session synchronization method is {3}.
CNTR0324E: The {0} method configured in the ejb-jar.xml file does not have the required method signature for a {1} session synchronization method for the {2} bean in the {3} module of the {4} application.
CNTR0325E: The configured {0} session synchronization method {1} is not implemented by the {2} bean in the {3} module of the {4} application.
CNTR0326E: Multiple {0} session synchronization methods have been configured for the {1} bean. The configured session synchronization methods are : {2} and {3}
CNTR0327E: The {0} method does not have the required method signature for a {1} session synchronization method.
CNTR5001E: The {0} bean is configured with the {1} remote component interface, but a remote home interface has not been provided.
CNTR5002E: The {0} bean is configured with the {1} local component interface, but a local home interface has not been provided.
CNTR5003E: The {1} bean class for the {0} bean is not defined as public.
CNTR5004E: The {1} bean class for the {0} bean is defined as final.
CNTR5005E: The {1} bean class for the {0} bean is defined as abstract.
CNTR5006E: The {1} bean class for the {0} bean is not defined as a top level class.
CNTR5007E: The {1} bean class for the {0} bean does not have a public constructor that does not take parameters.
CNTR5008E: The {1} bean class for the {0} bean has defined the finalize method.
CNTR5009E: The {1} bean class for the {0} entity bean does not implement the javax.ejb.EntityBean class.
CNTR5010E: The name of the {2} business method of the {1} interface for the {0} bean must not start with ejb.
CNTR5011E: The {1} class has been configured as a business or component interface for the {0} bean. However, the class is not an interface.
CNTR5012E: The {1} interface, which has been configured as a business interface for the {0} bean, must not extend the {2} interface.
CNTR5013E: The {1} interface, which has been configured as a local interface for the {0} bean, must not extend the javax.rmi.Remote interface.
CNTR5014E: The {1} interface, which has been configured as the local component interface for the {0} bean, must extend the javax.ejb.EJBLocalObject interface.
CNTR5015E: The {1} interface, which has been configured as the remote component interface for the {0} bean, must extend the javax.ejb.EJBObject interface.
CNTR5016E: The {1} interface, which has been configured as the local home interface for the {0} bean, must extend the javax.ejb.EJBLocalHome interface.
CNTR5017E: The {1} interface, which has been configured as the remote home interface for the {0} bean, must extend the javax.ejb.EJBHome interface.
CNTR5018E: The {2} method of the {1} interface, which has been configured as a home interface for the {0} bean, does not return the component interface.
CNTR5019E: The {1} interface, which has been configured as a home interface for the {0} bean, does not define a create method.
CNTR5020E: The {2} method of the {1} interface, which has been configured as a home interface for the {0} bean, does not return the {3} component interface.
CNTR5021E: The {2} method of the {1} interface, which has been configured as a home interface for the {0} bean, does not define the javax.ejb.CreateException exception on the throws clause.
CNTR5022E: The {1} home interface for the {0} bean has too many methods. The {2} method is not allowed.
CNTR5023E: The {1} home interface for the {0} bean has a method that does not start with the create string. The {2} method is not allowed.
CNTR5024E: The {1} home interface for the {0} bean has a method that starts with the remove string. The {2} method is not allowed.
CNTR5025E: The {2} method of the {1} home interface for the {0} bean does not define a corresponding init or ejbCreate method on the {3} class.
CNTR5026E: The {2} method of the {1} home interface for the {0} entity bean does not define a corresponding ejbCreate method for the {3} class.
CNTR5027E: The {2} method with the {3} return type on the {1} class for the {0} entity bean must return the {4} primary key class.
CNTR5028E: The {2} method of the {1} home interface for the {0} entity bean does not define a corresponding ejbPostCreate method on the {3} class.
CNTR5029E: The {2} method with the {3} return type on the {1} class for the {0} entity bean must return void.
CNTR5030E: The {2} method of the {1} home interface for the {0} entity bean does not define a corresponding ejbFind method on the {3} class.
CNTR5031E: The {2} method with the {3} return type on the {1} class for the {0} entity bean must return the {4} primary key class.
CNTR5032E: The {2} method with the {3} return type on the {1} class for the {0} entity bean must return the {4} primary key class, the java.util.Collection class, or the java.util.Enumeration class.
CNTR5033E: The {2} method of the {1} home interface for the {0} entity bean does not define a corresponding ejbHome method on the {3} class.
CNTR5034E: The {2} method with the {3} return type on the {1} class for the {0} entity bean must return the {4} type. This type must be the same type as the corresponding home interface method.
CNTR5035W: Multiple interfaces of the {0} bean define the same method signature, but with different exceptions on the throws clause. The following signature will be used for determining the application exceptions for the method : {3}
CNTR5100E: The {0} argument or return type of the {1} method on the {2} interface is not a valid type for Remote Method Invocation over the Internet Inter-ORB Protocol (RMI/IIOP).
CNTR5101W: The {0} method on the {1} interface should not define the java.rmi.RemoteException exception on the throws clause.
CNTR5102E: The {0} application exception that is defined on the {1} method of the {2} interface must not be defined as a subclass of the java.rmi.RemoteException exception.
CNTR5103E: The {0} application exception that is defined on the {1} method of the {2} interface must not be defined as a subclass of the java.lang.RuntimeException exception.
CNTR5104E: The {0} method on the {1} interface must be defined with the java.rmi.RemoteException exception on the throws clause.
CNTR5105E: The {0} interface is not a valid remote interface. The IDL name for the {1} method conflicts with the {2} method.
CNTR5106E: The {0} method on the {1} class must not be declared as final for the {2} bean.
CNTR5107E: The {0} application exception defined on the {1} method of the {2} class must be defined as a subclass of the java.lang.Exception class.
CNTR8990I: This message is an English-only Informational message: {0}.
CNTR8991W: This message is an English-only Warning message: {0}.
CNTR8992E: This message is an English-only Error message: {0}.
CNTR9100E: Exception {0}
CNTR9101E: Incompatible options: {0} {1}
CNTR9102E: Option {0} requires option {1}.
CNTR9103W: EJB timer {0} could not be found on server {1}.
CNTR9104W: EJB timer service {0} not available on server {1}.
CNTR9105E: Missing required filter.
CNTR9106E: Missing required server name.
CNTR9240I: The {0} Java archive (JAR) file is not an enterprise bean level 3.0 module.
CNTR9241I: The {0} Java archive (JAR) file has no level 3.0 enterprise beans with remote interfaces.
CNTR9250E: The first parameter must be a fully qualified class name, Java archive (JAR)file, Web archive (WAR)file, or enterprise archive (EAR) file.
CNTR9251E: Unable to read from the {0} file.
CNTR9252E: The {0} option was specified multiple times.
CNTR9253E: The {0} log file name parameter is not correct.
CNTR9254E: Unable to write to the {0} file.
CNTR9255E: The required log file name parameter is missing.
CNTR9256E: The {0} parameter is not recognized.
CNTR9257E: Too many input parameters were specified.
CNTR9258E: An unexpected exception was caught. The exception is: {0}
CNTR9259E: No component interface specified for the {0} home.
CNTR9260E: The {0} exception occured while setting up the user log file.
CNTR9261E: Unable to create temporary file in the {0} directory.
CNTR9262E: The {0} interface class could not be loaded. This can be caused by a spelling error, incorrect -cp option, failure to load parent class, or falure to load class on method parameter.
CNTR9263E: The {0} interface class could not be processed. The {1} method parameter class was not found.
CNTR9264E: The required class path name parameter was not specified.
CNTR9265E: The {0} input file was not found.
CNTR9266E: The createEJBStubs command could not rename the {0} file to the {1} file.
CNTR9267W: The createEJBStubs command could not delete the {0} file.
CNTR9268E: The {0} file name is not allowed for the -newfile option.
CNTR9269W: The {0} Enterprise JavaBeans (EJB) module does not have any enterprise beans configured.
CNTR9270E: The update file name parameter is not a Java archive (JAR), Web archive (WAR), or an enterprise archive (EAR) file type.
CNTR9271E: The {0} directory could not be deleted.
CNTR9272E: The {0} output file cannot be found.
CNTR9273E: The {0} directory could not be created.
CNTR9274E: The createEJBStubs command cannot create the {0} file.
CNTR9275E: The {0} output file already exists.
CNTR9276I: The {0} application has disabled the library directory. Java archive (JAR) and Web archive (WAR) files in the library directory will not be processed.
CNTR9277I: The {0} Java archive (JAR) or Web archive (WAR) file does not contain remote interface classes for a level 3.0 enterprise bean.
CNTR9278E: The input type of a fully qualified class name is not compatible with the {0} option.
CNTR9400I: The embeddable Enterprise JavaBeans (EJB) container is scanning for Enterprise JavaBeans (EJB) modules to start.
CNTR9401I: The embeddable Enterprise JavaBeans (EJB) container is initializing.
CNTR9402E: An error occurred while initializing the embeddable Enterprise JavaBeans (EJB) container {0}.
CNTR9403E: The embeddable enterprise bean container cannot start multiple modules with the same file name: {0} and {1}
CNTR9405I: The Enterprise JavaBeans (EJB) module, {0}, is starting.
CNTR9407W: There are no valid Enterprise JavaBeans (EJB) modules to start.
CNTR9408W: The Enterprise JavaBeans (EJB) module, {0} failed to stop. Exception: {1}
CNTR9409W: The embeddable Enterprise JavaBeans (EJB) container failed to stop. Exception: {0}
CNTR9410I: The embeddable Enterprise JavaBeans (EJB) container has closed.
CNTR9412E: An error occurred while shutting down the JNDI name space. Exception: {0}
CNTR9413E: Failed to read in the configuration file from {0}
CNTR9414E: Failed to bind data source into JNDI using the name, {0}. Exception: {1}
CNTR9415E: The embeddable Enterprise JavaBeans (EJB) container properties for the {0} data source do not contain the property, name.
CNTR9416E: The embeddable Enterprise JavaBeans (EJB) container properties for the {0} data source do not contain the property, className.
CNTR9417E: The embeddable Enterprise JavaBeans (EJB) container properties for the {0} data source contain a {1} ConnectionPool.MaxConnections value that is not a positive numeric value or zero.
CNTR9419E: The embeddable Enterprise JavaBeans (EJB) container failed to shutdown the JPA provider. Exception: {0}
CNTR9420E: The embeddable Enterprise JavaBeans (EJB) container properties for the {0} data source contain a {1} ConnectionPool value that is not valid.
CNTR9421E: The {0} property was assigned an incorrect value of {1}. This property indicates the local transaction containment (LTC) resolver setting, and must be either Application (default) or ContainerAtBoundary.
CNTR9422E: The {0} property was assigned an incorrect value of {1}. This property indicates the local transaction containment (LTC) unresolved action setting, and must be either Rollback (default) or Commit.


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ejs.container.container.dita
File name: com.ibm.ejs.container.container.html