Express (Distributed operating systems), v8.0 > Reference > Messages
CNTR
CNTR0001W: A Stateful SessionBean could not be passivated: {0} {1} {2}
Explanation The container was not able to passivate a stateful session bean. Action Check that passivation directory exists, the process has write permissions in that directory, and that there is enough disk space.
CNTR0002W: Failed to get the wrapper for a home.
Home: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0003W: A Stateful SessionBean could not be activated: {0} {1}
{2}
Explanation The container failed to activate a stateful session bean from storage. Action Take action based upon the exception message in message CNTR0003W.
CNTR0004E: An attempt to acquire a lock was interrupted.
Lock : {0}
Explanation A thread attempting to acquire an exclusive lock within the container was interrupted while waiting for the lock. Action More info at:
CNTR0005W: An enterprise bean could not be passivated: {0} {1} {2}
Explanation The container was unable to passivate an enterprise bean. Action Take action based upon the exception message in message CNTR0005W.
CNTR0006W: EJBObject "{0}" could not be connected to the ORB.
Explanation The container failed to connect a deserialized stub (reference) object on an attempt to activate a stateful bean. Action More info at:
CNTR0008W: A passivated Stateful SessionBean could not be removed: {0} {1} {2}
Explanation The container was unable to remove a passivated stateful session bean from storage. Action Take action based upon the exception message in message CNTR0008W.
CNTR0009W: An attempt to access bean "{0}" failed because it was not previously installed or problems occurred during its installation.
Explanation The Application Server made an attempt to access an enterprise bean that has not been installed in the container. Action Look for prior error messages that indicate that the bean installation has failed.
CNTR0010W: NumberFormatException occurred while converting <env-entry-name> {0} <env-entry-value> {1}: {2}
Explanation The container was unable to process an environment entry due to a NumberFormatException. Action Ensure that the value for the environment entry is a valid string representation for the specified type.
CNTR0011W: An invalid type was specified for a bean''s java:comp/env context environment entry: <env-entry-name> {0}
Explanation The container encountered a type for an environment entry that is not valid. Action Ensure that the environment entry type is one of : String, Integer, Boolean, Double, Byte, Short, Long or Float.
CNTR0012W: Collaborator {0} threw unexpected exception - proceeding with remaining collaborators.
Exception data:{1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0013W: Unable to map exception.
{0}
{1}
Explanation The container was unable to map exception to a valid CORBA exception. Action More info at:
CNTR0014W: StatefulBeanReaper thread was interrupted; terminating.
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0015W: An unexpected exception occurred during stateful bean cleanup.
Exception data:
{0}
{1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0016W: Passivated Stateful SessionBean "{0}" could not be removed due to exception: {1}
Explanation The container was unable to remove a passivated stateful session bean from the passivation store. Action Take action based upon the exception message in message CNTR0016W.
CNTR0017W: Security collaborator threw unexpected exception.
Exception data: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0018E: EJB threw an unexpected (non-declared) exception. Exception data: {0}
Explanation An exception, which is not declared on the EJB method signature, was created when the EJB container attempted to invoke an EJB method. Action Examine the stack trace to determine the origin of the exception. If the exception originates from customer-written code, correct the cause of the exception. If not, visit the IBM support Web site for information on problem determination.
CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "{1}". Exception data: {0}
Explanation An exception, which is not declared on the EJB method signature, was created when the EJB container attempted to invoke this EJB method. Action Examine the stack trace to determine the origin of the exception. If the exception originates from customer-written code, correct the cause of the exception. If not, visit the IBM support Web site for information on problem determination.
CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "{1}" on bean "{2}". Exception data: {0}
Explanation An exception, which is not declared on the EJB method signature, was created when the EJB container attempted to invoke this EJB method. Action Examine the stack trace to determine the origin of the exception. If the exception originates from customer-written code, correct the cause of the exception. If not, visit the IBM support Web site for information on problem determination.
CNTR0021E: EJB threw an unexpected (non-declared) exception while invoking a method on bean "{1}". Exception data: {0}
Explanation An exception, which is not declared on the EJB method signature, was created when the EJB container attempted to invoke this EJB method. Action Examine the stack trace to determine the origin of the exception. If the exception originates from customer-written code, correct the cause of the exception. If not, visit the IBM support Web site for information on problem determination.
CNTR0022E: Transaction coordinator not available.
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0023W: Directory "{0}" does not exist. The EJB Container will use the current directory for passivating beans.
Explanation The container failed to open the passivation directory. Action Ensure that the passivation directory exists.
CNTR0024W: Unable to open input stream: {0} {1} {2}
Explanation The EJB container encountered an IOException while attempting to read a file for a stateful session bean. Action See the message in the IOException to determine the action to take. Ensure that the proper file permissions are set for the file.
CNTR0025W: Unable to open output stream: {0} {1} {2}
Explanation The container encountered an IOException while attempting to write a file for a stateful session bean. Action See the message in the IOException to determine the action to take. Ensure that the proper file permissions are set for the file.
CNTR0026W: DataSource name for CMP bean "{0}" is null. Bean will be unavailable for use.
Explanation No Datasource has been specified for the entity bean. Action Specify a Datasource for the entity bean, or specify a default Datasource for the module.
CNTR0027W: Failed to commit connection:
{0}
Explanation An SQLException occurred when trying to commit a Datasource connection. Action See the vendor-specific documentation for the database product you are using. Typically a vendor-specific exception code will be displayed as part of the SQLException. This exception code can be used, in combination with the vendor-specific documentation, to determine the cause of the exception.
CNTR0028W: Failed to close connection:
{0}
Explanation An SQLException occurred when trying to close a Datasource connection. Action See the vendor-specific documentation for the database product you are using. Typically a vendor-specific exception code will be displayed as part of the SQLException. This exception code can be used, in combination with the vendor-specific documentation, to determine the cause of the exception.
CNTR0031W: Error starting CMP bean {0}:
{1}
Explanation An entity bean might have been bound to a Datasource using a Datasource name that is not valid or is not correct. If the Datasource name is correct, the Datasource might not be configured correctly. Action If the CNTR0026W message precedes this message, provide the name of the Datasource. If CNTR0026W did not precede this message, check the datasource name that appears in the CNTR0032W message that follows this message. If a 'name not found' exception occurred, the Datasource name is most likely not correct. If the correct Datasource name is provided, then check the Datasource configuration. For example, you might have specified a database name, a user ID, or a password in the datasource configuration that is not correct.
CNTR0032W: Error creating CMP persister using datasource: {0}
Explanation This message immediately follows the CNTR0031W message and provides the Datasource name used when starting the entity bean. Action Take the action described for the message CNTR0031W.
CNTR0033E: EJB container ignoring caught unexpected exception: {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0034I: ContainerEJBException.getExceptionChain is returning an incomplete list of exceptions.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0035E: EJB container caught {0} and is throwing {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0036E: EJB container does not support using the bean instance for finder methods on EJB 1.x container managed persistence and is throwing {0}
Explanation A bean that is configured for enterprise Java bean (EJB) V1.x container managed persistence has attempted to invoke methods on a bean instance for the processing of a finder method. Action Redeploy the bean and attempt the operation again.
CNTR0037E: Prepared statement does not map to connection.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
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.
Explanation A transaction was started with the TX_NOT_SUPPORTED, TX_NEVER, or the TX_SUPPORTS transaction attribute. The transaction updated a container managed persistence (CMP) entity bean, and the transaction is storing the update to the persistent store. If a concurrent transaction uses the CMP entity bean with the same primary key value, the updates of one transaction might overlay the updates of the other transaction. Action The application must ensure that concurrent transactions never update a CMP entity bean with the same primary key value. If that cannot be done, then whichever bean begins the transaction must use a transaction attribute other than TX_NEVER, TX_NOT_SUPPORTED, or TX_SUPPORTS to ensure that data consistency is maintained.
CNTR0039E: EJB container caught {0} and is rethrowing the caught exception.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0040E: Finder failure as a result of exception {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0041W: Finder result collection exceeded limit. Only the first Integer.MAX_VALUE elements are processed.
Explanation The finder resulted in a collection that contains more than 2147483647 entity beans. Action Change the finder so that it does not result in a collection of entity beans that is more than 2147483647.
CNTR0043E: Bean "{0}" is attempting to use an invalid combination of ActivationPolicy and LoadPolicy on a work load managed server.
Explanation The user has specified 'Commit Option A' on an enterprise bean that is contained within a server that is work load managed. This configuration combination is not supported. Action Change the enterprise bean to use a different Commit Option, or change the server to not be work load managed.
CNTR0044W: Bean "{0}" is attempting to use an invalid combination of Activation Policy: Transaction and Load Policy : Activation. Defaulting Load Policy to : Transaction.
Explanation The activation policy specified for the enterprise bean is not supported. Option C, which is the default action taken, might not be the desired result. The combination of the Activation Policy and the Load Policy is the method in which the Application Server implements commit options A, B, and C in the EJB specification. Action Redeploy the enterprise bean using a combination of valid settings to eliminate this message.
CNTR0045W: Unable to convert remote object to stub. Possible reason="{0}".
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0046E: Bean "{0}" did not specify a connection factory binding.
Explanation Neither the bean specific nor the default connection factory binding is specified for the bean. Action Specify a binding for the connection factory when installing the bean.
CNTR0047E: Bean is attempting to use interface or method "{0}" in a situation prohibited by the EJB specification.
Explanation The EJB Specification does not allow the method for one of the following reasons: - The getRollbackOnly and setRollbackOnly methods of the MessageDriven-Context interface should be used only in the message-driven bean methods that run in the context of a transaction. # - Invoking the getCallerPrincipal and isCallerInRole methods is not allowed in the message-driven bean methods because the Container does not have a client security context. # - Invoking the getRollbackOnly and setRollbackOnly methods is not allowed in the message-driven bean methods for which the Container does not have a meaningful transaction context, and for all message-driven beans with bean-managed transaction demarcation. # - The UserTransaction interface is not available to message-driven beans with container- managed transaction demarcation. # - Invoking getEJBHome or getEJBLocalHome is not allowed in message-driven bean methods because there are no EJBHome or EJBLocalHome objects for message-driven beans. # Action Do not invoke the method in this environment.
CNTR0048W: Bean''s finder method "{0}" erroneously specifies a finder collection timeout scope of zero.
Explanation The finder method has a finder collection timeout scope specified, but the value is set to zero. Action Provide a value that is not zero, if a finder collection timeout scope is desired.
CNTR0049E: Bean is attempting to use an invalid combination of Commit Option A and Optimistic Concurrency.
Explanation The user has specified Commit Option A and Optimistic Concurrency Control on an enterprise bean. The Application Server does not support both Commit Option A and Optimistic Concurrency Control on an enterprise bean. Action Change the enterprise bean to use either Commit Option A or Optimistic Concurrency Control, but not both.
CNTR0050E: Protocol error occurred in container transaction.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0051E: Transaction has timed out due to no client activity for greater than {1} seconds. Transaction ID: {0}
Explanation The client has been inactive longer than the inactivity timeout value. Action This can be a normal occurrence if client goes away and leaves a transaction active. If client is still active, have an administrator determine whether to change the Client or the Transaction Inactivity Timeout value.
CNTR0052W: LRU thread was interrupted. Terminating. {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0053W: Caught an exception during LRU sweep {0} {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0054W: Exception thrown by discard strategy {0} {1}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0055W: A Throwable exception was caught while attempting to construct <env-entry-name> {0} <env-entry-value> {1}
{2}
Explanation The container caught a Throwable when the container was trying to create a java:comp/env entry. Action Take action based upon the exception message in message CNTR0055W.
CNTR0056W: Failed to get the wrapper for a bean. Bean:
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0057W: Minimum pool size specified for bean {0} not a valid integer: {1}. Default used instead.
Explanation Only a positive integer can be specified for the minimum pool size. The default value will be used. Action Change the value for the minimum pool size to a positive integer.
CNTR0058W: Maximum pool size specified for bean {0} not a valid integer: {1}. Default used instead.
Explanation Only a positive integer can be specified for the maximum pool size. The default value will be used. Action Change the value of the maximum pool size to a positive integer.
CNTR0059W: Minimum pool size specified for bean {0} is greater than maximum pool size specified: ({1},{2}) Defaults used instead.
Explanation The maximum pool size must be greater than or equal to the minimum size. The default values will be used for the minimum pool size and the maximum pool size. Action Change the maximum pool size to be a value that is greater than or equal to the minimum pool size.
CNTR0060I: (Min,Max) pool size is ({0},{1}) for bean {2}
Explanation These are the minimum pool size and maximum pool size values that will be used for this bean type. Action There is no user action required.
CNTR0061I: Read-only attribute on findByPrimaryKey method overridden to true for bean: <All>
Explanation The findByPrimaryKey read-only attribute has been specified to be overridden to true on all entity beans. Action There is no user action required.
CNTR0062W: An equals sign was not found in the pool size specification string {0}
Explanation The format of a pool size specification is: bean_name=min,max . An equals sign must be present between the bean name and the minimum value and the maximum value. Action Ensure that an equals sign is present between the bean name and the minimum value and the maximum value.
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.
Explanation There might be a deployment descriptor with syntax that is not valid. Action Verify that the binding information in the deployment descriptor for the enterprise Java bean (EJB) is correct.
CNTR0064E: A bean instance of type "{0}" with an activity session based activation policy attempted to become involved with multiple concurrent transactions.
Explanation An enterprise Java bean (EJB) that is activated within an activity session should only participate in serial transactions. Having transaction attributes that vary, like REQUIRES for one method and REQUIRES_NEW or NOT_SUPPORTED for another, can cause this error. Action Review the transaction attributes that are assigned to the EJB methods, and verify that the sequence of the method calls do not result in multiple concurrent transactions for the same bean within an activity session.
CNTR0065E: CMP bean "{0}" attempted to use an unsupported Local Transaction resolution control value.
Explanation Only ContainerAtBoundary resolution control is supported for local transactions with container managed persistence (CMP) beans. Action Using an assembly tool, change "Resolution Control" to "ContainerAtBoundary" within the IBM Extensions tab for the CMP bean, and restart the server.
CNTR0066E: Bean "{0}" attempted to use an invalid Local Transaction boundary value of "activity session".
Explanation The local transaction boundary of "activity session" is not valid for message-driven beans. Action Change the local transaction boundary from "activity session" to "bean method", and restart the application server.
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.
Explanation The enterprise Java bean (EJB) specification states that a session bean or the home of a session bean with "Bean Managed Transactions" must not declare transaction attributes for the method. The attributes for the Container Managed method-level transaction have no meaning, because the session bean will use Bean Managed Transactions. Action Remove the transaction attributes for the methods of this bean or the bean home.
CNTR0068W: Bean "{0}" or its home attempted to use an invalid combination of Bean Managed Activity Sessions and method-level Activity Session attributes.
Explanation An enterprise Java bean (EJB) or its home with "Bean Managed Transactions" should not declare "Container Managed Activity Session" attributes for its methods. Action Remove the "Container Managed Activity Session" attributes for the methods of this EJB or its home.
CNTR0069E: Bean "{0}" in an EJB 1.1 module attempted to use an invalid "Activate at" policy of "Activity Session".
Explanation Activity Sessions are not supported for EJB V1.1 modules. Action Select "Once" or "Transaction" for the "Activate At" policy.
CNTR0070E: Bean "{0}" in an EJB 1.1 module attempted to use an invalid Local Transactions Boundary of "Activity Session".
Explanation Activity Sessions are not supported on EJB V1.1 modules. Action Select "Bean method" for Local Transactions Boundary.
CNTR0071E: Bean "{0}" in an EJB 1.1 module attempted to use an invalid Local Transactions Resolution control of "ContainerAtBoundary".
Explanation Local Transactions Resolution control, "ContainerAtBoundary", is not supported for EJB V1.1 modules. Action Select "Application" for the Local Transactions Resolution control.
CNTR0072E: Bean "{0}" attempted to use an invalid "Activate at" policy with a container managed Activity Session.
Explanation Beans that are configured to use an Activity Session that is container-managed must use an "Activate at" policy of "Activity Session" or must use a "Load at" policy of "Interval", "Daily", or "Weekly". Action Ensure that an "Activate at" policy of "Activity Session" or a "Load at" policy of "Interval", "Daily", or "Weekly" is used when using an Activity Session that is container-managed.
CNTR0073E: Bean "{0}" attempted to use an invalid Local Transactions Resolution control.
Explanation The Local Transactions Resolution control must be ContainerAtBoundary for a container-managed transaction or a container-managed Activity Session. Action Set the Local Transactions Resolution control to "ContainerAtBoundary".
CNTR0074E: Unexpected method call occurred in {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0075E: The user-provided class "{0}" needed by the EnterpriseBean could not be found or loaded.
Explanation One or more of the implementation, home interface, remote interface, local interface, or other similar class for the bean could not be found or could not be loaded. Action Ensure that the implementation class, home interface, remote interface, and other classes for the bean are installed and configured correctly.
CNTR0076W: A reference to an ResourceRef could not be found in the deployment descriptor for the WebApp or EnterpriseBean with the display name {0}.
Explanation The Java Enterprise Edition (Java EE) component might have specified binding information that is not valid. Action Verify the binding information in the deployment descriptor for the Java EE component is correct.
CNTR0077W: A reference to an ResourceEnvRef could not be found in the deployment descriptor for the WebApp or EnterpriseBean with the display name {0}.
Explanation The Java Enterprise Edition (Java EE) component might have specified binding information that is not valid. Action Verify that the binding information in the deployment descriptor for the Java EE component is correct.
CNTR0078I: Custom Finder access intent support enabled for bean {0}
Explanation The user has specified that Custom Finders access intent must be honored. If the method has an Update access intent, the Access Intent will be honored. Action We can disable the processing of access intent for custom finders by using the Java Virtual Machine (JVM) and the properties at the bean level, or you can set the access intent of the method to Read-Only.
CNTR0080E: EJB timer service is not available for EJB implementing the javax.ejb.TimedObject interface: {0}.
Explanation The enterprise Java bean (EJB) implementation requires the EJB timer service, which has been disabled or did not start. Action See the previous messages to determine why the EJB timer service did not start, and correct the problem or enable the EJB timer service.
CNTR0081E: setTranEnlistmentNotNeeded called with an unrecognized reason code of {0}.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0082E: Cannot enlist XAResource since recovery ID for resource adapter {0} for MDB {1} is not known.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0083E: Creation of a message endpoint failed:
{0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0084E: Method {0} of MDB {1} is deployed with an incorrect transaction attribute.
Explanation A method of a message-driven bean (MDB) is required to be deployed with a transaction attribute of "requires", "not supported", or "bean managed". Action Redeploy the application using "requires", "not supported", or "bean managed" as the transaction attribute for the method of the MDB.
CNTR0085E: MDB {0} must implement method {1} of interface {2}.
Explanation The resource adapter is calling a method that is not implemented by the message-driven bean (MDB). Action Determine if the MDB was deployed to use the correct resource adapter. If the bean is bound to the correct resource adapter, change the MDB to provide an implementation for the method.
CNTR0086E: Transaction recovery setup error occurred for resource adapter {0}, MDB {1}.
Explanation The createEndpoint method was called on the JCA MessageEndpointFactory object by the resource adapter, and the resource adapter passed an XAResource object as one of the parameters of createEndpoint method. However, the resource adapter life cycle manager encountered an error which prevented it from setting up transaction recovery for this resource adapter. The endpoint cannot be created successfully. Action Examine the log for a prior error message indicating the setup failure for the message-driven bean (MDB) that was bound to the resource adapter. Correct the error to eliminate this error message.
CNTR0087E: Resource adapter {0} is not allowed to pass a non null XAResource to createEndpoint method for MDB {1}.
Explanation The createEndpoint method was called on the JCA MessageEndpointFactory object by the resource adapter, and the resource adapter passed an XAResource object to the createEndpoint method. Transaction recovery for this resource adapter is not supported, because the resource adapter indicated that it does not support XA transactions. The resource adapter is not allowed to pass an XAResource object to the createEndpoint method. Action Have the Resource Adaptor vendor correct the configuration or implementation of the resource adapter.
CNTR0088E: The user-provided class "{0}" may not implement the javax.ejb.TimedObject interface.
Explanation Enterprise Java bean (EJB) V1.x, V2.0, and Stateful Session beans cannot implement the javax.ejb.TimedObject interface. Action Change the EJB deployment to V2.1 or greater, change the implementation to not implement the javax.ejb.TimedObject interface, or change the EJB type.
CNTR0089E: Transaction attribute {0} is not allowed for method "{1}" on EJB {2}.
Explanation The enterprise Java bean (EJB) Specification does not allow the transaction attribute that is configured for the EJB method. See the EJB Specification for further details. Action Change the deployment descriptor to specify a transaction attribute that is allowed for the EJB method.
CNTR0090E: WebServiceRef binding failed for {0} : {1}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0091W: A reference to a MessageDestinationRef could not be found in the deployment descriptor for the WebApp or EnterpriseBean with the display name {0}.
Explanation The Java Enterprise Edition (Java EE) component might have specified binding information that is not valid. Action Verify that the binding information is correct in the deployment descriptor for the Java EE component.
CNTR0092W: Attempted to access EnterpriseBean {0}, that has not been started.
Explanation An application tried to access an enterprise bean of an application that has not been installed, has not been started, or did not start successfully. Action Verify that the application has been installed and started. If the application has been installed and started, see the previous messages regarding the failure of the enterprise bean to start, and correct those problems.
CNTR0093E: Attempt to start EnterpriseBean {0} failed with exception: {1}
Explanation An error has occurred during the initialization and start of an EnterpriseBean. Action Take action based upon the exception message in message CNTR0093E.
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".
Explanation A Bean Cache LoadPolicy that reloads an entity bean at intervals is only supported for EJB V2.x container-managed persistence (CMP) beans. Action Change the Bean Cache LoadPolicy to a value that is supported by the bean type, or change the bean to use EJB V2.x container-managed persistence.
CNTR0095W: EJB module configuration for session bean "{0}" is missing override of memory-to-memory replication settings.
Explanation The session bean is configured to override the settings for memory-to-memory replication at the enterprise Java bean (EJB) module level, but no settings for memory-to-memory replication are provided at the EJB module level. Action Disable the override at the EJB module level, or provide the settings for memory-to-memory replication for this session bean.
CNTR0096W: Application configuration for session bean "{0}" is missing override of memory-to-memory replication settings.
Explanation The session bean is configured to override the memory-to-memory replication settings at the application level, but no settings for memory-to-memory replication are provided at the application level. Action Disable the override at the application level, or provide the settings for memory-to-memory replication for this session bean.
CNTR0097W: Memory-to-memory replication settings for EJB container is missing.
Explanation Stateful session bean failover using memory-to-memory replication has been enabled, but the memory-to-memory replication settings are missing. Action Disable stateful session bean failover, or provide the settings for memory-to-memory replication for the EJB container.
CNTR0098I: Container-managed pre-find persistent store synchronization disabled for bean: "{0}".
Explanation The application is configured for this bean to not synchronize with persistent storage prior to the invocation of custom findBy methods. This behavior is not compliant with the enterprise Java bean (EJB) V2.0 and later specifications, but it can improve performance. Action There is no user action required.
CNTR0099I: {0} service has initialized successfully.
Explanation The z/OS Controller Service for Stateful SessionBean support in DRS has initialized successfully. Action There is no user action required.
CNTR0100E: Method {0} caught exception: {1}
Explanation An exception was caught in the specified method. Action There is no user action required.
CNTR0101E: Method {0} token is null.
Explanation The specified method was passed a servant token that is null. Action There is no user action required.
CNTR0102E: Method {0} entryKey is null.
Explanation The specified method was passed a entryKey parameter that is null. Action There is no user action required.
CNTR0103E: Method {0} value is null.
Explanation The specified method was passed a entryKey value that is null. Action There is no user action required.
CNTR0104E: Method {0} cannot convert entryKey to byte array.
Explanation The method specified was not able to convert the entryKey parameter to a byte array. Action There is no user action required.
CNTR0105E: Method {0} caught exception: {1} stoken = {2}.
Explanation The method specified caught an exception when processing the servant token. Action There is no user action required.
CNTR0106E: Method {0} cannot acquire proxy for stoken = {1}.
Explanation The method specified was not able to obtain a proxy for processing the servant token. Action There is no user action required.
CNTR0107E: Method {0} cannot convert token to byte array : stoken = {1}.
Explanation The method specified was not able to convert the servant token to a byte array. Action There is no user action required.
CNTR0108E: Method {0} caught exception {1} while acquiring proxy for token = {2}.
Explanation The method specified caught an exception acquiring a proxy for processing the servant token. Action There is no user action required.
CNTR0109E: Method {0} event parameter is null.
Explanation The method specified was passed an event parameter that is null. Action There is no user action required.
CNTR0110E: Method {0} cannot convert value to byte array.
Explanation The method specified was not able to convert the passed entryKey value to a byte array. Action There is no user action required.
CNTR0111E: Method {0} cannot convert event to byte array : stoken = {1}.
Explanation The method specified was not able to convert the event to a byte array. Action There is no user action required.
CNTR0112E: The user-provided class "{0}" must implement the "{1}" interface.
Explanation The enterprise Java bean (EJB) specification requires that message-driven beans implement the message listener interface for the messaging type that it supports. Action Change the class so that it implements the interface, as required by EJB specification.
CNTR0113I: SfDRSControllerInstance {0} received event REPLICATION_UP.
Explanation The SfDRSControllerInstance specified received the event REPLICATION_UP. Action There is no user action required.
CNTR0114I: SfDRSControllerInstance {0} received event REPLICATION_DOWN.
Explanation The SfDRSControllerInstance specified received the event REPLICATION_DOWN. Action There is no user action required.
CNTR0115I: SfDRSControllerInstance {0} received event IS_CONGESTED.
Explanation The SfDRSControllerInstance specified received the event IS_CONGESTED. Action There is no user action required.
CNTR0116I: SfDRSControllerInstance {0} received event NOT_CONGESTED.
Explanation The SfDRSControllerInstance specified received the event NOT_CONGESTED. Action There is no user action required.
CNTR0117I: Container-managed ejbStore() call will be bypassed on bean: "{0}" if it has not been modified in the current transaction.
Explanation The bean has been configured to prevent the enterprise Java bean (EJB) container from invoking the ejbStore() method if the bean has not been modified. This behavior is not compliant with the EJB V2.0 or later specifications, but it can improve performance. Action There is no user action required.
CNTR0118I: Container pre- and post-method processing for all local and local home methods will be bypassed on bean: "{0}".
Explanation The bean has been configured to streamline the processing that occurs before and after calling the methods that are defined on the local home interface and local business interface. This behavior is not compliant with the enterprise Java bean (EJB) V2.0 and later specifications, but it can improve performance. Action There is no user action required.
CNTR0119E: The user-provided class "{0}" may not implement the com.ibm.websphere.ejbcontainer.LightweightLocal interface. Reason code = {1}.
Explanation Only enterprise Java bean (EJB) V2.x or later entity beans with a local interface may implement the com.ibm.websphere.ejbcontainer.LightweightLocal interface. The reason code identifies the specific violation as follows: 1 - The EJB is not an Entity bean. 2 - The bean is an EJB V1.x or container-managed persistence (CMP) V1.x entity bean. 3 - The EJB does not have a local interface defined. Action Change the EJB to be of the type "Entity", change the EJB deployment to version 2.0 or greater, change the EJB deployment to specify a local interface, or change the implementation to not implement the com.ibm.websphere.ejbcontainer.LightweightLocal interface.
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".
Explanation An enterprise Java bean (EJB) java:comp/env context environment entry of the type Boolean should be assigned a value of 'true' or 'false'. Any other value will result in 'false', but it might be an indication of a problem in the configuration. The application might not behave as expected. Action Change the EJB java:comp/env context environment entry of type Boolean to either 'true' or 'false'.
CNTR0121W: XML configuration error in ejb-jar.xml for jar: "{0}". The container-transaction element in error has trans-attribute element: "{1}".
Explanation All ejb-name elements within the container-transaction element must match valid ejb-name elements within the enterprise-beans element. Action Correct the ejb-jar.xml file so that all ejb-name elements within the container-transaction element match valid ejb-name entries in the enterprise-beans element.
CNTR0123W: XML configuration error in ejb-jar.xml for jar: "{0}". The method-permission element in error for EJB: "{1}".
Explanation All ejb-name elements within the method-permission element must match valid ejb-name elements within the enterprise-beans element. Action Correct the ejb-jar.xml file so that all ejb-name elements within the method-permission element match valid ejb-name entries in the enterprise-beans element.
CNTR0124W: XML configuration error in ejb-jar.xml for jar: "{0}". The exclude-list element in error for EJB: "{1}".
Explanation All ejb-name elements within the exclude-list element must match valid ejb-name elements within the enterprise-beans element. Action Correct the ejb-jar.xml file so that all ejb-name elements within the exclude-list element match valid ejb-name entries in the enterprise-beans element.
CNTR0125E: Unable to process injection information for class: {0}.
Explanation The injection processors registered with the injection engine failed to identify and collect all the annotations associated with the class. Action Correct the ejb-jar.xml and annotations on the class.
CNTR0126E: The {0} message-driven bean (MDB) class does not define a message listener interface.
Explanation A message-driven bean must define a message listener interface using XML, annotations, or the implements clause of the EJB class. Action Check the XML and Java source for the MDB class and specify the message listener interface.
CNTR0130E: When a simple 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.
Explanation Simple JNDI binding name cannot be mixed with specific JNDI bindings for a given bean or home. Action Correct the bindings file settings for the bean or home in the specified module.
CNTR0131E: The {0} bean in the {1} module does not have any configured productive interfaces.
Explanation Depending on the bean type, an enterprise bean must have at least one component, business, Web service endpoint, or message listener interface configured. Action Correct the ejb-jar.xml file or source code annotation configuration settings for this bean.
CNTR0132E: The {0} session bean in the {1} module has an interface configured for a message listener or Web service endpoint.
Explanation Stateless session beans cannot have message listener interfaces configured. Stateful session beans cannot have either of these interface types configured. Action Correct the ejb-jar.xml file or source code annotation configuration settings for this bean.
CNTR0133E: The {0} entity bean in the {1} module has an interface configured for a business, message listener, or Web service endpoint.
Explanation Entity beans cannot have any of these interface types configured. Action Correct the ejb-jar.xml file or source code annotation configuration settings for this bean.
CNTR0134E: The {0} message-driven bean in the {1} module has an interface configured for a component, business, Web service endpoint, or home.
Explanation Message-driven beans cannot have any of these interface types configured. Action Correct the ejb-jar.xml file or source code annotation configuration settings for this bean.
CNTR0135E: The {0} message-driven bean (MDB) does not have a corresponding binding in the binding file.
Explanation A message-driven bean binding must exist in the binding file for each message driven bean. Action Check the ejb-jar-bnd.xml binding file for the MDB and ensure that a binding entry exists.
CNTR0136E: The specific JNDI binding name provided for a local home or bean does not begin with ejblocal:. The {2} local binding name specified for the home or {0} bean in the {1} module does not begin with ejblocal:.
Explanation The local binding name for the specified bean or home does not begin with ejblocal:. Action Correct the local binding name for the bean or home in the specified module.
CNTR0137E: The specific JNDI binding name provided for a remote home or bean begins with ejblocal:. The {2} remote binding name specified for the home or {0} bean in the {1} module cannot begin with ejblocal:.
Explanation The remote binding name for the given bean or home cannot begin with ejblocal:. Action Correct the remote binding name for the bean or home in the specified module.
CNTR0138E: The {0} bean or home in the {1} module contains a blank string value for the JNDI binding name.
Explanation JNDI binding names must not contain blank strings. Action Correct the ejb-jar-bnd.xml bindings file to give this bean a valid JNDI binding name.
CNTR0139E: The {0} bean in the {1} module has multiple JNDI binding names specified for the {2} business interface.
Explanation Each business interface can have a single JNDI binding name configured. Action Correct the ejb-jar-bnd.xml bindings file to give this bean a single JNDI binding name.
CNTR0140E: The {0} bean in the {1} module has specified the {2} business interface, which does not exist for a business interface JNDI binding.
Explanation Each business interface JNDI binding must have a valid business interface class configured. Action Correct the ejb-jar.xml file or source code annotations to configure a valid business interface class.
CNTR0141E: The {0} bean in the {1} module has specified a home JNDI binding. The binding does not have a matching home interface class.
Explanation Each home JNDI binding must have a matching home interface class configured. Action Correct the ejb-jar.xml file or source code annotations to configure a valid home interface class.
CNTR0142W: The EJB binding with the {0} JNDI name does not contain an enterprise bean stanza.
Explanation All EJB bindings require an enterpriseBean stanza within the ibm-ejb-jar-bnd.xml file. Action Check the ibm-ejb-jar-bnd.xml file and ensure that all EJB bindings include an enterprise bean stanza.
CNTR0143E: The EJB binding with the {0} JNDI name does not contain a jca-adapter stanza.
Explanation All bindings for message driven beans require a jca-adapter stanza within the message-driven binding. Action Check the binding file and ensure that all message-driven bindings include a jca-adapter stanza.
CNTR0144E: The EJB binding with the {0} JNDI name has a jca-adapter stanza that does not contain an activation-spec-binding-name.
Explanation All bindings for message driven beans require a jca-adapter stanza containing an activation-spec-binding-name. Action Check the binding file and ensure that all message-driven bindings include a jca-adapter stanza with an activation-spec-binding-name.
CNTR0145E: The EJB binding with the {0} JNDI name has a jca-adapter stanza that does not contain a destination-binding-name.
Explanation All bindings for message driven beans require a jca-adapter stanza containing a destination-binding-name. Action Check the binding file and ensure that all message-driven bindings include a jca-adapter stanza with a destination-binding-name.
CNTR0146E: The {0} bindings file contained in the {1} module has a configuration error at line number: {2}, column number: {3}.
Explanation The bindings file contains either a simple syntax error, or a semantic violation. Action Examine the log file for additional 'caused by' exceptions, which may provide specific parser message details. Correct the bindings file error and reinstall the application.
CNTR0147E: The {0} bindings file contained in the {1} module has a configuration error.
Explanation The bindings file contains either a simple syntax error, or a semantic violation. Action Correct the bindings file error and reinstall the application.
CNTR0148E: The {0} Container Managed Persistence (CMP) entity bean is configured to use a CMP Connection Factory with a {1} JNDI. This Connection Factory resource is not configured.
Explanation The Connection Factory resource that is required by this bean is not configured. The CMP entity bean will not function. Action Create the required Connection Factory resource by ensuring that the proper data source is selected for CMP use in the administrative console.
CNTR0149E: The start up process for the {0} enterprise bean in the {1} module failed with the following exception: {2}
Explanation An error has occurred during the initialization and start process for the bean. Action Examine the exception message to determine why the bean did not start. Also, check the log for other exception messages that are related to starting this bean.
CNTR0150E: The {0} annotation and the {1} annotation cannot both be configured on the {2} method of the {3} enterprise bean class.
Explanation The annotations that are identified in this error message are in conflict with each other. Do not specify these annotations on the same method. Action Change the Java source code by removing one or both of the annotations from the specified method. Then, reinstall the application.
CNTR0151E: The {0} role is specified multiple times in the @RolesAllowed annotation on the {1} method of the {2} enterprise bean class.
Explanation A specified role can be specified once in a @RolesAllowed annotation. Action Change the Java source code by removing the duplicate roles from this annotation. Then, reinstall the application.
CNTR0152E: The class-level {0} and {1} annotations cannot be configured on the {2} enterprise bean class at the same time.
Explanation The annotations that are identified in this error message are in conflict with each other. Do not specify these annotations on the same class. Action Change the Java source code by removing one, or both, of the annotations from the specified class. Then, reinstall the application.
CNTR0153E: The {0} role is specified multiple times in the class level @RolesAllowed annotation on the {1} enterprise bean class.
Explanation A given role can be specified once in a @RolesAllowed annotation.. Action Change the Java source code by removing the duplicate roles from this annotation. Then, reinstall the application.
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.
Explanation The component that is attempting to reference this bean has a configuration error. The component has specified an unsupported interface for this bean. Action Change the ejb-ref tag or @EJB annotation on the component that is attempting to reference this bean so that it specifies a supported interface. Check the log file for a related exception, which indicates the calling component that has the configuration error.
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.
Explanation The component that is attempting to reference the bean has a configuration error. The component has not specified whether to invoke the local or remote interface on this bean. Action Change the ejb-ref tag or @EJB annotation on the component that is attempting to reference this bean so that it specifies either the local or the remote interface of the bean. Check the log file for a related exception, which indicates the calling component that has the configuration error.
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.
Explanation Stateful sessions beans cannot be configured for both failover support and extended-scope persistence context support. Action Eliminate one of these two configuration settings for this bean. Then, reinstall the application.
CNTR0157E: The {0} enterprise bean in the {1} module does not implement the {2} method. This method is part of the bean interface.
Explanation Enterprise beans must implement all of the methods specified on their interface classes. Action Correct the bean implementation to include all of the required methods. Then, reinstall the application.
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.
Explanation Timer beans must implement a timeout method, which has either a single parameter of the javax.ejb.Timer type, or no parameters. Action Correct the bean implementation to include the required parameter, or include no parameters. Then, reinstall the application.
CNTR0159E: The {0} module has a configuration error in the inheritance relationship specified between the {1} parent bean and the {2} child bean.
Explanation There might be an error in the configuration extensions file for the module, or one of the two beans might not exist. Action Correct the configured inheritance relationship in the extensions XML file for the module or supply the missing bean implementation.
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
Explanation Timer beans, which inherit from the TimedObject interface, must implement the following timeout method: ejbTimeout Action Correct the bean implementation to include the required method. Then, reinstall the application.
CNTR0161E: The {0} enterprise bean in the {1} module has specified the @Timeout annotation on more than one method.
Explanation Timer beans may only implement a single timeout method. Action Correct the bean implementation to include only one timeout method. Then, reinstall the application.
CNTR0162E: The {0} enterprise bean in the {1} module has specified the following timeout method: {2} This method is not implemented by the bean.
Explanation Timer beans must provide an implementation for the configured timeout method. Action Correct the bean implementation to include the required timeout method. Then, reinstall the application.
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.
Explanation Timer beans must configure only one timeout method. Action Correct the bean configuration to specify a single timeout method. Then, reinstall the application.
CNTR0164E: The {0} enterprise bean in the {1} module implements a {2} timeout method, which creates an application exception..
Explanation Timeout methods must not create application exceptions. Action Correct the timeout method implementation to not create application exceptions. Then, reinstall the application.
CNTR0165E: The {0} enterprise bean in the {1} module implements a {2} timeout method, which has a non-void return type.
Explanation Timeout methods must return void. Action Correct the timeout method implementation to return void. Then, reinstall the application.
CNTR0166E: The {0} enterprise bean in the {1} module implements a {2} timeout method, which is declared as static or final.
Explanation Timeout methods must not be declared as static or final. Action Correct the implementation declaration for the timeout method. Then, reinstall the application.
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}
Explanation The interface has been bound at the specified naming location. Action Use the specified naming location when attempting to look up this interface.
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 specified.
Explanation Because the enterprise bean has multiple interfaces, each binding name must be extended to make it unique. Action Complete one of the following actions: /n Look up the interfaces for this enterprise bean using the extended names. /n Change the configuration data for this bean to specify unique binding locations for each interface.
CNTR0169E: The {0} enterprise bean, which is specified in the {1} binding within the {2} module, does not exist.
Explanation The enterprise bean name might be incorrect, or a binding might have been specified for a bean that does not exist. Action Correct the binding file. Then, reinstall the application.
CNTR0170E: The {0} enterprise bean in the {1} module does not have a defined bean type.
Explanation Each enterprise bean must specify a bean type such as stateless session bean, message driven bean, and so on. Action Correct the Java source code annotation or the ejb-jar.xml configuration setting for this bean. Then, reinstall the application.
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}
Explanation Each enterprise bean must specify a unique binding location. Action Correct the binding file for one of these two beans so that each bean has a unique binding location.
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.
Explanation Each enterprise bean interface must specify a unique binding location. Action Correct the binding file for one of these two bean interfaces so that each interface has a unique binding 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.
Explanation Each enterprise bean interface must specify a unique binding location. Action Correct the binding file for one of these two bean interfaces so that each interface has a unique binding location.
CNTR0174I: The {0} bean in the {1} module is an EJB version prior to 3.0, and has no home binding name specified. The following binding name has been manufactured for this bean: {2}.
Explanation The home interface will be bound at the specified naming location. Action There is no user action required.
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.
Explanation A Stateful Session bean that references an extended persistence context must be configured with an Activation Policy of ONCE. Action Change the Activation Policy configured for the bean to 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.
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0177E: Failure occurred attempting to create a Web service endpoint proxy for the {0} bean in the {1} module of the {2} application : {3}
Explanation A session bean is not allowed to implement both a Web service Provider interface and a JAX-RPC Web service endpoint interface. Action Remove the configured JAX-RPC Web service endpoint interface from the ejb-jar.xml file, or change the bean implementation so that it does not implement the Web service Provider interface.
CNTR0178E: Configured Web service endpoint method {0} is not implemented by the {1} bean in the {2} module of the {3} application.
Explanation All configured Web service endpoint methods must be implemented by the bean. Action Change bean implementation to include all Web service endpoint methods.
CNTR0179W: Non-persistent timer maximum number of retries {0} was reached.
Explanation The maximum number of retries configured on the EJB timer service (nonPersistentTimerRetryCount on the EJBTimer configuration object) has been reached. No further retries will be attempted until a timout method succeeds. Action Determine the cause of the failing timeout method, or increase the maximum number of retries.
CNTR0183E: The timer manager used by the EJB timer service could not be obtained.
{0}
Explanation An attempt was made to obtain the timer manager, because the option to create a separate thread pool for non-persistent timers was configured on the EJBTimer configuration object (uniqueTimerManagerForNP). Action As an alternative, you may configure the timer service to use a scheduler for non-persistent timers.
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.
Explanation An interceptor stanza contains more than one ejb-ref, resource-ref, resource-env-ref, or message-destination-ref stanza with the same value for its name attribute. Each ejb-ref, resource-ref, resource-env-ref, or message-destination-ref stanza is required to have a different name attribute value. Action Either remove the extranous stanza or change the value of its name attribute in one or more ejb-ref, resource-ref, resource-env-ref, or message-destination-ref stanza so that the name is unique within the interceptor stanza and within the session or message-driven stanza for the 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.
Explanation We can configure asynchronous methods on session beans only. Action Remove the asynchronous method from the bean.
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.
Explanation Asynchronous methods can have the following transaction attribute types configured: TX_REQUIRED, TX_REQUIRES_NEW, or TX_NOT_SUPPORTED. Action Change the transaction attribute configuration on the method to one of the three supported types.
CNTR0188E: An unexpected exception was caught. The exception is: {0}
Explanation This exception is unexpected. The cause is not immediately known. Action More info at:
CNTR0189E: The {0} bean class can not be designated as a Startup bean using Java annotations or within the XML deployment descriptor.
Explanation Only Singleton Session beans can be defined with the Startup annotation or XML deployment descriptor. Action Eliminate the Startup Java annotation or XML deployment descriptor from this EJB class, or change the class to be a Singleton Session Bean.
CNTR0190E: The {0} startup singleton session bean in the {1} module failed initialization with exception:
{2}
Explanation Startup Singleton Session bean instances are created as part of application start processing. Any failure will result in the application failing to start. Action Eliminate cause of the exception that is attached to this error message.
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}
Explanation When you share thread pools that are configured for persistent timers, configure multiple timer threads. On the EJBTimer configuration object, when the uniqueTimerManagerForNP attribute is set to true, the numNPTimerThreads attribute must be set to 1 or greater. Action In the EJB timer service settings of the application server, specify a positive value for the number of non-persistent timer threads. As an alternative, you can configure the timer service to use a scheduler for non-persistent timers by selecting the option to share thread pool configured for persistent timers (Specify false for the uniqueTimerManagerForNP attribute on the EJBTimer configuration object).
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).
Explanation The access timeout is specified either via annotations or by deployment descriptor. The value must be -1 or greater and less than java.lang.Long.MAX_VALUE (9223372036854775807). Action Correct the access timeout value for the method identified by the message. A method name of "*" is used in deployment descriptor to indicate all methods of the singleton class. If annotation is used and @AccessTimeout annotation is not found on the method, correct the @AccessTimeout annotation at class level.
CNTR0193E: The value, {0}, specified for the concurrency management type of the {1} enterprise bean class must be either Bean or Container.
Explanation The concurrency management type can be specified using either the @ConcurrencyManagement annotation or the concurrency-management-type tag in deployment descriptor for a Singleton session bean. The value must be either BEAN or CONTAINER for Singleton session beans. Action Correct the @ConcurrencyManagement annotation or the concurrency-management-type tag so that the value is either Bean or Ccontainer.
CNTR0194E: The value {0} 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.
Explanation The deployment descriptor cannot override the value provided by the @ConcurrencyManagement annotation on a Singleton session bean. Action Remove or change the value in the ejb-jar.xml file so that it does not override the value in the @ConcurrencyManagement annotation.
CNTR0195E: The work manager associated with the {0} scheduler used by the EJB timer service could not be obtained.
Explanation An attempt was made to obtain the work manager. Action Ensure that the timer service scheduler has a work manager configured.
CNTR0196E: The conversion of access timeout value {0} from {1} time unit to milli-seconds time unit resulted in an overflow.
Explanation The access timeout is specified either via annotations or by deployment descriptor. The resulting conversion to milli-seconds must be greater than zero and less than java.lang.Long.MAX_VALUE (9223372036854775807) to be valid. Action Correct the access timeout value for the method identified by the message. A method name of "*" is used in deployment descriptor to indicate all methods of the singleton class. If annotation is used and @AccessTimeout annotation is not found on the method, correct the @AccessTimeout annotation at class level.
CNTR0197E: The {0} non-singleton enterprise bean has dependency metadata.
Explanation The bean was configured to depend on another bean through the @DependsOn annotation or the depends-on element in the ejb-jar.xml file. However, the bean is not a singleton session bean. Action Remove the dependency metadata, or change the type of the bean.
CNTR0198E: The {0} singleton session bean in the {1} module depends on {2}, which does not exist.
Explanation The bean was configured to depend on another bean through the @DependsOn annotation or the depends-on element in the ejb-jar.xml file. However, the other bean does not exist. Action Remove or change the dependency on the nonexistent bean.
CNTR0199E: The {0} singleton session bean in the {1} module depends on {2}, which does not uniquely specify an enterprise bean.
Explanation The bean was configured to depend on another bean with the specified name. A bean with that name does not exist in the same module, and more than one module has a bean with that name. Action Remove the dependency, or use a fully qualified bean name such as module.jar#BeanName
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.
Explanation The bean was configured to depend on another bean through the @DependsOn annotation or the depends-on element in the ejb-jar.xml file. However, the other bean is not a singleton. Action Remove or change the dependency on the non-singleton bean, or adjust the type of the non-singleton bean.
CNTR0201E: The {0} singleton session bean in the {1} module directly or indirectly depends on itself.
Explanation The bean was configured to depend on itself or another bean that indirectly depends on that bean through the @DependsOn annotation or the depends-on element in the ejb-jar.xml file. Action Remove or change the dependency on the specified bean, or change one of its dependencies to not depend on it.
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.
Explanation The method was configured to be asynchronous through the @Asynchronous annotation or the asynch-method element in the ejb-jar.xml file. Asynchronous methods with a void return type must not have application exceptions on the throws clause. Action Change the return type of method, remove the application exception from the throws clause, or change the metadata for the method so that it is not asynchronous.
CNTR0203E: The ejb-jar.xml declares an asynchronous method for the {0} session bean, but did not declare a method-name.
Explanation The specified session bean declares an asynchronous method in the ejb-jar.xml file, but did not specify the "method-name" element. Action Modify the ejb-jar.xml file and specify a method-name for the method that should be asynchronous (or "*" for all methods).
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.
Explanation The ejb-jar.xml file incorrectly specifies a method-params element inside an async-method element which contains a wildcard (*) method-name element. This is not allowed, per the EJB 3.1 specification. Action Either remove the method-params element from the XML or change the method-name element to represent a specific method with the specified method-params parameters.
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.
Explanation The only valid values for the method-intf element of an asynchronous method are "Local" and "Remote". Any other value is invalid and the EJB Container will not recognize the containing async-method element. Action Modify the method-intf element's value to be either "Local" or "Remote".
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.
Explanation Asynchronous methods must return void or future <V>. Action Correct the asynchronous method implementation to return void or future <V>. Then, reinstall the application.
CNTR0207E: The {0} stateful session bean in the {1} module has an automatic timer.
Explanation We cannot specify automatic timers for stateful session beans. Action Remove the automatic timer, or change the bean type.
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.
Explanation An automatic timer can either have no parameters or a single javax.ejb.Timer parameter. Action Change the method parameter types, or remove the automatic timer metadata.
CNTR0209E: The {0} enterprise bean in the {1} module has the {2} timeout callback method that does not have the required method signature.
Explanation The EJB specification requires that timeout callback methods have the following signature: void <METHOD>() or void <METHOD>(Timer timer) Action Correct the timeout callback method signature for this bean class.
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.
Explanation The deployment descriptor contains automatic timer metadata for the specified method name, but no method with a timeout callback method signature was found by that name. A timeout callback method must have a void return type, and it must either have no parameters or have a single parameter with the type javax.ejb.Timer. Action Add a method with the specified name, change the method signature of an existing method with that name, or remove the timer from the deployment descriptor.
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.
Explanation The specified method has automatic timer metadata in the deployment descriptor or in a @Schedule or @Schedules annotation, but the specified field in the metadata has a value that is not valid. Action Change the field in the automatic timer metadata, or remove the automatic timer metadata.
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.
Explanation The specified method has automatic timer metadata in the deployment descriptor or in a @Schedule or @Schedules annotation, but the specified field in the metadata has a value that is out of bounds for that field. Action Change the field in the automatic timer metadata, or remove the automatic timer metadata.
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.
Explanation The specified method has automatic timer metadata in the deployment descriptor or in a @Schedule or @Schedules annotation, but the specified field in the metadata has an range bound that is not valid. The upper and lower bound for a range must be non-negative integers or keyword values. Action Change the field in the automatic timer metadata, or remove the automatic timer metadata.
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.
Explanation The specified method has automatic timer metadata in the deployment descriptor or in a @Schedule or @Schedules annotation, but the specified field in the metadata has an interval value that is not valid. Increment values must be integers. Action Change the field in the automatic timer metadata, or remove the automatic timer metadata.
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.
Explanation The specified method has automatic timer metadata in the deployment descriptor or in a @Schedule or @Schedules annotation, but the specified field in the metadata has a value for a list that is not valid. List values must be integers, keywords, or ranges. Action Change the field in the automatic timer metadata, or remove the automatic timer metadata.
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.
Explanation The specified method has automatic timer metadata in the deployment descriptor or in a @Schedule or @Schedules annotation, but the specified field in the metadata uses an increment. We can use increments for the second, minute, and hour fields only. Action Change the field in the automatic timer metadata, or remove the automatic timer metadata.
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.
Explanation The specified method has automatic timer metadata in the deployment descriptor or in a @Schedule or @Schedules annotation, but the specified field in the metadata has an ordinal keyword without a day of the week. The 1st, 2nd, 3rd, 4th, and 5th keywords must be followed by a keyword for the day of the week. Action Change the field in the automatic timer metadata, or remove the automatic timer metadata.
CNTR0218E: An error occurred while creating persistent automatic timers for the {0} module:
{1}
Explanation Either the module has metadata that is not valid, or the scheduler for the EJB timer service was unable to create the automatic timers. Action Check the module metadata and scheduler configuration.
CNTR0219I: The server created {0} persistent automatic timer or timers and {1} non-persistent automatic timer or timers for the {2} module.
Explanation The server has created the specified number of automatic timers for the specified module. If the server had previously created persistent automatic timers for this module, then no persistent automatic timers will be created on subsequent starts of the application. Action There is no user action required.
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}
Explanation The @Interceptors annotation or the interceptor-class tag in the deployment descriptor was used to provide a list of interceptor class names. A class must exist only once in the interceptor class list. Action Eliminate the duplicate interceptor class from the interceptor class list. Or, change the interceptor class name, if an incorrect name was specified.
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}
Explanation An interceptor class can be either a class-level or a method-level interceptor, but not both types. Action Eliminate the interceptor class from either the class-level interceptor list or the method-level interceptor list.
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}
Explanation The interceptor class can be either a default interceptor or a method-level interceptor, but not both types. Action Eliminate the interceptor class from either the default interceptor list or the method-level interceptor list.
CNTR0223E: Only one method in the {0} class is allowed to be a {1} interceptor method.
Explanation More than one method of this class is specified as an interceptor method of the given type. The EJB 3.0 specification does not allow you to have multiple interceptor methods of the same type for this class. Action Correct the Java source code annotations or deployment descriptor for this class so that it only contains a single interceptor method of the given type.
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.
Explanation The interceptor-binding element is using an exclude-class-interceptors element, which must specify a method-name tag. Action Correct the deployment descriptor by adding a method-name tag.
CNTR0225E: The exclude-default-interceptors element in the deployment descriptor is not valid for a style 1 interceptor-binding element.
Explanation The interceptor-binding element is using an exclude-default-interceptors element which is only valid for a style 2, style 3, or style 4 interceptor-binding element. Action Eliminate the exclude-default-intercrptor element. Or, change the ejb-name tag within the interceptor-binding element to provide a specific enterprise bean name.
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.
Explanation Style 3 and style 4 interceptor-binding elements cannot be specified on the same method of an enterprise bean. Action Eliminate either the style 3 or the style 4 interceptor-binding element for the specified method of this 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}
Explanation When the interceptor-order element is used, the specified ordering at the class-level must be a total order. The order must be over all of the interceptor classes that have been defined at that level and above. The only exception to this rule is when interceptor classes have been explicitly excluded by means of an exclude-default-inteceptors element. Action Specify additional interceptor names on the class-level interceptor-order element for this bean. Then, the bean will provide a total ordering of the interceptors.
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}.
Explanation When the interceptor-order element is used, the specified ordering at the method-level must be a total order. The order must be over all of the interceptor classes that have been defined at that level and above. The only exception to this rule is when interceptor classes have been explicitly excluded by means of an exclude-class-interceptors or exclude-default-inteceptors element. Action Specify additional interceptor names on the method-level interceptor-order element for this bean. Then, the bean will provide a total ordering of the interceptors.
CNTR0229E: The {0} interceptor method must not be declared as final or static.
Explanation The EJB 3.0 specification does not allow an interceptor method to be final or static. Action Remove the final or static modifier from this interceptor method.
CNTR0230E: The {0} method does not have the required method signature for a {1} method.
Explanation The EJB 3.0 specification requires that around-invoke and around-timeout methods have the following signature: Object <METHOD>(InvocationContext) throws Exception Action Correct the method signature of this interceptor.
CNTR0231E: The {0} method signature is not valid as a {1} method of an enterprise bean class.
Explanation The EJB 3.0 specification requires that life cycle methods of an enterprise bean have the following signature: void <METHOD>() Action Correct the method signature for this interceptor.
CNTR0232E: The {0} method does not have the required method signature for a {1} method of a interceptor class.
Explanation The EJB 3.0 specification requires that life cycle methods of an interceptor class have the following signature: void <METHOD> (InvocationContext) Action Correct the method signature for this interceptor.
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.
Explanation The EJB 3.0 specification requires that @Remove annotations be applied to business methods of a stateful session bean. Action Either relocate the @Remove annotation to a business method of this bean, or change the specified method to be a business method.
CNTR0234E: An initialization method for a stateful session bean can be an ejbCreate<METHOD> method only when the bean conforms to the EJB 2.1 or earlier specification levels. Therefore, it cannot be applied to the {0} method of the {1} enterprise bean.
Explanation The EJB 3.0 specification requires a matching ejbCreate<METHOD> to be the initialization method of a stateful session bean class. This requirement exists for stateful session beans that are written for the EJB 2.1 or earlier-level API. Action Remove the @Init annotation or the init-method element in ejb-jar.xml file from the specified method of this bean.
CNTR0235E: The name of the adapted create<METHOD> method must be specified for either the {0} method or the {1} method of the {2} enterprise bean.
Explanation The @Init annotation is applied to multiple methods of the enterprise bean. The EJB 3.0 specification requires that the name of the adapted create<METHOD> method of the home or local home interface must be specified if there is any ambiguity. Action Use the value element of the @Init annotation to specify the name of the create<METHOD> on one of the two specified methods. This approach will remove the ambiguity.
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.
Explanation The init-method element specifies a method name that is not a public method of the enterprise bean class. Action Correct either the method name or the method signature in the init-method element to specify a public method of this bean.
CNTR0237E: The user-provided enterprise bean level 3.0 {0} interceptor class cannot be found or loaded.
Explanation An enterprise bean level 3.0 interceptor class cannot not be found or loaded. Action Verify that the interceptor class is installed and configured correctly.
CNTR0238E: The {2} interceptor class specifies the {1} method, which is not an {0} method of this class.
Explanation The specified method name is not a method of the interceptor class. Action Correct either the method name or method signature to specify one of the methods of this interceptor class.
CNTR0239E: The method-name element is not valid for a style 1 interceptor-binding element.
Explanation The method-name element is not allowed in a style 1 interceptor-binding element. Action Correct the interceptor-binding to be a style 2 interceptor-binding element or remove the method-name element.
CNTR0240E: The {1} enterprise bean specifies the {0} class-level interceptor, which duplicates a name in the following default interceptors list: {2}
Explanation This interceptor class cannot be in both the default interceptor list and the class-level interceptor list unless the default interceptors are excluded at the class level. Action Remove the duplicate interceptor class from either the default or the class-level interceptor list. Or, exclude the default interceptors at the class level for this bean.
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.
Explanation For a stateless session bean, the EJB 3.0 specification requires that the ejbCreate, ejbRemove, ejbActivate, and ejbPassivate methods be treated as @PostConstruct, @PreDestroy, @PostActivate, and @PrePassivate life cycle callback interceptor methods, respectively. Action Correct the deployment descriptor or annotation so that the method is the correct type of life cycle callback interceptor.
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.
Explanation For a stateful session bean, the EJB 3.0 specification requires that the ejbRemove, ejbActivate, and ejbPassivate methods be treated as @PreDestroy, @PostActivate, and @PrePassivate life cycle callback interceptor methods, respectively. The ejbCreate method must be treated as an @Init method. Action Correct the deployment descriptor or annotation so that the method is the correct type of life cycle callback interceptor.
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.
Explanation For a message driven bean, the EJB 3.0 specification requires that the ejbCreate and ejbPassivate methods be treated as @PostConstruct and @PreDestroy life cycle callback interceptor methods, respectively. Action Correct the deployment descriptor or annotation so that the method is the correct type of life cycle callback interceptor.
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.
Explanation According to the EJB specification, a style 3 or style 4 interceptor-binding must use a <method-name> tag to specify the name of a method that is found in one of the business interfaces of the enterprise bean. Action Either specify one of the method names found in one of the business interfaces of the enterprise bean or add the method to one of the business interfaces 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.
Explanation According to the EJB specification, only one style 1 interceptor-binding can be used for the module. Action Correct deployment descriptor so that only one style 1 interceptor-binding is used for the module.
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.
Explanation According to the EJB specification, only one style 2 interceptor-binding can be used for each enterprise bean. Action Correct deployment descriptor so that only one style 2 interceptor-binding is used for the enterprise bean.
CNTR0247E: More than one style 3 interceptor-binding element is provided in the deployment descriptor for the {0} method of the {1} enterprise bean.
Explanation According to the EJB specification, only one style 3 interceptor-binding can be used for each method of an enterprise bean. Action Correct deployment descriptor so that only one style 3 interceptor-binding is used for the method of an 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.
Explanation According to the EJB specification, only one style 4 interceptor-binding can be used for each method of a given method signature of an enterprise bean. Action Correct deployment descriptor so that only one style 4 interceptor-binding is used for the method of an 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} "
Explanation Any automatic Enterprise Java Bean timers associated with the application, on the server, were not removed from the scheduler. Therefore, the scheduler may attempt to run these timers in the future. Action Execute the 'removeAutomaticEJBTimers' command from a connected wsadmin session to remove the timers associated with the application on this specific server.
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} "
Explanation Any automatic Enterprise Java Bean timers associated with the application and module, on the server, were not removed from the scheduler. Therefore, the scheduler may attempt to run these timers in the future. Action Execute the 'removeAutomaticEJBTimers' command from a connected wsadmin session to remove the timers associated with the application and module on this specific server.
CNTR0253W: Unable to find the RemoveBinaries task. As a result, if automatically created EJB timers exist, they are not removed.
Explanation Use the removeAutomaticEJBTimers command to manually remove any automatic Enterprise Java Bean timers that are no longer valid. Action The processing to remove any automatic Enterprise Java Bean timers is triggered by another internal process, called RemoveBinaries, which was not found. As a result, the processing to remove automatic Enterprise Java Bean timers did not run.
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.
Explanation Use the removeAutommaticEJBTimers command to manually remove any automatic Enterprise Java Bean timers that are no longer valid. Action The processing to remove automatic Enterprise Java Bean timers does not execute when you are running in a disconnected wsadmin session. As a result, the automatic Enterprise Java Bean timers were not removed.
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.
Explanation The server attempted to run a timeout callback method for an automatic timer, but an incompatible change was made to the application without removing the automatic timers. Action Stop the application and run the removeAutomaticEJBTimers command to manually clear the contents of the database. The server automatically recreates the timers when the application is restarted.
CNTR0302W: The work manager configuration used for asynchronous methods does not comply with the EJB specification.
Explanation The specification requires asynchronous methods to have security context information only. Action Ensure that the work manager instance is configured to pass security context only, as required by the specification.
CNTR0303W: The work manager configuration used for the EJB timer service does not comply with the EJB specification.
Explanation The specification does not support any execution context information passed to the timeout method. Action Ensure that the work manager instance is configured to not pass context information, as required by the 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.
Explanation The @StatefulTimeout annotation is only applicable to stateful session beans. The Enterprise JavaBean (EJB) container will ignore the annotation on this bean. Action Remove the @StatefulTimeout annotation from the specified bean, or make the bean a stateful session 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.
Explanation The @Asynchronous annotation is only applicable on bean classes, not business interfaces. The EJB container ignores these annotations on the interfaces. Unless this annotation is specified on the bean class or a bean class method, or if the methods are declared asynchronous in the ejb-jar.xml deployment descriptor, the bean methods will run synchronously. Action Remove any @Asynchronous annotation from the specified business interface, and verify that the annotations are specified correctly in the bean class.
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.
Explanation The @StatefulTimeout annotation is only applicable on bean classes, not business interfaces. The EJB container ignores this annotations on interfaces. Unless this annotation is specified on the bean class or a bean class method, or if the bean declares a stateful-timeout in the ejb-jar.xml deployment descriptor, the bean will use a default timeout value. Action Remove the @StatefulTimeout annotation from the specified business interface, and verify that the annotations are specified correctly in the bean class.
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.
Explanation Only a positive integer can be specified for the stateful timeout value. The default value will be used. Action Change the value for the stateful timeout to a positive integer.
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.
Explanation The timeout value is required to be specified on the stateful-timeout deployment descriptor element. Action Add a timeout value to the stateful-timeout deployment descriptor element for the specified bean.
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.
Explanation The stateful timeout is specified either via annotations or by deployment descriptor. The resulting conversion to milliseconds must be greater than zero and less than java.lang.Long.MAX_VALUE (9223372036854775807) to be valid. Action Correct the stateful timeout value for the Enterprise JavaBean identified by the message.
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.
Explanation This element applies only to stateful session beans. The Enterprise JavaBean (EJB) container will ignore the stateful-timeout on this bean. Action Remove the stateful-timeout deployment descriptor element from the specified bean, or make the bean a stateful session 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}.
Explanation The stateful timeout must be postive, or 0 to indicate no timeout, or -1 to indicate infinite timeout. Action Modify the StatefulTimeout annotation on the EJB.
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}.
Explanation The stateful timeout must be postive, or 0 to indicate no timeout, or -1 to indicate infinite timeout. Action Modify the stateful-timeout timeout element in the EJB deployment descriptor.
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.
Explanation Only a positive integer can be specified for the stateful timeout value. The default value will be used. Action Change the value for the stateful timeout to a positive integer.
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.
Explanation The deployment descriptor defines a timer that targets the specified method, but does not indicate how many parameters that method accepts. Multiple methods have that same name in the class hierarchy of the bean, which are eligible to receive timer callbacks. As a result, the EJB container is unable to determine which method the timer must target. Action Change the deployment descriptor so that the timer explicitly indicates whether it targets the zero parameter or the one parameter version of the method.
CNTR0315E: The {0} stateful session bean in the {1} module in the {2} application did not declare a dependency on the {3} persistence reference.
Explanation When a stateful session bean is located in a WAR, it must declare dependencies on all persistence context references and persistence unit references that it intends to access. Action Add the appropriate @PersistenceContext or @PersistenceUnit source code annotation to the stateful session bean, or add the appropriate persistence-context-ref or persistence-unit-ref element to the appropriate session element in the XML deployment descriptor.
CNTR0316E: A resource reference conflict was detected. {0}
Explanation A resource reference was defined in multiple places, with conflicting information. Action Change the resource reference definitions so they no longer conflict, or use a single resource reference and remove the duplicate resource reference definitions.
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.
Explanation An Enterprise JavaBean may not be declared as a JAX-RPC endpoint and packaged inside a WAR module. Action Package the Enterprise JavaBean in an EJBJAR module. Or, update to ejb-jar.xml descriptor to no longer declare the Enterprise JavaBean as a JAX-RPC endpoint.
CNTR0318E: No ejb-class element was specified for the {0} bean, in the {1} module, of the {2} application.
Explanation When declaring an Enterprise JavaBean in the ejb-jar.xml file, users must provide a class name for the bean. Action Modify the ejb-jar.xml file or application source code and re-install the 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.
Explanation A startup bean must not be packaged inside of a .war file. Action Package the startup bean inside a stand-alone EJB JAR module. Alternatively, use a singleton session bean marked with the @Startup annotation or the corresponding XML element, and package the bean in either an EJB JAR module or a WAR module.
CNTR0320E: The {0} singleton session bean in the {1} module has an interface configured for a component view.
Explanation According to the EJB specification, the EJB 2.1 remote and local client views are not supported for singleton session beans. Action Correct the ejb-jar.xml file or source code annotation configuration settings for this bean.
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.
Explanation According to the EJB specification, method return types for an enterprise bean must match the corresponding interface. Action Change the return type of the method so that the enterprise bean and the interface return types are the same.
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.
Explanation According to the EJB specification, method return types for an enterprise bean must be compatible with the corresponding interface. Action Change the return type of the method so that the enterprise bean and the interface return types are compatible.
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}.
Explanation The EJB 3.1 specification requires that a stateful session bean must not both implement the javax.ejb.SessionSynchronization interface and also configure a session synchronization method in the ejb-jar.xml file or with an annotation. Action Remove either the implementation of the javax.ejb.SessionSynchronization interface or the configuration of the session synchronization methods.
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.
Explanation The EJB 3.1 specification requires that session synchronization methods of a stateful session bean class have the following signature: after-begin and before-completion : void <METHOD> (), after-completion : void <METHOD> (boolean) Action Correct the session synchronization method signature for this bean class.
CNTR0325E: The configured {0} session synchronization method {1} is not implemented by the {2} bean in the {3} module of the {4} application.
Explanation All configured session synchronization methods must be implemented by the bean. Action Change the bean implementation to include all configured session synchronization methods.
CNTR0326E: Multiple {0} session synchronization methods have been configured for the {1} bean. The configured session synchronization methods are : {2} and {3}
Explanation The EJB 3.1 specification requires that only one of each type of session synchronization method be configured for a stateful session bean. Action Configure only one of each type of session synchronization method for this bean.
CNTR0327E: The {0} method does not have the required method signature for a {1} session synchronization method.
Explanation The EJB 3.1 specification requires that session synchronization methods of a stateful session bean class have the following signature: after-begin and before-completion : void <METHOD> (), after-completion : void <METHOD> (boolean) Action Correct the session synchronization method signature for this bean class.
CNTR5001E: The {0} bean is configured with the {1} remote component interface, but a remote home interface has not been provided.
Explanation According to the EJB specification, a remote home interface must be provided when a remote component interface is provided. Action Change the application configuration to provide a remote home interface for the bean.
CNTR5002E: The {0} bean is configured with the {1} local component interface, but a local home interface has not been provided.
Explanation According to the EJB specification, a local home interface must be provided when a local component interface is provided. Action Change the application configuration to provide a local home interface for the bean.
CNTR5003E: The {1} bean class for the {0} bean is not defined as public.
Explanation According to the EJB specification, the bean class must be defined as public. Action Define the bean class as public.
CNTR5004E: The {1} bean class for the {0} bean is defined as final.
Explanation According to the EJB specification, the bean class must not be defined as final. Action Do not define the bean class as a final class.
CNTR5005E: The {1} bean class for the {0} bean is defined as abstract.
Explanation According to the EJB specification, the bean class must not be defined as abstract. Action Do not define the bean class as an abstract class.
CNTR5006E: The {1} bean class for the {0} bean is not defined as a top level class.
Explanation According to the EJB specification, the bean class must be defined as a top level class. Action Define the bean class 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.
Explanation According to the EJB specification, the bean class must have a public constructor that does not take parameters. Action Change the bean class to have a public constructor that does not take parameters.
CNTR5008E: The {1} bean class for the {0} bean has defined the finalize method.
Explanation According to the EJB specification, the bean class must not define the finalize method. Action Do not define the finalize method in the bean class.
CNTR5009E: The {1} bean class for the {0} entity bean does not implement the javax.ejb.EntityBean class.
Explanation According to the EJB specification, the entity bean class must implement the javax.ejb.EntityBean class. Action Change the bean class to 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.
Explanation According to the EJB specification, the name of business methods must not start with ejb. Otherwise, conflicts might occur with the callback methods. Action Change the name of the business method so that it does 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.
Explanation According to the EJB specification, the configured business and component interfaces must be Java interfaces. Action Change the bean configuration to provide Java interfaces.
CNTR5012E: The {1} interface, which has been configured as a business interface for the {0} bean, must not extend the {2} interface.
Explanation According to the EJB specification, the configured business interfaces must not extend any interface in the javax.ejb package. Action Change the business interface to not extend an interface in the javax.ejb package. Also, you can change the bean configuration to not specify the interface as a business 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.
Explanation According to the EJB specification, the configured local interfaces must not extend the javax.rmi.Remote interface. Action Change the interface to not extend the javax.rmi.Remote interface. Also, you can change the bean configuration to not specify the interface as a local 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.
Explanation According to the EJB specification, the configured local component interface must extend the javax.ejb.EJBLocalObject interface. Action Change the interface to extend the javax.ejb.EJBLocalObject interface. Also, you can change the bean configuration to not specify the interface as a local component 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.
Explanation According to the EJB specification, the configured remote component interface must extend the javax.ejb.EJBObject interface. Action Change the interface to extend the javax.ejb.EJBObject interface. Also, you can change the bean configuration to not specify the interface as a remote component 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.
Explanation According to the EJB specification, the configured local home interface must extend the javax.ejb.EJBLocalHome interface. Action Change the interface to extend the javax.ejb.EJBLocalHome interface or change the bean configuration to not specify the interface as a local home 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.
Explanation According to the EJB specification, the configured remote home interface must extend the javax.ejb.EJBHome interface. Action Change the interface to extend the javax.ejb.EJBHome interface or change the bean configuration to not specify the interface as the remote home 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.
Explanation According to the EJB specification, all create methods on a home interface must return the component interface. Action Change the create methods on the home interface to 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.
Explanation According to the EJB specification, all home interfaces must define at least one create method. Action Change the home interface to 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.
Explanation According to the EJB specification, all create methods on a home interface must return the component interface. Action Change the create methods on the home interface to return the 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.
Explanation According to the EJB specification, the throws clause of all create methods on a home interface must contain the javax.ejb.CreateException exception. Action Change the create methods on the home interface to throw javax.ejb.CreateException.
CNTR5022E: The {1} home interface for the {0} bean has too many methods. The {2} method is not allowed.
Explanation According to the EJB specification, a home interface for a stateless session bean must have only one method. The method must be the create method. Action Remove the method from the home interface.
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.
Explanation According to the EJB specification, all methods that are defined on a home interface for a stateless session bean must start with the create string. Action Change the name of the method on the home interface so that it starts with the create string, or remove the method.
CNTR5024E: The {1} home interface for the {0} bean has a method that starts with the remove string. The {2} method is not allowed.
Explanation According to the EJB specification, you cannot define methods on an entity bean home interface that start with the remove string. Action Change the name of the method on the home interface so that it does not start with the remove string, or remove the method.
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.
Explanation According to the EJB specification, the bean class must implement an ejbCreate or init method for every create method for a home interface. Action Change the bean class to provide an ejbCreate or init method that corresponds to the method.
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.
Explanation According to the EJB specification, the entity bean class must implement an ejbCreate method for every create method for a home interface. Action Change the bean class to provide an ejbCreate method that corresponds to the method.
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.
Explanation According to the EJB specification, the return type of all ejbCreate methods for an entity bean class must be the primary key type. Action Change the return type of the method to the 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.
Explanation According to the EJB specification, the entity bean class must implement an ejbPostCreate method for every create method for a home interface. Action Change the bean class to provide an ejbPostCreate method that corresponds to the method.
CNTR5029E: The {2} method with the {3} return type on the {1} class for the {0} entity bean must return void.
Explanation According to the EJB specification, the return type of all ejbPostCreate methods for an entity bean class must be void. Action Change the return type of the method to 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.
Explanation The method of the home interface for the entity bean does not define a corresponding ejbFind method on the class. Action Change the bean class to provide an ejbFind method that corresponds to the method.
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.
Explanation According to the EJB specification, the return type of the ejbFindByPrimaryKey method for an entity bean class must be the primary key type. Action Change the return type of the method to the 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.
Explanation According to the EJB specification, the return type of all custom ejbFind methods for an entity bean class must be the primary key class, the java.util.Collection class, or the java.util.Enumeration class. Action Change the return type of the method to the 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.
Explanation TAccording to the EJB specification, the entity bean class must implement an ejbHome method for every home interface home method. Action Change the bean class to provide an ejbHome method that corresponds to the method.
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.
Explanation According to the EJB specification, the return type of the ejbHome methods for an entity bean class must match the corresponding home interface method. Action Change the return type of the method to the type that matches 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}
Explanation According to the EJB specification, the exceptions defined on the throws clause of a method are used by the container to determine which exceptions are application exceptions. If the exceptions on the throws clause of a method vary by interface, then unexpected exception behavior will occur for some of the interfaces. Action Change the application so that all methods with the same signature define the same exceptions on the throws clause.
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).
Explanation According to the EJB specification, the arguments and return types of all EJB remote business methods must be a valid type for RMI/IIOP. Action Change the application method to only use valid types for RMI/IIOP. Also, you can change the application to not use the interface as an EJB remote interface.
CNTR5101W: The {0} method on the {1} interface should not define the java.rmi.RemoteException exception on the throws clause.
Explanation According to the EJB specification, the throws clause of remote business interface methods should not include the java.rmi.RemoteException exception. Action Remove the RemoteException exception from the throws clause of the method. Also, you can change the interface to implement the java.rmi.Remote interface or change the application to not use the interface as an EJB remote interface.
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.
Explanation According to the EJB specification, an application exception must not be defined as a subclass of the java.rmi.RemoteException exception. Action Change the application so that there are no remote business interface methods that are defined with a java.rmi.RemoteException subclass on the throws clause.
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.
Explanation According to the EJB specification, an application exception for a component interface must not be defined as a subclass of the java.lang.RuntimeException exception. Action Change the application so that remote component interface methods are not defined with a java.lang.RuntimeException subclass on the throws clause.
CNTR5104E: The {0} method on the {1} interface must be defined with the java.rmi.RemoteException exception on the throws clause.
Explanation According to the EJB specification, for remote business interface methods that implement the java.rmi.Remote interface, the throws clause must include the java.rmi.RemoteException exception. Action Add the RemoteException exception to the throws clause of the method. Also, you can change the interface to not implement the java.rmi.Remote interface or change the application to not use the interface as an EJB remote interface.
CNTR5105E: The {0} interface is not a valid remote interface. The IDL name for the {1} method conflicts with the {2} method.
Explanation For remote interfaces, the Java Language to IDL Mapping specification states the following information: Methods that follow the JavaBeans design patterns for simple read-write properties or simple read-only properties are mapped to OMG IDL interface attributes. Both specified methods map to the same OMG IDL interface attribute. The interface is not a valid RMI/IIOP type. Action Change the application by either renaming or removing one of the conflicting methods.
CNTR5106E: The {0} method on the {1} class must not be declared as final for the {2} bean.
Explanation According to the EJB specification, all methods of the bean class and any superclass must not be declared as final when the bean class is exposed as a no-interface view. And, business methods must not be declared as final. Action Change the application so the method is not declared as final.
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.
Explanation According to the EJB specification, an application exception for an interface must be defined as a subclass of either the java.lang.Exception class or the java.lang.RuntimeException class. Action Change the application so that the exception is a subclass of either the java.lang.Exception class or the java.lang.RuntimeException class.
CNTR8990I: This message is an English-only Informational message: {0}.
Explanation This informational message is not translated. Action See message for details.
CNTR8991W: This message is an English-only Warning message: {0}.
Explanation This warning message is not translated. Action See message for details.
CNTR8992E: This message is an English-only Error message: {0}.
Explanation This error message is not translated. Action See message for details.
CNTR9100E: Exception {0}
Explanation A general exception condition has been discovered. Action Combine this information with additional exception messages to perform additional problem determination.
CNTR9101E: Incompatible options: {0} {1}
Explanation Two of the options specified are not compatible and cannot be specified together. Action Examine the usage statement, and remove one of the specified options.
CNTR9102E: Option {0} requires option {1}.
Explanation One of the options specified requires another option that has not been specified. Action Examine the usage statement, and specify the required option.
CNTR9103W: EJB timer {0} could not be found on server {1}.
Explanation The EJB timer specified does not exist on the server specified. The EJB timer might have expired, or it might have been cancelled. Action Verify that the identity of the EJB timer and the server name have been specified correctly. If the EJB timer does exist, the identity name is correct, and server name is correct, see any previous exceptions for more information.
CNTR9104W: EJB timer service {0} not available on server {1}.
Explanation The EJB timer service that is configured for the server specified is not available. The EJB timer service cannot start if there are no applications with TimedObject enterprise Java beans started on the server. Action Verify that an application with a TimedObject enterprise Java bean has been started on the server process specified.
CNTR9105E: Missing required filter.
Explanation One of the three filters must be specified: -all -timer -app Action Examine the usage statement, and specify one of the three filters.
CNTR9106E: Missing required server name.
Explanation A server name must be specified. Action Examine the usage statement, and specify a server name.
CNTR9240I: The {0} JAR file is not an enterprise bean level 3.0 module.
Explanation The listed jar file is not configured as a level 3.0 module. Action If this module should have contained enterprise bean level 3.0 components, check the Java source code annotations, or ejb-jar.xml configuration data.
CNTR9241I: The {0} JAR file has no level 3.0 enterprise beans with remote interfaces.
Explanation The listed jar file does not contain any level 3.0 enterprise beans with remote interfaces. Action If this module should have contained level 3.0 enterprise beans with remote interfaces, check the module's annotations or ejb-jar.xml configuration data.
CNTR9250E: The first parameter must be a fully qualified class name, JARfile, Web archive (WAR)file, or EAR file.
Explanation The first parameter must be a fully qualified class name, a JAR file, a WAR file, or an EAR file. JAR, WAR, and EAR files must include the complete directory path. Action Invoke the createEJBStubs command with the -help option to view the command syntax.
CNTR9251E: Unable to read from the {0} file.
Explanation The specified file could not be opened for read operation. Action Examine the file system permissions setting for this file.
CNTR9252E: The {0} option was specified multiple times.
Explanation An option may only be specified once per createEJBStubs command invocation. Action Invoke the createEJBStubs command with -help option to view the command syntax.
CNTR9253E: The {0} log file name parameter is not correct.
Explanation The log file name must point to a file, including the directory path. Also, the log file name may not begin with "-". Action Invoke the createEJBStubs command with the -help option to view the command syntax.
CNTR9254E: Unable to write to the {0} file.
Explanation The specified file could not be opened for write operation. Action Examine the file system permissions setting for this file.
CNTR9255E: The required log file name parameter is missing.
Explanation For option -logfile, the log file name must be provided as the next parameter Action Examine the usage statement and provide the required log file name parameter.
CNTR9256E: The {0} parameter is not recognized.
Explanation The parameter does not match any of the allowed input options. Action Invoke the createEJBStubs command with the -help option to view the command syntax.
CNTR9257E: Too many input parameters were specified.
Explanation The total number of allowed input parameters was exceeded. Action Invoke createEJBStubs command with the -help option to view the command syntax.
CNTR9258E: An unexpected exception was caught. The exception is: {0}
Explanation An unexpected exception occurred during command processing. Action Add the -verbose option to the createEJBStubs command invocation see more information.
CNTR9259E: No component interface specified for the {0} home.
Explanation Each configured home must have a component interface. Action Examine the configuration data for this home.
CNTR9260E: The {0} exception occured while setting up the user log file.
Explanation The exception was not expected. Action Examine the file system permissions settings.
CNTR9261E: Unable to create temporary file in the {0} directory.
Explanation A temporary file could not be created on the file system. Action Examine the file system permissions settings for the specified 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.
Explanation The specified class could not be loaded. Action Check for spelling errors, and make sure that all parent classes of this class are included in the input JAR file or EAR file, or are made available using the -cp option.
CNTR9263E: The {0} interface class could not be processed.
The {1} method parameter class was not found.
Explanation A method parameter or a method return value class of the listed class could not be loaded. Action Check to make sure that all classes passed as method parameters, or used as method return values, on methods of the listed class are included in the input Java achive (JAR) file or EAR file, or are made available using the -cp option.
CNTR9264E: The required class path name parameter was not specified.
Explanation For the -cp option, the class path name must be provided as the next parameter. Action Examine the usage statement and provide the required class path name parameter.
CNTR9265E: The {0} input file was not found.
Explanation The file specified as the first parameter was not found. Action Check the spelling and the read permissions of the specified file.
CNTR9266E: The createEJBStubs command could not rename the {0} file to the {1} file.
Explanation The specified file could not be renamed. Action Examine the file system permissions settings. Also, make sure target file does not already exist.
CNTR9267W: The createEJBStubs command could not delete the {0} file.
Explanation The specified file could not be deleted. Action Examine the file system permissions settings.
CNTR9268E: The {0} file name is not allowed for the -newfile option.
Explanation The name specified for the -newfile option is not allowed. Action Make sure the name is not the same as the input file.
CNTR9269W: The {0} EJB module does not have any enterprise beans configured.
Explanation EJB modules must contain one or more enterprise beans. Action Make sure that one or more enterprise beans are configured for this module. The enterprise beans must use either an ejb-jar.xml file , or source code annotations.
CNTR9270E: The update file name parameter is not a JAR, Web archive (WAR), or an EAR file type.
Explanation The update file name parameter must be a JAR, WAR, and EAR file type and include the file path. Action Invoke the createEJBStubs command with the -help option to view the command syntax.
CNTR9271E: The {0} directory could not be deleted.
Explanation The specified directory can not be deleted. Action Manually delete the directory.
CNTR9272E: The {0} output file cannot be found.
Explanation The specified output file cannot be found. Action Check the spelling and the write permissions for the file.
CNTR9273E: The {0} directory could not be created.
Explanation The specified directory can not be created. Action Ensure that the file system permissions allow for directory creation.
CNTR9274E: The createEJBStubs command cannot create the {0} file.
Explanation The specified file cannot be created on the file system. Action Examine the file system permissions settings for the specified directory.
CNTR9275E: The {0} output file already exists.
Explanation The specified output file must be a non-existing file. Action Specify a new output file name.
CNTR9276I: The {0} application has disabled the library directory. JAR and Web archive (WAR) files in the library directory will not be processed.
Explanation The application configuration data specified a library directory with a blank string for the library directory name. This action disables the library directory. Action If the library directory for this application should not be disabled, modify the application.xml configuration file in the application EAR file.
CNTR9277I: The {0} JAR or Web archive (WAR) file does not contain remote interface classes for a level 3.0 enterprise bean.
Explanation The specified JAR or WAR file does not contain any remote interface classes for a level 3.0 enterprise bean. Action If this module should contain remote interface classes for a level 3.0 enterprise bean, add these classes to the module.
CNTR9278E: The input type of a fully qualified class name is not compatible with the {0} option.
Explanation The input type of fully qualified class name is not compatible with the specified option. Action Examine the usage statement and either change the input type or remove the specified option.
CNTR9400I: The embeddable EJB container is scanning for EJB modules to start.
Explanation The embeddable container is scanning the classpath for valid EJB modules. Valid EJB modules contain an ejb-jar.xml file or EJB annotations. Action There is no user action required.
CNTR9401I: The embeddable EJB container is initializing.
Explanation The embeddable container must initialize before the user code can access the enterprise beans. Action There is no user action required.
CNTR9402E: An error occurred while initializing the embeddable EJB container {0}.
Explanation The process of scanning for EJB modules or initializing the embeddable EJB container failed and the container is no longer usable. Additional diagnostics might be found in FFDC output. Action Examine the exception type, and optionally, the FFDC output, to determine the cause of the initialization failure. A common reason for this error is an invalid EJB module is in the classpath.
CNTR9403E: The embeddable enterprise bean container cannot start multiple modules with the same file name: {0} and {1}
Explanation User code has directed the embeddable container to start multiple modules with the same file name. Action Specify a list of modules that does not have duplicate file names, or rename one of the modules with a unique file name.
CNTR9405I: The EJB module, {0}, is starting.
Explanation The embeddable EJB container is starting the identified EJB module. This includes binding the EJB factories and homes to the JNDI and executing any EJB code that has been specified to run on startup. Action There is no user action required.
CNTR9407W: There are no valid EJB modules to start.
Explanation The embeddable EJB container found no valid EJB modules to start. A valid EJB module contains a valid META-INF/ejb-jar.xml or classes with EJB annotations. This could be because no EJB module exists in the classpath, or that the javax.ejb.embeddable.modules property defined modules that do not exist. Action Review the classpath and the javax.ejb.embeddable.modules property to determine which EJB modules should be started.
CNTR9408W: The EJB module, {0} failed to stop. Exception: {1}
Explanation The embeddable EJB container failed to shutdown the EJB module due to the exception. The enterprise beans might still be bound into JNDI and are still accessible to clients. Future attempts to re-start that module might fail due to naming or other resource collisions. Action Resolve the failure by examining the exception, the logs, and the FFDC output. If other modules stop cleanly, examine the failing module.
CNTR9409W: The embeddable EJB container failed to stop. Exception: {0}
Explanation The embeddable EJB container failed to stop when the Close method was invoked due to the exception. Since this occurs after all the EJB modules have been stopped, this is a problem with the embeddable EJB container or its configuration. Action Resolve the failure by examining the exception, the logs, the FFDC output, and review the configuration of the embeddable EJB container.
CNTR9410I: The embeddable EJB container has closed.
Explanation The Close method has been invoked and the embeddable EJB container has completed its shutdown routine. Action There is no user action required.
CNTR9412E: An error occurred while shutting down the JNDI name space. Exception: {0}
Explanation The embeddable EJB container was unable to close the java:global namespace. This means that some EJB or other objects bound into the namespace could be leaked. Additionally, this could lead to JNDI problems if additional embeddable EJB container instances are created. Action Resolve the failure by examining the exception, the logs, and the FFDC output.
CNTR9413E: Failed to read in the configuration file from {0}
Explanation The embeddable EJB container failed to read the configuration properties from the specified file. This can occur if the file is not a properly formed properties file. Action Verify that the specified file exists on the file system and that it is a well formed properties file (i.e. <property_name>= <property_value>).
CNTR9414E: Failed to bind data source into JNDI using the name, {0}. Exception: {1}
Explanation The embeddable EJB container was unable to bind a javax.sql.DataSource instance into the JNDI namespace. Action Resolve the failure by examining the exception, the logs, and the FFDC output.
CNTR9415E: The embeddable EJB container properties for the {0} data source do not contain the property, name.
Explanation The properties that the embeddable EJB container uses contain a data source with no JNDI name specified. Action Add a name property for this data source to the properties file.
CNTR9416E: The embeddable EJB container properties for the {0} data source do not contain the property, className.
Explanation The properties that the embeddable EJB container uses contain a data source with no className specified. Action Add a className property for this data source to the properties file.
CNTR9417E: The embeddable EJB container properties for the {0} data source contain a {1} ConnectionPool.MaxConnections value that is not a positive numeric value or zero.
Explanation The properties that the embeddable EJB container uses contain a data source with a ConnectionPool.MaxConnections value that is not a positive numeric value or zero. Action Change the ConnectionPool.MaxConnections property value for this data source to be a positive numeric value or zero.
CNTR9419E: The embeddable EJB container failed to shutdown the JPA provider. Exception: {0}
Explanation An error during shutdown processing prevented the JPA provider from closing correctly due to the exception. This is indicative of another problem that should have occurred earlier in the logs. Future attempts to use JPA may fail. Action Resolve the failure by examining the exception, the logs, and the FFDC output to find and resolve the underlying problem.
CNTR9420E: The embeddable EJB container properties for the {0} data source contain a {1} ConnectionPool value that is not valid.
Explanation The properties that the embeddable EJB container uses contain a data source with a ConnectionPool value that is not valid. Action Change the ConnectionPool property value for this data source to a valid value. Valid values are names of a connection pool.
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.
Explanation The LTC resolver property was assigned an unsupported value. Action The LTC resolver property must be assigned a default value of Application 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.
Explanation The LTC unresolved action property was assigned an unsupported value. Action The LTC unresolved action property must be assigned a default value of Rollback or Commit.