Problem | 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. |
Problem | 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/. |
Problem | 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}. |
Problem | 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/. |
Problem | The container was unable to passivate an enterprise bean due to exception {2}. |
User response | Take action based upon message in exception {2}. |
Problem | 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/. |
Problem | 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}. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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}. |
Problem | 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/. |
Problem | 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. 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/ |
Problem | 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. 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/ |
Problem | 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. 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/ |
Problem | 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. 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/ |
Problem | 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/. |
Problem | The container failed to open the passivation directory. |
User response | Ensure that the passivation directory exists. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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}. |
Problem | 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}. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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/. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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}". |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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}. |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | These are the minimum and maximum pool size values that will be used for this bean type. |
User response | None. |
Problem | The user has specified that the findByPrimaryKey read-only attribute be overridden to true on all EntityBeans. |
User response | None. |
Problem | 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). |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
User response | Remove the transaction attributes for the methods of this bean or its home. |
Problem | 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. |
Problem | Use of Activity Sessions is not supported on EJB 1.1 modules. |
User response | Select "Once" or "Transaction" for Activate At policy. |
Problem | Activity Sessions are not supported on EJB 1.1 modules. |
User response | Select "Bean method" for Local Transactions Boundary. |
Problem | Local Transactions Resolution control, "ContainerAtBoundary" is not supported for EJB1.1 modules. |
User response | Select "Application" for Local Transactions Resolution control. |
Problem | 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. |
Problem | For Container-managed Transaction or Activity Session, the Local Transactions Resolution control must be ContainerAtBoundary. |
User response | Set Local Transactions Resolution control to "ContainerAtBoundary". |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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}. |
Problem | 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}. |
Problem | 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. |
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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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/. |
Problem | 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. |
Problem | 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. |
Problem | 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}. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
User response | None. |
Problem | The z/OS Controller Service for Stateful SessionBean support in DRS has initialized successfully. |
User response | None. |
Problem | An exception was caught in the specified method. |
User response | None. |
Problem | The specified method was passed a null servant token. |
User response | None. |
Problem | The specified method was passed a null entryKey parameter. |
User response | None. |
Problem | The specified method was passed a null entryKey value. |
User response | None. |
Problem | The specified method was unable to convert the entryKey parameter to a byte array. |
User response | None. |
Problem | The specified method caught an exception while processing the servant token. |
User response | None. |
Problem | The specified method was unable to obtain a proxy for processing the servant token. |
User response | None. |
Problem | The specified method was unable to convert the servant token to a byte array. |
User response | None. |
Problem | The specified method caught an exception while acquiring a proxy for processing the servant token. |
User response | None. |
Problem | The specified method was passed a null event parameter. |
User response | None. |
Problem | The specified method was unable to convert the passed entryKey value to a byte array. |
User response | None. |
Problem | The specified method was unable to convert the event to a byte array. |
User response | None. |
Problem | 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. |
Problem | The specified SfDRSControllerInstance received event REPLICATION_UP. |
User response | None. |
Problem | The specified SfDRSControllerInstance received event REPLICATION_DOWN. |
User response | None. |
Problem | The specified SfDRSControllerInstance received event IS_CONGESTED. |
User response | None. |
Problem | The specified SfDRSControllerInstance received event NOT_CONGESTED. |
User response | None. |
Problem | 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. |
User response | None. |
Problem | 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. |
User response | None. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | Change the EJB java:comp/env context environment entry of type Boolean to either "true" or "false". |
Problem | All ejb-name elements within the container-transaction element must match valid ejb-name elements within the enterprise-beans element. |
User response | 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. |
Problem | All ejb-name elements within the method-permission element must match valid ejb-name elements within the enterprise-beans element. |
User response | 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. |
Problem | All ejb-name elements within the exclude-list element must match valid ejb-name elements within the enterprise-beans element. |
User response | 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. |
Problem | The injection processors registered with the injection engine failed to identify and collect all the annotations associated with the class. |
User response | Correct the ejb-jar.xml and annotations on the class. |
Problem | A message-driven bean must define a message listener interface using XML, annotations, or the implements clause of the Enterprise JavaBeans (EJB) class. |
User response | Check the XML and Java source for the {0} MDB class and specify the message listener interface. |
Problem | Simple JNDI binding name cannot be mixed with specific JNDI bindings for a given bean or home. |
User response | Correct the bindings file settings for the bean or home in the specified module. |
Problem | Depending on the bean type, an enterprise bean must have at least one component, business, Web service endpoint, or message listener interface configured. |
User response | Correct the ejb-jar.xml file or source code annotation configuration settings for this bean. |
Problem | Stateless session beans cannot have message listener interfaces configured. Stateful session beans cannot have either of these interface types configured. |
User response | Correct the ejb-jar.xml file or source code annotation configuration settings for this bean. |
Problem | Entity beans cannot have any of these interface types configured. |
User response | Correct the ejb-jar.xml file or source code annotation configuration settings for this bean. |
Problem | Message-driven beans cannot have any of these interface types configured. |
User response | Correct the ejb-jar.xml file or source code annotation configuration settings for this bean. |
Problem | A message-driven bean binding must exist in the binding file for each message driven bean. |
User response | Check the ejb-jar-bnd.xml binding file for the MDB and ensure that a binding entry exists. |
Problem | The local binding name for the specified bean or home does not begin with ejblocal:. |
User response | Correct the local binding name for the bean or home in the specified module. |
Problem | The remote binding name for the given bean or home cannot begin with ejblocal:. |
User response | Correct the remote binding name for the bean or home in the specified module. |
Problem | JNDI binding names must not contain blank strings. |
User response | Correct the ejb-jar-bnd.xml bindings file to give this bean a valid JNDI binding name. |
Problem | Each business interface can have a single JNDI binding name configured. |
User response | Correct the ejb-jar-bnd.xml bindings file to give this bean a single JNDI binding name. |
Problem | Each business interface JNDI binding must have a valid business interface class configured. |
User response | Correct the ejb-jar.xml file or source code annotations to configure a valid business interface class. |
Problem | Each home JNDI binding must have a matching home interface class configured. |
User response | Correct the ejb-jar.xml file or source code annotations to configure a valid home interface class. |
Problem | All EJB bindings require an enterpriseBean stanza within the ibm-ejb-jar-bnd.xml file. |
User response | Check the ibm-ejb-jar-bnd.xml file and ensure that all EJB bindings include an enterprise bean stanza. |
Problem | All bindings for message driven beans require a jca-adapter stanza within the message-driven binding. |
User response | Check the binding file and ensure that all message-driven bindings include a jca-adapter stanza. |
Problem | All bindings for message driven beans require a jca-adapter stanza containing an activation-spec-binding-name value. |
User response | Check the binding file and ensure that all message-driven bindings include a jca-adapter stanza with an activation-spec-binding-name value. |
Problem | All bindings for message driven beans require a jca-adapter stanza containing a destination-binding-name value. |
User response | Check the binding file and ensure that all message-driven bindings include a jca-adapter stanza with a destination-binding-name value. |
Problem | The bindings file contains either a simple syntax error, or a semantic violation. |
User response | 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. |
Problem | The bindings file contains either a simple syntax error, or a semantic violation. |
User response | Correct the bindings file error and reinstall the application. |
Problem | The Connection Factory resource that is required by this bean is not configured. The CMP entity bean will not function. |
User response | Create the required Connection Factory resource by ensuring that the proper data source is selected for CMP use in the administrative console. |
Problem | An error has occurred during the initialization and start up processes for the bean. |
User response | 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. |
Problem | The annotations that are identified in this error message are in conflict with each other. Do not specify these annotations on the same method. |
User response | Change the Java source code by removing one or both of the annotations from the specified method. Then, reinstall the application. |
Problem | A specified role can be specified once in a @RolesAllowed annotation. |
User response | Change the Java source code by removing the duplicate roles from this annotation. Then, reinstall the application. |
Problem | The annotations that are identified in this error message are in conflict with each other. Do not specify these annotations on the same class. |
User response | Change the Java source code by removing one, or both, of the annotations from the specified class. Then, reinstall the application. |
Problem | A given role can be specified once in a @RolesAllowed annotation.. |
User response | Change the Java source code by removing the duplicate roles from this annotation. Then, reinstall the application. |
Problem | The component that is attempting to reference this bean has a configuration error. The component has specified an unsupported interface for this bean. |
User response | 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. |
Problem | 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. |
User response | 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. |
Problem | Stateful sessions beans cannot be configured for both failover support and extended-scope persistence context support. |
User response | Eliminate one of these two configuration settings for this bean. Then, reinstall the application. |
Problem | Enterprise beans must implement all of the methods that are specified on their interface classes. |
User response | Correct the bean implementation to include all of the required methods. Then, reinstall the application. |
Problem | Timer beans must implement a timeout method, which has a single parameter of the javax.ejb.Timer type. |
User response | Correct the bean implementation to include the required parameter. Then, reinstall the application. |
Problem | There might be an error in the configuration extensions file for the module, or one of the two beans might not exist. |
User response | Correct the configured inheritance relationship in the extensions XML file for the module or supply the missing bean implementation. |
Problem | Timer beans, which inherit from the TimedObject interface, must implement the following timeout method: ejbTimeout |
User response | Correct the bean implementation to include the required method. Then, reinstall the application. |
Problem | Timer beans may only implement a single timeout method. |
User response | Correct the bean implementation to include only one timeout method. Then, reinstall the application. |
Problem | Timer beans must provide an implementation for the configured timeout method. |
User response | Correct the bean implementation to include the required timeout method. Then, reinstall the application. |
Problem | Timer beans must configure only one timeout method. |
User response | Correct the bean configuration to specify a single timeout method. Then, reinstall the application. |
Problem | Timeout methods must not create application exceptions.. |
User response | Correct the timeout method implementation to not create application exceptions. Then, reinstall the application. |
Problem | Timeout methods must return void. |
User response | Correct the timeout method implementation to return void. Then, reinstall the application. |
Problem | Timeout methods must not be declared as static or final. |
User response | Correct the implementation declaration for the timeout method. Then, reinstall the application. |
Problem | The interface has been bound at the specified naming location. |
User response | Use the specified naming location when attempting to look up this interface. |
Problem | Because the enterprise bean has multiple interfaces, each binding name must be extended to make it unique. |
User response | 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. |
Problem | The enterprise bean name might be incorrect, or a binding might have been specified for a bean that does not exist. |
User response | Correct the binding file. Then, reinstall the application. |
Problem | Each enterprise bean must specify a bean type such as stateless session bean, message driven bean, and so on. |
User response | Correct the Java source code annotation or the ejb-jar.xml configuration setting for this bean. Then, reinstall the application. |
Problem | Each enterprise bean must specify a unique binding location. |
User response | Correct the binding file for one of these two beans so that each bean has a unique binding location. |
Problem | 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. |
User response | Eliminate the duplicate interceptor class from the interceptor class list. Or, change the interceptor class name, if an incorrect name was specified. |
Problem | An interceptor class can be either a class-level or a method-level interceptor, but not both types. |
User response | Eliminate the interceptor class from either the class-level interceptor list or the method-level interceptor list. |
Problem | The interceptor class can be either a default interceptor or a method-level interceptor, but not both types. |
User response | Eliminate the interceptor class from either the default interceptor list or the method-level interceptor list. |
Problem | 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. |
User response | 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. |
Problem | The interceptor-binding element is using an exclude-class-interceptors element, which must specify a method-name tag. |
User response | Correct the deployment descriptor by adding a method-name tag. |
Problem | Style 3 and style 4 interceptor-binding elements cannot be specified on the same method of an enterprise bean. |
User response | Eliminate either the style 3 or the style 4 interceptor-binding element for the specified method of this bean. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | 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. |
Problem | The Enterprise JavaBeans 3.0 specification does not allow an interceptor method to be final or static. |
User response | Remove the final or static modifier from this interceptor method. |
Problem | The Enterprise JavaBeans 3.0 specification requires that around-invoke methods have the following signature: Object <METHOD>(InvocationContext) throws Exception |
User response | Correct the method signature of this interceptor. |
Problem | The Enterprise JavaBeans 3.0 specification requires that lifecycle methods of an enterprise bean have the following signature: void <METHOD>() |
User response | Correct the method signature for this interceptor. |
Problem | The Enterprise JavaBeans 3.0 specification requires that lifecycle methods of an interceptor class have the following signature: void <METHOD> (InvocationContext) |
User response | Correct the method signature for this interceptor. |
Problem | The Enterprise JavaBeans 3.0 specification requires that @Remove annotations be applied to business methods of a stateful session bean. |
User response | Either relocate the @Remove annotation to a business method of this bean, or change the specified method to be a business method. |
Problem | The Enterprise JavaBeans 3.0 specification requires a matching ejbCreate<METHOD> to be the initialization method of a stateful session bean class. This requirement exists for stateful session beans that are written for the EJB 2.1 or earlier-level application programming interface (API)." |
User response | Remove the @Init annotation or the init-method element in ejb-jar.xml file from the specified method of this bean. |
Problem | 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<METHOD> method of the home or local home interface must be specified if there is any ambiguity. |
User response | Use the value element of the @Init annotation to specify the name of the create<METHOD> on one of the two specified methods. This approach will remove the ambiguity. |
Problem | The init-method element specifies a method name that is not a public method of the enterprise bean class. |
User response | Correct either the method name or the method signature in the init-method element to specify a public method of this bean. |
Problem | An enterprise bean level 3.0 interceptor class cannot not be found or loaded. |
User response | Verify that the interceptor class is installed and configured correctly. |
Problem | The specified method name is not a method of the interceptor class. |
User response | Correct either the method name or method signature to specify one of the methods of this interceptor class. |
Problem | The method-name element is not allowed in a style 1 interceptor-binding element. |
User response | Correct the interceptor-binding to be a style 2 interceptor-binding element or remove the method-name element. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | Correct the deployment descriptor or annotation so that the method is the correct type of life cycle callback interceptor. |
Problem | 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. |
User response | Correct the deployment descriptor or annotation so that the method is the correct type of life cycle callback interceptor. |
Problem | 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. |
User response | Correct the deployment descriptor or annotation so that the method is the correct type of life cycle callback interceptor. |
Problem | According to the Enterprise JavaBeans (EJB) specification, a style 3 or style 4 interceptor-binding must use a <method-name> tag to specify the name of a method that is found in one of the business interfaces of the enterprise bean. |
User response | 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. |
Problem | According to the Enterprise JavaBeans (EJB) specification, only one style 1 interceptor-binding can be used for the module. |
User response | Correct deployment descriptor so that only one style 1 interceptor-binding is used for the module. |
Problem | According to the Enterprise JavaBeans (EJB) specification, only one style 2 interceptor-binding can be used for each enterprise bean. |
User response | Correct deployment descriptor so that only one style 2 interceptor-binding is used for the enterprise bean. |
Problem | According to the Enterprise JavaBeans (EJB) specification, only one style 3 interceptor-binding can be used for each method of an enterprise bean. |
User response | Correct deployment descriptor so that only one style 3 interceptor-binding is used for the method of an enterprise bean. |
Problem | 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. |
User response | Correct deployment descriptor so that only one style 4 interceptor-binding is used for the method of an enterprise bean. |
Problem | According to the Enterprise JavaBeans (EJB) specification, a remote home interface must be provided when a remote component interface is provided. |
User response | Change the application configuration to provide a remote home interface for the {0} bean. |
Problem | According to the Enterprise JavaBeans (EJB) specification, a local home interface must be provided when a local component interface is provided. |
User response | Change the application configuration to provide a local home interface for the {0} bean. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the bean class must be defined as public. |
User response | Define the {1} bean class as public. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the bean class must not be defined as final. |
User response | Do not define the {1} bean class as a final class. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the bean class must not be defined as abstract. |
User response | Do not define the {1} bean class as an abstract class. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the bean class must be defined as a top level class. |
User response | Define the {1} bean class as a top level class. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the bean class must have a public constructor that does not take parameters. |
User response | Change the {1} bean class to have a public constructor that does not take parameters. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the bean class must not define the finalize method. |
User response | Do not define the finalize method in the bean class. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the entity bean class must implement the javax.ejb.EntityBean class. |
User response | Change the {1} bean class to implement the javax.ejb.EntityBean class. |
Problem | 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. |
User response | Change the name of the {2} business method so that it does not start with ejb. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the configured business and component interfaces must be Java interfaces. |
User response | Change the {0} bean configuration to provide Java interfaces. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the configured business interfaces must not extend any interface in the javax.ejb package. |
User response | 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. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the configured local interfaces must not extend the javax.rmi.Remote interface. |
User response | 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. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the configured local component interface must extend the javax.ejb.EJBLocalObject interface. |
User response | 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. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the configured remote component interface must extend the javax.ejb.EJBObject interface. |
User response | 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. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the configured local home interface must extend the javax.ejb.EJBLocalHome interface. |
User response | 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. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the configured remote home interface must extend the javax.ejb.EJBHome interface. |
User response | 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. |
Problem | According to the Enterprise JavaBeans (EJB) specification, all create methods on a home interface must return the component interface. |
User response | Change the {2} method on the {1} home interface to return the component interface. |
Problem | According to the Enterprise JavaBeans (EJB) specification, all home interfaces must define at least one create method. |
User response | Change the {1} home interface to define a create method. |
Problem | According to the Enterprise JavaBeans (EJB) specification, all create methods on a home interface must return the component interface. |
User response | Change the {2} method on the {1} home interface to return the {3} component interface. |
Problem | 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. |
User response | Change the {2} method on the {1} home interface to throw javax.ejb.CreateException. |
Problem | 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. |
User response | Remove the {2} method from the {1} home interface. |
Problem | 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. |
User response | Change the name of the {2} method on the {1} home interface so that it starts with the create string, or remove the method. |
Problem | According to the Enterprise JavaBeans (EJB) specification, you cannot define methods on an entity bean home interface that start with the remove string. |
User response | 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. |
Problem | 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. |
User response | Change the {3} bean class to provide an ejbCreate or init method that corresponds to the {2} method. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the entity bean class must implement an ejbCreate method for every create method for a home interface. |
User response | Change the {3} bean class to provide an ejbCreate method that corresponds to the {2} method. |
Problem | 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. |
User response | Change the return type of the {2} method to the primary key class. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the entity bean class must implement an ejbPostCreate method for every create method for a home interface. |
User response | Change the {3} bean class to provide an ejbPostCreate method that corresponds to the {2} method. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the return type of all ejbPostCreate methods for an entity bean class must be void. |
User response | Change the return type of the {2} method to void. |
Problem | The {2} method of the {1} home interface for the {0} entity bean does not define a corresponding ejbFind method on the {3} class. |
User response | Change the {3} bean class to provide an ejbFind method that corresponds to the {2} method. |
Problem | 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. |
User response | Change the return type of the {2} method to the primary key class. |
Problem | 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. |
User response | Change the return type of the {2} method to the primary key class, the java.util.Collection class, or the java.util.Enumeration class. |
Problem | TAccording to the Enterprise JavaBeans (EJB) specification, the entity bean class must implement an ejbHome method for every home interface home method. |
User response | Change the {3} bean class to provide an ejbHome method that corresponds to the {2} method. |
Problem | 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. |
User response | Change the return type of the {2} method to the {4} type. |
Problem | 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. |
User response | 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. |
Problem | According to the Enterprise JavaBeans (EJB) specification, the throws clause of remote business interface methods should not include the java.rmi.RemoteException exception. |
User response | 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. |
Problem | According to the Enterprise JavaBeans (EJB) specification, an application exception must not be defined as a subclass of the java.rmi.RemoteException exception. |
User response | 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. |
Problem | 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. |
User response | Change the application so that remote component interface methods are not defined with a java.lang.RuntimeException subclass on the thrwos clause. |
Problem | 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. |
User response | 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. |
Problem | 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. |
User response | Change the application by either renaming or removing one of the conflicting methods. |
Problem | This informational message is not translated. |
User response | See message for details. |
Problem | This warning message is not translated. |
User response | See message for details. |
Problem | This error message is not translated. |
User response | See message for details. |
Problem | Some general exception condition has been discovered. |
User response | Combine this information with additional exception messages in order to perform additional problem determination. |
Problem | 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. |
Problem | One of the specified options requires another option, that has not been specified. |
User response | Examine the usage statement and specify the required option. |
Problem | 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. |
Problem | 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. |
Problem | The listed jar file is not configured as a level 3.0 module. |
User response | If this module should have contained enterprise bean level 3.0 components, check the Java source code annotations, or ejb-jar.xml configuration data. |
Problem | The listed jar file does not contain remote interfaces. |
User response | If this module should have contained remote interfaces, check the module's annotations or ejb-jar.xml configuration data. |
Problem | The first parameter must be a jar or ear file, including file path. |
User response | Invoke command with -help option to view command syntax. |
Problem | The file could not be opened for read operation. |
User response | Examine the file system permissions setting for this file. |
Problem | An option may only be specified once per command invocation. |
User response | Invoke command with -help option to view command syntax. |
Problem | The log file name must point to a file, including path. Also, the log file name may not begin with "-". |
User response | Invoke command with -help option to view command syntax. |
Problem | The file could not be opened for write operation. |
User response | Examine the file system permissions setting for this file. |
Problem | For option -logfile, the log file name must be provided as the next parameter |
User response | Examine the usage statement and provide the required log file name parameter. |
Problem | The parameter does not match any of the expected input values. |
User response | Invoke command with -help option to view command syntax. |
Problem | The total number of parameters allowed was exceeded. |
User response | Invoke command with -help option to view command syntax. |
Problem | An unexpected exception occured during command processing. |
User response | Add the -verbose option to see more information. |
Problem | Each configured home must have a component interface. |
User response | Examine the configuraion data for this home. |
Problem | An exception occured setting up the user's log file. |
User response | Examine the file system's permissions settings. |
Problem | The file could not be created on the file system. |
User response | Examine the file system permissions settings for the directory specified in "TMP" environment variable. |
Problem | The listed class could not be loaded. |
User response | Check to make sure that all parent classes of this class are included the input jar or ear file. |
Problem | A method parameter or a method return value class of the listed class could not be loaded. |
User response | 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. |
Problem | For option -cp, the classpath must be provided as the next parameter |
User response | Examine the usage statement and provide the required classpath parameter. |
Problem | The file specified as the first parameter was not found. |
User response | Check the spelling as well as the read permissions of the file. |
Problem | The file could not be renamed. |
User response | Examine the file system''s permissions settings. Also, make sure file "{1}" does not currently exist. |
Problem | The file could not be deleted. |
User response | Examine the file system's permissions settings. |
Problem | The name specified for the -newfile option is not allowed. |
User response | Make sure the name is not the same as the input file. |
Problem | EJB modules must contain one or more enterprise beans. |
User response | 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. |