WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS


CNTR

CNTR0001W: A Stateful SessionBean could not be passivated: {0} {1} {2}
Explanation The container was unable 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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0003W: A Stateful SessionBean could not be activated: {0} {1}
{2}
Explanation The container failed to activate a stateful session bean from storage due to exception {2}.
Action Take action based upon message in exception {2}.
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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0005W: An enterprise bean could not be passivated: {0} {1} {2}
Explanation The container was unable to passivate an enterprise bean due to exception {2}.
Action Take action based upon message in exception {2}.
CNTR0006W: EJBObject "{0}" could not be connected to the ORB.
Explanation On an attempt to activate a stateful bean the container failed to connect a deserialized stub (reference) object.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 due to exception {2}.
Action Take action based upon message in exception {2}.
CNTR0009W: An attempt to access bean "{0}" failed because it was not previously installed or problems occurred during its installation.
Explanation An attempt was made to access an enterprise bean which has not been installed in the container.
Action Look for prior error messages that indicate 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 an invalid type for an environment entry.
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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0013W: Unable to map exception.
{0}
{1}
Explanation The container was unable to map exception {0} to a valid CORBA exception.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0014W: StatefulBeanReaper thread was interrupted; terminating.
{0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 message in exception {1}.
CNTR0017W: Security collaborator threw unexpected exception.
Exception data: {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0018E: EJB threw an unexpected (non-declared) exception. Exception data: {0}
Explanation An exception, not declared on the EJB method signature, was thrown when the EJB container attempted to invoke an EJB method.
Action Examine stack trace to determine origin of exception. If exception originates from customer-written code, correct cause of exception. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CNTR0019E: EJB threw an unexpected (non-declared) exception during invocation of method "{1}". Exception data: {0}
Explanation An exception, not declared on the EJB method signature, was thrown when the EJB container attempted to invoke this EJB method.
Action Examine stack trace to determine origin of exception. If exception originates from customer-written code, correct cause of exception. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "{1}" on bean "{2}". Exception data: {0}
Explanation An exception, not declared on the EJB method signature, was thrown when the EJB container attempted to invoke this EJB method.
Action Examine stack trace to determine origin of exception. If exception originates from customer-written code, correct cause of exception. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CNTR0021E: EJB threw an unexpected (non-declared) exception while invoking a method on bean "{1}". Exception data: {0}
Explanation An exception, not declared on the EJB method signature, was thrown when the EJB container attempted to invoke this EJB method.
Action Examine stack trace to determine origin of exception. If exception originates from customer-written code, correct cause of exception. If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/
CNTR0022E: Transaction coordinator not available.
{0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 message in IOException to determine action to take. Ensure 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 message in IOException to determine action to take. Ensure 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 {0}.
Action Specify a datasource for the entity bean or a default datasource for the module.
CNTR0027W: Failed to commit connection:
{0}
Explanation SQLException occurred while trying to commit a datasource connection.
Action Take action recommended in database messages reference for the message associated with exception {0}.
CNTR0028W: Failed to close connection:
{0}
Explanation SQLException occurred while trying to close a datasource connection.
Action Take action recommended in database messages reference for the message associated with exception {0}.
CNTR0031W: Error starting CMP bean {0}:
{1}
Explanation Entity bean may have been bound to a datasource using a undefined or incorrect datasource name. If correct datasource name, the datasource itself maybe configured incorrectly.
Action If CNTR0026W precedes this message, you need to provide the name of the datasource. If CNTR0026W did not precede this message, check datasource name that appears in the CNTR0032W message that follows this message. If a name not found exception occurred, you probably provided an incorrect datasource name. If correct datasource name is provided, then check the datasource configuration. For example, you may have specified incorrect database name, user id, or password in the datasource configuration.
CNTR0032W: Error creating CMP persister using datasource: {0}
Explanation This message immediately follows CNTR0031W message and provides the datasource name used when starting the entity bean.
Action Take the action described for message CNTR0031W.
CNTR0033E: EJB container ignoring caught unexpected exception: {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0034I: ContainerEJBException.getExceptionChain is returning an incomplete list of exceptions.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0035E: EJB container caught {0} and is throwing {1}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 configured for EJB 1.x container managed persistence has attempted to invoke methods on a bean instance for finder method processing.
Action Redeploy the bean and try again.
CNTR0037E: Prepared statement does not map to connection.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 by using either the TX_NOT_SUPPORTED, TX_NEVER, or the TX_SUPPORTS transaction attribute. The transaction updated a CMP entity bean and is storing the update to persistent store. If a concurrent transaction uses the CMP entity bean with the same primary key value, the updates of one transaction may 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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0040E: Finder failure as a result of exception {0}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 such a huge collection of entity beans.
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 contained within a work load managed server. This combination is not supported.
Action Either change the Enterprise Bean to use a different Commit Option, 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 enterprise bean {0} is not supported. The default action (Option C) taken may not be what you wanted to occur. The combination of Activation Policy and Load Policy is WebSphere way of implementing commit option A, B, and C in the EJB specification.
Action You need to redeploy enterprise bean using a valid combination 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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 "{0}".
Action Specify a connection factory binding when installing bean "{0}".
CNTR0047E: Bean is attempting to use interface or method "{0}" in a situation prohibited by the EJB specification.
Explanation The method "{0}" is disallowed per the EJB Specification 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 execute in the context of a transaction. # - Invoking the getCallerPrincipal and isCallerInRole methods is disallowed in the message-driven bean methods because the Container does not have a client security context. # - Invoking the getRollbackOnly and setRollbackOnly methods is disallowed 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 unavailable to message-driven beans with container- managed transaction demarcation. # - Invoking getEJBHome or getEJBLocalHome is disallowed in message-driven bean methods because there are no EJBHome or EJBLocalHome objects for message-driven beans. #
Action The user must not invoke method "{0}" in this environment.
CNTR0048W: Bean''s finder method "{0}" erroneously specifies a finder collection timeout scope of zero.
Explanation The finder method "{0}" has finder collection timeout scope specified but with zero as the value.
Action Provide a non-zero value if 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. This combination is not supported.
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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 inactivity timeout value of {1} seconds.
Action This can be a normal occurrence if client goes away and leaves a transaction active. If client is still active, you need to have administrator determine whether to change Client or Transaction Inactivity Timeout value.
CNTR0052W: LRU thread was interrupted. Terminating. {0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0053W: Caught an exception during LRU sweep {0} {1}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0054W: Exception thrown by discard strategy {0} {1}.
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 while trying to create a java:comp/env entry.
Action Take action based upon message associated with exception {2}.
CNTR0056W: Failed to get the wrapper for a bean. Bean:
{0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0057W: Minimum pool size specified for bean {0} not a valid integer: {1} Default used instead.
Explanation Only a positive integer may be specified for the minimum pool size. The default value will be used instead.
Action Change the value 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 may be specified for the maximum pool size. The default value will be used instead.
Action Change the value 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. Default values will be used for min and max.
Action Change the max size to be greater than or equal to the min size.
CNTR0060I: (Min,Max) pool size is ({0},{1}) for bean {2}
Explanation These are the minimum and maximum pool size values that will be used for this bean type.
Action None.
CNTR0061I: Read-only attribute on findByPrimaryKey method overridden to true for bean: <All>
Explanation The user has specified that the findByPrimaryKey read-only attribute be overridden to true on all EntityBeans.
Action None.
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 min/max value(s).
Action Ensure that an equals sign is present between the bean name and the min/max value(s).
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 A deployment descriptor with invalid syntax may be at fault.
Action Verify the binding information in the deployment descriptor for the 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 EJB activated within an activity session should only participate in serial transactions. Having varying transaction attributes, like REQUIRES for one method and REQUIRES_NEW or NOT_SUPPORTED for another can cause this error.
Action Review the transaction attributes assigned to the EJB methods and verify the method call sequences 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 CMP beans.
Action Using assembly tool, change "Resolution Control" to "ContainerAtBoundary" within 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 Local transaction boundary of activity session is invalid for Message Driven Beans.
Action Change 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 EJB specification states that a Session Bean or Home of a Session Bean with "Bean Managed Transactions" must not declare method transaction attributes. Since the Session Bean will use Bean Managed Transactions, the Container Managed method-level transaction attributes have no meaning.
Action Remove the transaction attributes for the methods of this bean or its 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 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 Use of Activity Sessions is not supported on EJB 1.1 modules.
Action Select "Once" or "Transaction" for 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 1.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 EJB1.1 modules.
Action Select "Application" for Local Transactions Resolution control.
CNTR0072E: Bean "{0}" attempted to use an invalid "Activate at" policy with a container managed Activity Session.
Explanation Beans configured to use container managed Activity Session 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 container managed Activity Session support.
CNTR0073E: Bean "{0}" attempted to use an invalid Local Transactions Resolution control.
Explanation For Container-managed Transaction or Activity Session, the Local Transactions Resolution control must be ContainerAtBoundary.
Action Set 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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0075E: The user-provided class "{0}" needed by the EnterpriseBean could not be found or loaded.
Explanation One or more of the bean's implementation, home interface, remote interface, local interface, or other similar class could not be found or loaded.
Action Check to ensure that the bean implementation class, home interface, remote interface, and other classes 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 J2EE component may have specified binding information that is not valid.
Action Verify the binding information in the deployment descriptor for J2EE 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 J2EE component may have specified binding information that is not valid.
Action Verify the binding information in the deployment descriptor for J2EE 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 The user can disable access intent processing for custom finders by using JVM and bean level properties or setting the access intent of method to Read-Only.
CNTR0080E: EJB Timer Service is not available for EJB implementing the javax.ejb.TimedObject interface: {0}.
Explanation The specified EJB implementation requires the EJB Timer Service, which has either been disabled or failed to start.
Action See previous messages to determine why the EJB Timer Service failed to 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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0083E: Creation of a message endpoint failed:
{0}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CNTR0084E: Method {0} of MDB {1} is deployed with an incorrect transaction attribute.
Explanation A method of a MDB is required to be deployed with a transaction attribute of either requires, not supported, or bean managed.
Action Redeploy application using either requires, not supported, or bean managed as the transaction attribute for method {0} for MDB {1}.
CNTR0085E: MDB {0} must implement method {1} of interface {2}.
Explanation Resource adapter is calling method {1} on interface {2} and the method is not implemented by MDB {0}.
Action Determine if MDB was deployed to use the correct resource adapter. If bound to the correct resource adapter, then change MDB {0} to provide an implementation for method {1} of interface {2}.
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 passed a XAResource object as one of the parameters of createEndpoint method. However, the resource adapter life cyle manager encountered error which prevented it from setting up transaction recovery for this resource adapter. Consequently the endpoint cannot be created successfully.
Action Have the administrator examine the log for a prior error message indicating the setup failure for MDB {1} that was bound to resource adapter {0}. The administrator must 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 was passed a XAResource object. However, transaction recovery for this resource adapter was not setup since the resource adapter indicated it does not support XA transactions. For that reason, the resource adapter is not allowed to pass an XAResource object to the createEndpoint method.
Action Have the Resource Adaptor vendor correct resource adapter {0} configuration or implementation.
CNTR0088E: The user-provided class "{0}" may not implement the javax.ejb.TimedObject interface.
Explanation EJB 1.x, 2.0, and Stateful Session beans may not implement the javax.ejb.TimedObject interface.
Action Change the EJB deployment to version 2.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 EJB Specification does not allow the configured transaction attribute for the specified EJB method. See the EJB Specification for further details.
Action Change the deployment descriptor to specify an allowed transaction attribute for the EJB method.
CNTR0090E: WebServiceRef binding failed for {0} : {1}
Explanation This exception is unexpected. The cause is not immediately known.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
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 J2EE component may have specified binding information that is not valid.
Action Verify the binding information in the deployment descriptor for J2EE component is correct.
CNTR0092W: Attempted to access EnterpriseBean {0}, that has not been started.
Explanation An attempt has been made to access an EnterpriseBean of an application that has not been installed, not been started, or failed to start.
Action Verify the application has been installed and started. If the application has been installed and started, see the previous messages regarding the failure of the EnterpriseBean 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 {0}.
Action Take action recommended in the message associated with exception {1}.
CNTR0094E: Entity bean "{0}" has been configured with a BeanCache LoadPolicy that will reload the Entity at an interval, but the Entity bean is not configured for EJB 2.x container managed persistence".
Explanation Bean cache load policies that result in the Entity bean being reloaded at intervals are only supported for EJB 2.x container managed persistence beans.
Action Either change the Bean Cache LoadPolicy to a value supported by the bean type, or change to bean to use EJB 2.x container managed persistence.
CNTR0095W: EJB module configuration for session bean "{0}" is missing override of memory to memory replication settings.
Explanation The administrator has configured a session bean "{0}" to override the memory to memory replication settings at the EJB module level, but no memory to memory replication settings is provided at the EJB module level.
Action The administrator should either disable the override at EJB module level or provide the memory to memory replication settings for this session bean.
CNTR0096W: Application configuration for session bean "{0}" is missing override of memory to memory replication settings.
Explanation The administrator has configured a session bean "{0}" to override the memory to memory replication settings at the application level, but no memory to memory replication settings is provided at the application level.
Action The administrator should either disable the override at application level or provide the memory to memory replication settings for this session bean.
CNTR0097W: Memory to memory replication settings for EJB container is missing.
Explanation The administrator has configured stateful session bean failover using memory to memory replication, but the memory to memory replication settings are missing.
Action The administrator should either disable stateful session bean failover or provide the memory to memory replication settings 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 cause a synchronization with persistent storage prior to invocation of custom findBy methods. This behavior is not compliant with the EJB 2.0 specification but can improve performance.
Action None.
CNTR0099I: {0} service has initialized successfully.
Explanation The z/OS Controller Service for Stateful SessionBean support in DRS has initialized successfully.
Action None.
CNTR0100E: Method {0} caught exception: {1}
Explanation An exception was caught in the specified method.
Action None.
CNTR0101E: Method {0} token is null.
Explanation The specified method was passed a null servant token.
Action None.
CNTR0102E: Method {0} entryKey is null.
Explanation The specified method was passed a null entryKey parameter.
Action None.
CNTR0103E: Method {0} value is null.
Explanation The specified method was passed a null entryKey value.
Action None.
CNTR0104E: Method {0} cannot convert entryKey to byte array.
Explanation The specified method was unable to convert the entryKey parameter to a byte array.
Action None.
CNTR0105E: Method {0} caught exception: {1} stoken = {3}.
Explanation The specified method caught an exception while processing the servant token.
Action None.
CNTR0106E: Method {0} cannot acquire proxy for stoken = {1}.
Explanation The specified method was unable to obtain a proxy for processing the servant token.
Action None.
CNTR0107E: Method {0} cannot convert token to byte array : stoken = {1}.
Explanation The specified method was unable to convert the servant token to a byte array.
Action None.
CNTR0108E: Method {0} caught exception {1} while acquiring proxy for token = {3}.
Explanation The specified method caught an exception while acquiring a proxy for processing the servant token.
Action None.
CNTR0109E: Method {0} event parameter is null.
Explanation The specified method was passed a null event parameter.
Action None.
CNTR0110E: Method {0} cannot convert value to byte array.
Explanation The specified method was unable to convert the passed entryKey value to a byte array.
Action None.
CNTR0111E: Method {0} cannot convert event to byte array.
Explanation The specified method was unable to convert the event to a byte array.
Action None.
CNTR0112E: The user-provided class "{0}" must implement the "{1}" interface.
Explanation EJB specification requires Message Driven beans to implement the message listener interface for the messaging type it supports.
Action Change class "{0}" so that it implements the interface "{1}" as required by EJB specification.
CNTR0113I: SfDRSControllerInstance {0} received event REPLICATION_UP.
Explanation The specified SfDRSControllerInstance received event REPLICATION_UP.
Action None.
CNTR0114I: SfDRSControllerInstance {0} received event REPLICATION_DOWN.
Explanation The specified SfDRSControllerInstance received event REPLICATION_DOWN.
Action None.
CNTR0115I: SfDRSControllerInstance {0} received event IS_CONGESTED.
Explanation The specified SfDRSControllerInstance received event IS_CONGESTED.
Action None.
CNTR0116I: SfDRSControllerInstance {0} received event NOT_CONGESTED.
Explanation The specified SfDRSControllerInstance received event NOT_CONGESTED.
Action None.
CNTR0117I: Container-managed ejbStore() call will be bypassed on bean: "{0}" if it has not been modified in the current transaction.
Explanation The application is configured for this bean to prevent the EJB container from invoking the bean's ejbStore() method if the bean has not been modified. This behavior is not compliant with the EJB 2.0 specification but can improve performance.
Action None.
CNTR0118I: Container pre- and post-method processing for all local and local home methods will be bypassed on bean: "{0}".
Explanation The application is configured for this bean to streamline the pre- and post-method processing performed on the local home and local business methods. This behavior is not compliant with the EJB 2.0 specification but can improve performance.
Action None.
CNTR0119E: The user-provided class "{0}" may not implement the com.ibm.websphere.ejbcontainer.LightweightLocal interface. Reason code = {1}.
Explanation Only EJB 2.x 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 either an EJB 1.x or CMP 1.x Entity bean. 3 - The EJB does not have a local interface defined.
Action Change the EJB to be of 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 EJB java:comp/env context environment entry of type Boolean should be assigned a value of either "true" or "false". Any other value will result in "false", but may be an indication of a problem in configuration. The application may 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 Enterprise JavaBeans (EJB) class.
Action Check the XML and Java source for the {0} MDB class and specify the message listener interface.
CNTR0130E: When a simple Java Naming and Directory Interface (JNDI) binding name is specified for a bean or home, specific JNDI bindings cannot be specified. The {0} bean in The {1} module either must use a simple JNDI binding name or specific JNDI bindings, but not use both options.
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 Java Naming and Directory Interface (JNDI) binding name provided for a local home or bean does not begin with ejblocal:. The {2} local binding name that is specified for the home or {0} bean in the {1} module does not begin with ejblocal:.
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 Java Naming and Directory Interface (JNDI) binding name that is provided for a remote home or bean begins with ejblocal:. The {2} remote binding name that is specified for the home or {0} bean in the {1} module cannot begin with ejblocal:.
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 Java Naming and Directory Interface (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 Java Naming and Directory Interface (JNDI) binding names specified for the {3} 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 Java Naming and Directory 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 Java Naming and Directory Interface (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 Enterprise JavaBeans (EJB) binding with the {0} Java Naming and Directory Interface (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 Enterprise JavaBeans (EJB) binding with the {0} Java Naming and Directory Interface (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 Enterprise JavaBeans (EJB) binding with the {0} Java Naming and Directory Interface (JNDI) name has a jca-adapter stanza that does not contain an activation-spec-binding-name value.
Explanation All bindings for message driven beans require a jca-adapter stanza containing an activation-spec-binding-name value.
Action Check the binding file and ensure that all message-driven bindings include a jca-adapter stanza with an activation-spec-binding-name value.
CNTR0145E: The Enterprise JavaBeans (EJB) binding with the {0} Java Naming and Directory Interface (JNDI) name has a jca-adapter stanza that does not contain a destination-binding-name value.
Explanation All bindings for message driven beans require a jca-adapter stanza containing a destination-binding-name value.
Action Check the binding file and ensure that all message-driven bindings include a jca-adapter stanza with a destination-binding-name value.
CNTR0146E: The {0} bindings file contained in the {1} module has a configuration error at line number: {2}, column number: {3}.
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} Java Naming and Directory Interface (JNDI). This Connnection 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 up processes 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 can not 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 that are 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.
Explanation Timer beans must implement a timeout method, which has a single parameter of the javax.ejb.Timer type.
Action Correct the bean implementation to include the required parameter. Then, reinstall the application.
CNTR0159E: The {0} module has a configuration error in the inheritance relationship that is specified between the {1} parent bean and the {2} child bean.
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 that is 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.
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 Enterprise JavaBeans 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.
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 {1} enterprise bean has an interceptor-order element which specifies the following interceptor-order list: {0}. 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 {2} enterprise bean specifies method-level interceptors for the {1} method with the following interceptor-order list: {0}. 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 Enterprise JavaBeans 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 specifies an around-invoke interceptor signature, which is not correct.
Explanation The Enterprise JavaBeans 3.0 specification requires that around-invoke methods have the following signature: Object &lt;METHOD&gt;(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 Enterprise JavaBeans 3.0 specification requires that lifecycle methods of an enterprise bean have the following signature: void &lt;METHOD&gt;()
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 Enterprise JavaBeans 3.0 specification requires that lifecycle methods of an interceptor class have the following signature: void &lt;METHOD&gt; (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 Enterprise JavaBeans 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&lt;METHOD&gt; method only when the bean conforms to the Enterprise JavaBeans (EJB) 2.1 or earlier specification levels. Therefore, it cannot be applied to the {0} method of the {1} enterprise bean.
Explanation The Enterprise JavaBeans 3.0 specification requires a matching ejbCreate&lt;METHOD&gt; 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 application programming interface (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&lt;METHOD&gt; 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 Enterprise JavaBeans 3.0 specification requires that the name of the adapted create&lt;METHOD&gt; 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&lt;METHOD&gt; 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 Enterprise JavaBeans 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 Enterprise JavaBeans 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 Enterprise JavaBeans 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 Enterprise JavaBeans (EJB) specification, a style 3 or style 4 interceptor-binding must use a &lt;method-name&gt; 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 Enterprise JavaBeans (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 Enterprise JavaBeans (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 Enterprise JavaBeans (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 Enterprise JavaBeans (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.
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 Enterprise JavaBeans (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 {0} 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 Enterprise JavaBeans (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 {0} bean.
CNTR5003E: The {1} bean class for the {0} bean is not defined as public.
Explanation According to the Enterprise JavaBeans (EJB) specification, the bean class must be defined as public.
Action Define the {1} bean class as public.
CNTR5004E: The {1} bean class for the {0} bean is defined as final.
Explanation According to the Enterprise JavaBeans (EJB) specification, the bean class must not be defined as final.
Action Do not define the {1} bean class as a final class.
CNTR5005E: The {1} bean class for the {0} bean is defined as abstract.
Explanation According to the Enterprise JavaBeans (EJB) specification, the bean class must not be defined as abstract.
Action Do not define the {1} 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 Enterprise JavaBeans (EJB) specification, the bean class must be defined as a top level class.
Action Define the {1} 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 Enterprise JavaBeans (EJB) specification, the bean class must have a public constructor that does not take parameters.
Action Change the {1} 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 Enterprise JavaBeans (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 Enterprise JavaBeans (EJB) specification, the entity bean class must implement the javax.ejb.EntityBean class.
Action Change the {1} 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 Enterprise JavaBeans (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 {2} 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 Enterprise JavaBeans (EJB) specification, the configured business and component interfaces must be Java interfaces.
Action Change the {0} 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 Enterprise JavaBeans (EJB) specification, the configured business interfaces must not extend any interface in the javax.ejb package.
Action Change {1} interface to not extend the {2} interface. Also, you can change the {0} bean configuration to not specify the {1} 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 Enterprise JavaBeans (EJB) specification, the configured local interfaces must not extend the javax.rmi.Remote interface.
Action Change {1} interface to not extend the javax.rmi.Remote interface. Also, you can change the {0} bean configuration to not specify the {1} 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 Enterprise JavaBeans (EJB) specification, the configured local component interface must extend the javax.ejb.EJBLocalObject interface.
Action Change {1} interface to extend the javax.ejb.EJBLocalObject interface. Also, you can change the {0} bean configuration to not specify the {1} 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 Enterprise JavaBeans (EJB) specification, the configured remote component interface must extend the javax.ejb.EJBObject interface.
Action Change {1} interface to extend the javax.ejb.EJBObject interface. Also, you can change the {0} bean configuration to not specify the {1} 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 Enterprise JavaBeans (EJB) specification, the configured local home interface must extend the javax.ejb.EJBLocalHome interface.
Action Change the {1} interface to extend the javax.ejb.EJBLocalHome interface or change the {0} bean configuration to not specify the {1} 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 Enterprise JavaBeans (EJB) specification, the configured remote home interface must extend the javax.ejb.EJBHome interface.
Action Change the {1} interface to extend the javax.ejb.EJBHome interface or change the {0} bean configuration to not specify the {1} 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 Enterprise JavaBeans (EJB) specification, all create methods on a home interface must return the component interface.
Action Change the {2} method on the {1} 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 Enterprise JavaBeans (EJB) specification, all home interfaces must define at least one create method.
Action Change the {1} 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 Enterprise JavaBeans (EJB) specification, all create methods on a home interface must return the component interface.
Action Change the {2} method on the {1} home interface to return the {3} component interface.
CNTR5021E: The {2} method of the {1} interface, which has been configured as a home interface for the {0} bean, does not define the javax.ejb.CreateException exception on the throws clause.
Explanation According to the Enterprise JavaBeans (EJB) specification, the throws clause of all create methods on a home interface must contain the javax.ejb.CreateException exception.
Action Change the {2} method on the {1} 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 Enterprise JavaBeans (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 {2} method from the {1} 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 Enterprise JavaBeans (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 {2} method on the {1} 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 Enterprise JavaBeans (EJB) specification, you cannot define methods on an entity bean home interface that start with the remove string.
Action Change the name of the {2} method on the {1} 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 Enterprise JavaBeans (EJB) specification, the bean class must implement an ejbCreate or init method for every create method for a home interface.
Action Change the {3} bean class to provide an ejbCreate or init method that corresponds to the {2} 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 Enterprise JavaBeans (EJB) specification, the entity bean class must implement an ejbCreate method for every create method for a home interface.
Action Change the {3} bean class to provide an ejbCreate method that corresponds to the {2} 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 Enterprise JavaBeans (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 {2} 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 Enterprise JavaBeans (EJB) specification, the entity bean class must implement an ejbPostCreate method for every create method for a home interface.
Action Change the {3} bean class to provide an ejbPostCreate method that corresponds to the {2} 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 Enterprise JavaBeans (EJB) specification, the return type of all ejbPostCreate methods for an entity bean class must be void.
Action Change the return type of the {2} 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 {2} method of the {1} home interface for the {0} entity bean does not define a corresponding ejbFind method on the {3} class.
Action Change the {3} bean class to provide an ejbFind method that corresponds to the {2} 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 Enterprise JavaBeans (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 {2} 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 Enterprise JavaBeans (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 {2} 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 Enterprise JavaBeans (EJB) specification, the entity bean class must implement an ejbHome method for every home interface home method.
Action Change the {3} bean class to provide an ejbHome method that corresponds to the {2} 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 Enterprise JavaBeans (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 {2} method to the {4} type.
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 Enterprise JavaBeans (EJB) specification, the arguments and return types of all EJB remote business methods must be a valid type for RMI/IIOP.
Action Change the {1} application method to only use valid types for RMI/IIOP. Also, you can change the application to not use the {2} 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 Enterprise JavaBeans (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 Enterprise JavaBeans (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 Enterprise JavaBeans (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 thrwos 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 Enterprise JavaBeans (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.
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 Some general exception condition has been discovered.
Action Combine this information with additional exception messages in order to perform additional problem determination.
CNTR9101E: Incompatible options: {0} {1}
Explanation Two of the specified options are not compatible and may not 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 specified options 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 specified EJB Timer does not exist on the server specified. The EJB Timer may have expired or been cancelled.
Action Verify that the EJB Timer identity and server name have been specified correctly. If the EJB Timer does exist and the identity and server name has been specified correctly, then see any previous exceptions.
CNTR9104W: EJB Timer service {0} not available on server {1}.
Explanation The EJB Timer service configured for the specified server is not available. The EJB Timer service may not 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.
CNTR9240W: Warning: 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.
CNTR9241W: Warning: Jar file "{0}" has no remote interfaces.
Explanation The listed jar file does not contain remote interfaces.
Action If this module should have contained remote interfaces, check the module's annotations or ejb-jar.xml configuration data.
CNTR9250E: Error: First parameter must be jar or ear file.
Explanation The first parameter must be a jar or ear file, including file path.
Action Invoke command with -help option to view command syntax.
CNTR9251E: Error: Unable to read from file "{0}".
Explanation The file could not be opened for read operation.
Action Examine the file system permissions setting for this file.
CNTR9252E: Error: Option "{0}" specified multiple times.
Explanation An option may only be specified once per command invocation.
Action Invoke command with -help option to view command syntax.
CNTR9253E: Error: Incorrect log file name "{0}".
Explanation The log file name must point to a file, including path. Also, the log file name may not begin with "-".
Action Invoke command with -help option to view command syntax.
CNTR9254E: Error: Unable to write to file "{0}".
Explanation The file could not be opened for write operation.
Action Examine the file system permissions setting for this file.
CNTR9255E: Error: Required log file 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: Error: Parameter "{0}" is not recognized.
Explanation The parameter does not match any of the expected input values.
Action Invoke command with -help option to view command syntax.
CNTR9257E: Error: Too many input parameters specified.
Explanation The total number of parameters allowed was exceeded.
Action Invoke command with -help option to view command syntax.
CNTR9258E: Error: Unexpected exception "{0}" occurred.
Explanation An unexpected exception occured during command processing.
Action Add the -verbose option to see more information.
CNTR9259E: Error: No component interface for home "{0}".
Explanation Each configured home must have a component interface.
Action Examine the configuraion data for this home.
CNTR9260E: Error: Exception setting up user log file:
"{0}".
Explanation An exception occured setting up the user's log file.
Action Examine the file system's permissions settings.
CNTR9261E: Error: Unable to create temporary file.
Explanation The file could not be created on the file system.
Action Examine the file system permissions settings for the directory specified in "TMP" environment variable.
CNTR9262E: Error: Interface class "{0}" could not be loaded.
Explanation The listed class could not be loaded.
Action Check to make sure that all parent classes of this class are included the input jar or ear file.
CNTR9263E: Error: Interface class "{0}" could not be processed.
Method parameter class "{1}" 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 the input jar or ear file.
CNTR9264E: Error: Required classpath parameter is missing.
Explanation For option -cp, the classpath must be provided as the next parameter
Action Examine the usage statement and provide the required classpath parameter.
CNTR9265E: Error: Input file "{0}" was not found.
Explanation The file specified as the first parameter was not found.
Action Check the spelling as well as the read permissions of the file.
CNTR9266E: Error: Unable to rename file "{0}" to file "{1}".
Explanation The file could not be renamed.
Action Examine the file system''s permissions settings. Also, make sure file "{1}" does not currently exist.
CNTR9267W: Warning: Unable to delete file "{0}".
Explanation The file could not be deleted.
Action Examine the file system's permissions settings.
CNTR9268E: Error: The name "{0}" is not allowed for -newfile.
Explanation The name specified for the -newfile option is not allowed.
Action Make sure the name is not the same as the input file.
CNTR9269E: The {0} Enterprise JavaBeans (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.
Reference topic    

Terms of Use | Feedback

Last updated: Feb 18, 2011 4:35:06 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ejs.container.container.html

© Copyright IBM Corporation 2006, 2010. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)