Objaśnienie | Used to dump the exception callstack when the persistence manager threw the original exception. |
Działanie | See the preceeding error message which caused this call stack dump. |
Objaśnienie | Used to print the messageText of the exception(s) nested (a.k.a. chained) in the original exception. |
Działanie | Read the chain of exceptions to help determine the problem. The last one is often the root cause of the problem. |
Objaśnienie | An exception occurred, please look at the nested exception for the reason. |
Działanie | Read the chained exception for detailed information. |
Objaśnienie | DataAccessSpec (part of the Deploy Tool-generated xxxAdapterBinding.java file) was not found for the given data access spec name and given Access Intents (for example, optimistic vs. pessimistic, read vs. update). Either the backend datasource does not support the SQLStatement needed for the AccessIntent, or the deployed code is of earlier version which does not contain the new functions. |
Działanie | Check in the generated xxxAdapterBinding class for the bean type being used, which is where the data access spec is defined. May need to redeploy the ear. |
Objaśnienie | Error in one or more of the .java source code files generated by the Deploy Tool. |
Działanie | Check these generated files for errors. Check whether you specified correct information when using the Deploy Tool. |
Objaśnienie | There is no Relationship defined for a given relationship role name. |
Działanie | Check the code generation of ConcretexxxBean (generated by the Deploy tool)to see if the given role name is properly defined there. |
Objaśnienie | There is no EJB Object in the context. |
Działanie | Check EJB Object availability in the context. |
Objaśnienie | The data is already deleted from the datastore (for example, your relational database). |
Działanie | Check if the data is already deleted from datastore. |
Objaśnienie | Trasaction is null from the context. |
Działanie | Check the availability of transaction in the context. The absence of a transaction usually indicates an internal logic error within WebSphere's Container component. |
Objaśnienie | Missing the finder in executeFinderForLink. |
Działanie | Check the code generation of ConcretexxxBean (generated by the Deploy tool)to see if the given finder method is properly defined there. |
Objaśnienie | The PMHomeInfo does not exist for a given name. |
Działanie | Check in the generated xxxAdapterBinding class (generated by the Deploy tool) to see if the given name is the abstract schema name generated into this code. |
Objaśnienie | Exception occurred when creating DataAccessSpec from the generated xxxAdapterBinding class (generated by the Deploy tool). |
Działanie | Check the generated xxxAdapterBinding class. |
Objaśnienie | The current backend id in the ibm-ejb-jar-bnd.xml does not have a matching deployed xxxAdapterBinding class (generated by the Deploy tool). |
Działanie | Check the deploy process. |
Objaśnienie | The current backend id in the ibm-ejb-jar-bnd.xml is null. |
Działanie | Check the deploy process. |
Objaśnienie | The current backend id in the ibm-ejb-jar-bnd.xml does not match the datasource it connected to. |
Działanie | Check the deploy process or the datasource definition. |
Objaśnienie | See the nested exception . |
Działanie | Check the nested exception to find out the reason. |
Objaśnienie | See the nested exception . |
Działanie | Check the nested exception to find out the reason. Usually it is because of something wrong with the datasource configuration. |
Objaśnienie | The data in the datasource is changed for the read-only bean. |
Działanie | Re-drive the trasaction or choose a different read-verification strategy. |
Objaśnienie | The state of the concrete bean is not correct for a given lifecycle method. |
Działanie | 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/. |
Objaśnienie | Exception occurred when look up of AccessIntenetService. |
Działanie | Check if the runtime AccessIntentService is defined. See "AccessIntent" in the documentation. |
Objaśnienie | Exception occured when ejbCreate/ejbStore/ejbRemove a bean , which load as read intent. |
Działanie | Check the AccessIntent setting for the method which loads the bean. |
Objaśnienie | Illegal state due to ejbRemove/ejbLoad/ejbStore called before calling ejbPostCreateor ejbActivate. |
Działanie | Check the deployed code or container for problems |
Objaśnienie | Illegal state due to ejbActivate/ejbCreate called to a ready bean. |
Działanie | Check the deployed code or container for problems |
Objaśnienie | Exception occured when ejbCreate/ejbStore/ejbRemove a bean , which is class level read only |
Działanie | Check the ibm-ejb-jar-ext for DataCache setting. |
Objaśnienie | Exception occured when ejbFind<>/ejbLoad a bean , which is class level read only, but the AccessIntent is set as for update. |
Działanie | Check the ibm-ejb-jar-ext for DataCache setting and AccessIntent and the AccessIntent setting for the method which loads the bean.. |
Objaśnienie | Get NULL AccessIntent from EntityContext. |
Działanie | Check with container component owner. |
Objaśnienie | The asscociations framework did not find a legal link type in the associated metadata |
Działanie | The associations framework and Deploy tool code generation are probably out of synch |
Objaśnienie | Container threw RemoveException when PersistenceManager tried to cascade remove to an associated bean |
Działanie | Try to determine the underlying cause of the RemoveException |
Objaśnienie | The DataAccessSpec for a finder method included a CompleteAssociationList but the xxxDataCacheEntry was not generated to make use of it. |
Działanie | Check the xxxAdapterBinding class and the xxxCacheEntry class(generated by the Deploy tool) for the bean type being used. Examine the input you gave to the Deploy Tool for this bean type. |
Objaśnienie | Caused when client code sends a PMCacheInvalidationRequest with a beanAbstractSchemaName. Either someone forgot to configure this bean type's "Lifetime In Cache Usage" or the request's beanAbstractSchemaName is for the wrong bean type. |
Działanie | Use the Application Assembly Tool to update your Entity Bean's configuration; on the "IBM Extensions" tab, set "Lifetime In Cache Usage" to an appropriate value other than "OFF". Or find the application code that sends the PMCacheInvalidationRequest and correct the beanAbstractSchemaName value used. |
Objaśnienie | Caused when client code sends an incorrect JMS message to the PM cache invalidate topic. |
Działanie | Find the application code that sends to the PM cache invalidate topic and fix it so it follows the documented interface for "Cache Invalidation". |
Objaśnienie | Caused when client code sends an incorrect JMS message to the PM cache invalidate topic. |
Działanie | Find the application code that sends to the PM cache invalidate topic and set the beanHomeJNDIName parameter to a correct value. |
Objaśnienie | Caused when CMP entity beans do not insure that each uses a unique bean home JNDI name and a feature of WebSphere is used which depends on this uniqueness. |
Działanie | Examine the bean home JNDI name used by installed beans (these can be found the deployment descriptor and other places) and get rid of any duplicate names. |
Objaśnienie | An error occured while processing a WebSphere PM cache invalidation request, specifically a primary key object serialized into a byte[]. If the bean's key class is at fault, there should be other errors elsewhere as well. |
Działanie | Confirm that your bean's primary key class correctly serializes & deserializes itself, as required by the EJB 2.x specification. If it does, report this error to IBM. |
Objaśnienie | Caused when client code sends an incorrect JMS message to the PM cache invalidate topic. |
Działanie | Find the application code that sends to the PM cache invalidate topic and fix it so it follows the documented interface for "Cache Invalidation". Especially, insure that the key objects you pass in the request are of the correct type for the beanHomeJNDIName you pass in the request. |
Objaśnienie | An error occurred while setting up for PM cache invalidation. This occurs during server startup. It is likely an internal error in the WAS-install-time configuration of the JMS TopicConnectionFactory or TopicDestination we use. |
Działanie | 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/. |
Objaśnienie | Internal PMCacheInvalidationMessageHandler thread caught an exception while receiving invalidation messages. |
Działanie | 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/. |
Objaśnienie | An exception was thrown while requesting a connection from the Resource Adapter |
Działanie | Please verify the J2EE Connector (also called the Resource Adapter) configured for use with the current bean type is a valid ResourceAdapter. In this case, it is the ConnectionFactory which is actually failing. |
Objaśnienie | An exception was thrown while requesting a connection from the Resource Adapter |
Działanie | Please verify the J2EE Connector (also called the Resource Adapter) configured for use with the current bean type is a valid ResourceAdapter. In this case, it is the connection.getInteraction() or the interaction itself which is actually failing. |
Objaśnienie | Although there are other reasons for this exception, the most typical cause for EJB 2.0 applications is a deadlock with another transaction in this or another application on this or another computer. Deadlock here means you are attempting to obtain a lock on data in the database when some other transaction already has a conflicting lock. Locks are obtained when you try to access the data for a bean, or sometimes for a nearby bean in the same database table. |
Działanie | Correct the application logic or data access pattern for this application or the one you conflict with so the conflict does not occur. For more information on when and how locks are obtained, see the documentation for your particular database or other datastore. To learn how to configure your applications to avoid such a deadlock, see the documentation for WebSphere Application Server, under "Access Intents". |
Objaśnienie | The ResourceAdapter configured for this bean type indicates that the supplied key is a duplicate of one already in the datastore. This may happen during normal application execution. |
Działanie | Your application should be written to accept this exception and communicate this to your end user. |
Objaśnienie | Another application probably changed the data in the database while you were using it. Since you chose to use optimistic concurrency control (e.g., Access Intent = optimisticUpdate), you chose to take the chance this might happen to gain other benefits. |
Działanie | Your application should be written to handle this exception and either retry the update or communicate the failure to your end user and let them decide whether to retry the update. |
Objaśnienie | The bean type being used is part of an inheritance hierarchy, and a finder method returned data for a bean subclass not recognized by the Extractor subclasses (generated by the Deploy Tool) |
Działanie | Ensure you have a deployment descriptor entry for all possible bean types in this inheritance hierarchy. Then make sure the Deploy Tool generated an xxxExtractor class for all of these bean types. |
Objaśnienie | There was a low-level error in getting data returned from your Resource Adapter (or the DataStore behind it), as the result of a finder or select method. A common source of error is that the type of the field/column does not match the Deployment Descriptor section defining this bean type, or some other error in the mapping of bean attributes to backend data. |
Działanie | Verify that the mapping information (bean attribute types to datastore types) is correct. If correct, examine the xxxExtractor classes (generated by the Deploy Tool), especially the extractXXX() methods. |
Objaśnienie | There was a low-level error in navigating through or otherwise using data returned from your Resource Adapter (or the DataStore behind it), as the result of a finder or select method. |
Działanie | Review the documentation for the ResourceAdapter you are using to see if it is compatible for use as the datastore for CMP 2.0 beans. If you are using the Relational Resource Adapter (the default), it is an internal error. |
Objaśnienie | An attempt has been made to call a method which will not work until after bean data has been extracted from this result row using xxxExtractor.extractData(). |
Działanie | 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/. |
Objaśnienie | The data retrieved from the datastore for a bean does not match the generated Extractor code for that bean type, so that the method cannot properly process the data for use as an entity bean. |
Działanie | Internal error in the tooling that generated the Extractor for this bean type. No user error during data mappping or other configuration should cause this error to occur. |
Objaśnienie | There was a low-level error in iterating through the javax.resource.cci.ResultSet returned from your Resource Adapter (or the DataStore behind it), as the result of a finder or select method. |
Działanie | Review the documentation for the ResourceAdapter you are using to see if it is compatible for use as the datastore for CMP 2.0 beans. If you are using the Relational Resource Adapter (the default), it is an internal error. |
Objaśnienie | Calling next() on the javax.resource.cci.ResultSet returned by the ResourceAdapter failed. |
Działanie | Review the documentation for the ResourceAdapter you are using to see if it is compatible for use as the datastore for CMP 2.0 beans. If you are using the Relational Resource Adapter (the default), it is an internal error. |
Objaśnienie | Internal error in the logic which creates and initialized a ResultCollection. |
Działanie | 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/. |
Objaśnienie | The connection used to obtain the ResultSet could have been broken,which sometimes (if you are lucky) triggers a close of ResultSets instead of some more obscure error. It could also be that ConnectionManager (J2C) has prematurely closed a connection (this would be an internal error perhaps caused by a bad fixpack). |
Działanie | Check for a dropped connection to your datastore. Review the documentation for the ResourceAdapter you are using to see if it is compatible for use as the datastore for CMP 2.0 beans. If you are using the Relational Resource Adapter (the default), it is an internal error. |
Objaśnienie | Some unknown SQLException occurred while iterating through a ResultSet returned from a finder or select method. |
Działanie | Review the documentation for the ResourceAdapter you are using to see if it is compatible for use as the datastore for CMP 2.0 beans. If you are using the Relational Resource Adapter (the default), it is an internal error. |
Objaśnienie | Some unknown Exception (other than as in PMGR6040 or PMGR6041) occurred while iterating through a ResultSet returned from a finder or select method. |
Działanie | Review the documentation for the ResourceAdapter you are using to see if it is compatible for use as the datastore for CMP 2.0 beans. If you are using the Relational Resource Adapter (the default), it is an internal error. |
Objaśnienie | While executing a method other than a finder or select (such as create, update or remove), an exception was thrown while attempting to close a connection being used for that method. |
Działanie | Check for a dropped connection to your datastore or other problem with database connections. Review the documentation for the ResourceAdapter you are using to see if it is compatible for use as the datastore for CMP 2.0 beans. If you are using the Relational Resource Adapter (the default), it is an internal error. |
Objaśnienie | Persistence Manger (a component of WAS CMP 2.0 support) requires that Resource Adapters return the result of a finder or select method as either javax.resource.cci.ResultSet or javax.resource.cci.IndexedRecord. javax.resource.cci.MappedRecord is not supported. |
Działanie | Review the documentation for the ResourceAdapter you are using to see if it is compatible for use as the datastore for CMP 2.0 beans. There could be an error or omission in the EJBToRAAdapter subclass supplied with (or added to) your Resource Adapter. If you are using the Relational Resource Adapter (the default), it is an internal error. |
Objaśnienie | The Resource Adapter for this bean type returned the result of a finder or select method as an unknown type of object. |
Działanie | Review the documentation for the ResourceAdapter you are using to see if it is compatible for use as the datastore for CMP 2.0 beans. There could be an error or omission in the EJBToRAAdapter subclass supplied with (or added to) your Resource Adapter. If you are using the Relational Resource Adapter (the default), it is an internal error. |
Objaśnienie | Collections returned from a finder or select method are read-only, they do not allow changes to their content. Your application attempted to call a Collection method which would update the content. |
Działanie | Change your application so it does not call Collection methods which would update the content. If you need a collection which has some but not all of the beans in the returned collection, copy the desired elements into a Collection you created yourself. |
Objaśnienie | This generated extractor did not override the 'discriminate' method, although it should have since its bean is part of an inheritance hierarchy. |
Działanie | If you changed the code generated by the deploy tool, check for errors in this code. |
Objaśnienie | This generated extractor did not override the 'extractDiscriminationValues' method, although it should have since its bean is part of an inheritance hierarchy. |
Działanie | If you changed the code generated by the deploy tool, check for errors in this code. |
Objaśnienie | fieldResultRawData is a wrapper for the ResultSet or IndexedRecord returned from a finder or select method. It is always set to a non-null value. There must be an internal logic error in the code which initialized the ResultCollection. |
Działanie | 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/. |
Objaśnienie | This IP address is used (on the "distributed" platform, not z/OS) to generate unique key values for use with beans defined as having 'unknown' primary keys. Without the IP addresss, the Persistence Manager cannot support "unknown" keys. |
Działanie | 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/. |
Objaśnienie | Your application attempted to call a method which is not supported in this release of WebSphere Application Server. |
Działanie | Change your application so it does not call methods which are not supported in this release. |
Objaśnienie | This generated DataAccessSpec has a WholeRowExtractor with more than one extractor (which indicates other bean data will be read ahead) and yet has no ReadAheadHint to indicate what other bean data should be read ahead. |
Działanie | If you changed the code generated by the deploy tool, especially the xxxAdapterBinding class, check for errors in this code. |
Objaśnienie | The format or content of data in the generated BeanAdapterBinding subclass for some CMP bean does not match what the PM runtime expects. This could be caused by an error in ejbdeploy or in PM runtime, or could be caused by someone incorrectly editing the generated code. |
Działanie | If you changed the code generated by the deploy tool, check for errors in this code. Otherwise, report this error to IBM. |
Objaśnienie | There was a low-level error in getting data returned from your Resource Adapter (or the DataStore behind it), as the result of a finder or select method. A common source of error is that the data in the given column is not a Serialized (or Externalized) Java object as you asserted it was, or some other error in the mapping of this backend column to a bean attribute. |
Działanie | Verify that the value of this column in your datastore is a Serialized (or Externalized) Java object. If it is, examine the classes generated by the Deploy Tool, especially the xxxAdapterBinding class for this bean type. |
Objaśnienie | When unserializing a column of data resulting from a finder or select, the Java class of the object previously serialized into this column could not be found. |
Działanie | Examine the Java classpath in effect for your application, .jar file contents, etc. to determine why this class (which would typically be a class supplied by you) cannot be found. One test you can do is to attempt to create an instance of this class, or otherwise refer to it, within a servlet you have written (which also runs on the application server just as the Persistence Manager does). |
Objaśnienie | Clarification of where the preceeding exception came from. |
Działanie | See the preceeding exeception for what to do. |
Objaśnienie | Clarification of where the preceeding exception came from. |
Działanie | See the preceeding exeception for what to do. |
Objaśnienie | Clarification of where the preceeding exception came from. |
Działanie | See the preceeding exeception for what to do. |
Objaśnienie | Clarification of where the preceeding exception came from. |
Działanie | See the preceeding exeception for what to do. |
Objaśnienie | You have altered the WebSphere INTERNAL USE ONLY flag "INTERNAL_USE_ONLY_throwOnDatastoreAccess". Doing so is a user error and is not supported. |
Działanie | Remove the code in your application that altered the WebSphere INTERNAL USE ONLY flag "INTERNAL_USE_ONLY_throwOnDatastoreAccess". |