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. |
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/. |
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}. |
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/. |
Explanation | The container was unable to passivate an enterprise bean due to exception {2}. |
Action | Take action based upon message in exception {2}. |
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/. |
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}. |
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. |
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. |
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. |
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/. |
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/. |
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/. |
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/. |
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}. |
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/. |
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. CMSG0002 |
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. CMSG0002 |
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. CMSG0002 |
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. CMSG0002 |
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/. |
Explanation | The container failed to open the passivation directory. |
Action | Ensure that the passivation directory exists. |
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. |
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. |
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. |
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}. |
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}. |
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. |
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. |
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/. |
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/. |
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/. |
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. |
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/. |
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. |
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/. |
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/. |
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. |
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. |
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. |
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/. |
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}". |
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. |
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. |
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. |
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/. |
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. |
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/. |
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/. |
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/. |
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}. |
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/. |
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. |
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. |
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. |
Explanation | These are the minimum and maximum pool size values that will be used for this bean type. |
Action | None. |
Explanation | The user has specified that the findByPrimaryKey read-only attribute be overridden to true on all EntityBeans. |
Action | None. |
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). |
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. |
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. |
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. |
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. |
Explanation | A Session Bean or Home of a Session Bean with "Bean Managed Transactions" should not declare method transaction attributes. |
Action | Remove the transaction attributes for the methods of this bean or its home. |
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. |
Explanation | Use of Activity Sessions is not supported on EJB 1.1 modules. |
Action | Select "Once" or "Transaction" for Activate At policy. |
Explanation | Activity Sessions are not supported on EJB 1.1 modules. |
Action | Select "Bean method" for Local Transactions Boundary. |
Explanation | Local Transactions Resolution control, "ContainerAtBoundary" is not supported for EJB1.1 modules. |
Action | Select "Application" for Local Transactions Resolution control. |
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. |
Explanation | For Container-managed Transaction or Activity Session, the Local Transactions Resolution control must be ContainerAtBoundary. |
Action | Set Local Transactions Resolution control to "ContainerAtBoundary". |
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/. |
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. |
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. |
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. |
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. |
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. |
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/. |
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/. |
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/. |
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}. |
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}. |
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. |
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. |
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. |
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. |
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/. |
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. |
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. |
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}. |
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. |
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. |
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. |
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. |
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. |
Action | None. |
Explanation | The z/OS Controller Service for Stateful SessionBean support in DRS has initialized successfully. |
Action | None. |
Explanation | An exception was caught in the specified method. |
Action | None. |
Explanation | The specified method was passed a null servant token. |
Action | None. |
Explanation | The specified method was passed a null entryKey parameter. |
Action | None. |
Explanation | The specified method was passed a null entryKey value. |
Action | None. |
Explanation | The specified method was unable to convert the entryKey parameter to a byte array. |
Action | None. |
Explanation | The specified method caught an exception while processing the servant token. |
Action | None. |
Explanation | The specified method was unable to obtain a proxy for processing the servant token. |
Action | None. |
Explanation | The specified method was unable to convert the servant token to a byte array. |
Action | None. |
Explanation | The specified method caught an exception while acquiring a proxy for processing the servant token. |
Action | None. |
Explanation | The specified method was passed a null event parameter. |
Action | None. |
Explanation | The specified method was unable to convert the passed entryKey value to a byte array. |
Action | None. |
Explanation | The specified method was unable to convert the event to a byte array. |
Action | None. |
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. |
Explanation | The specified SfDRSControllerInstance received event REPLICATION_UP. |
Action | None. |
Explanation | The specified SfDRSControllerInstance received event REPLICATION_DOWN. |
Action | None. |
Explanation | The specified SfDRSControllerInstance received event IS_CONGESTED. |
Action | None. |
Explanation | The specified SfDRSControllerInstance received event NOT_CONGESTED. |
Action | None. |
Explanation | The application has configured 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. |
Explanation | Some general exception condition has been discovered. |
Action | Combine this information with additional exception messages in order to perform additional problem determination. |
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. |
Explanation | One of the specified options requires another option, that has not been specified. |
Action | Examine the usage statement and specify the required option. |
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. |
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. |