EJB Container messages |
CNTR0001W: A Stateful SessionBean could not be passivated: {0} {1} {2}
Explanation:
The container was unable to passivate a stateful session bean
User Response:
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.
User Response:
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}.
User Response:
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.
User Response:
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}.
User Response:
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.
User Response:
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}.
User Response:
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.
User Response:
Look for prior error messages that indicate bean installation has failed.
CNTR0010W: NumberFormatException occurred while converting
Explanation:
The container was unable to process an environment entry due to a NumberFormatException.
User Response:
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:
Explanation:
The container encountered an invalid type for an environment entry.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
Examine stack trace to determine origin of exception. If exception originates from customer-written code, correct cause of exception. CMSG0002
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.
User Response:
Examine stack trace to determine origin of exception. If exception originates from customer-written code, correct cause of exception. CMSG0002
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.
User Response:
Examine stack trace to determine origin of exception. If exception originates from customer-written code, correct cause of exception. CMSG0002
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.
User Response:
Examine stack trace to determine origin of exception. If exception originates from customer-written code, correct cause of exception. CMSG0002
CNTR0022E: Transaction coordinator not available.
{0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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}.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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}".
User Response:
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. #
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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
Explanation:
The container caught a Throwable while trying to create a java:comp/env entry.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
None.
CNTR0061I: Read-only attribute on findByPrimaryKey method overridden to true for bean:
Explanation:
The user has specified that the findByPrimaryKey read-only attribute be overridden to true on all EntityBeans.
User Response:
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).
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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 method-level Transaction attributes.
Explanation:
A Session Bean or Home of a Session Bean with "Bean Managed Transactions" should not declare method transaction attributes.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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".
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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: Can not 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.
User Response:
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.
User Response:
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.
User Response:
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}.
User Response:
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 can not be created successfully.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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}.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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 has configured 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.
User Response:
None.
CNTR0099I: {0} service has initialized successfully.
Explanation:
The z/OS Controller Service for Stateful SessionBean support in DRS has initialized successfully.
User Response:
None.
CNTR0100E: Method {0} caught exception: {1}
Explanation:
An exception was caught in the specified method.
User Response:
None.
CNTR0101E: Method {0} token is null.
Explanation:
The specified method was passed a null servant token.
User Response:
None.
CNTR0102E: Method {0} entryKey is null.
Explanation:
The specified method was passed a null entryKey parameter.
User Response:
None.
CNTR0103E: Method {0} value is null.
Explanation:
The specified method was passed a null entryKey value.
User Response:
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.
User Response:
None.
CNTR0105E: Method {0} caught exception: {1} stoken = {3}.
Explanation:
The specified method caught an exception while processing the servant token.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
None.
CNTR0109E: Method {0} event parameter is null.
Explanation:
The specified method was passed a null event parameter.
User Response:
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.
User Response:
None.
CNTR0111E: Method {0} cannot convert event to byte array.
Explanation:
The specified method was unable to convert the event to a byte array.
User Response:
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.
User Response:
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.
User Response:
None.
CNTR0114I: SfDRSControllerInstance {0} received event REPLICATION_DOWN.
Explanation:
The specified SfDRSControllerInstance received event REPLICATION_DOWN.
User Response:
None.
CNTR0115I: SfDRSControllerInstance {0} received event IS_CONGESTED.
Explanation:
The specified SfDRSControllerInstance received event IS_CONGESTED.
User Response:
None.
CNTR0116I: SfDRSControllerInstance {0} received event NOT_CONGESTED.
Explanation:
The specified SfDRSControllerInstance received event NOT_CONGESTED.
User Response:
None.
CNTR9100E: Exception {0}
Explanation:
Some general exception condition has been discovered.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
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.
User Response:
Verify that an application with a TimedObject Enterprise Java Bean has been started on the server process specified.