|
Persistence Manager messages |
|
PMGR0000E: Call stack:
{0}
Explanation:
Used to dump the exception callstack when the persistence manager threw the original exception.
User Response:
See the preceeding error message which caused this call stack dump.
PMGR0001E: Caused by: {0}
Explanation:
Used to print the messageText of the exception(s) nested (a.k.a. chained) in the original exception.
User Response:
Read the chain of exceptions to help determine the problem. The last one is often the root cause of the problem.
PMGR1000E: Exception occurred :{0}.
Explanation:
An exception occurred, please look at the nested exception for the reason.
User Response:
Read the chained exception for detailed information.
PMGR1001E: No such DataAccessSpec :{0}.
Explanation:
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)
User Response:
Check in the generated xxxAdapterBinding class for the bean type being used, which is where the data access spec is defined.
PMGR1002E: Error in code generation
Explanation:
Error in one or more of the .java source code files generated by the Deploy Tool.
User Response:
Check these generated files for errors. Check whether specified correct information when using the Deploy Tool.
PMGR1003E: No such LinkMetadata :{0}.
Explanation:
There is no Relationship defined for a given relationship role name.
User Response:
Check the code generation of ConcretexxxBean (generated by the Deploy tool)to see if the given role name is properly defined there.
PMGR1004E: The EJB Object is null.
Explanation:
There is no EJB Object in the context.
User Response:
Check EJB Object availability in the context.
PMGR1005E: Record for load is null.
Explanation:
The data is already deleted from the datastore (for example, your relational database).
User Response:
Check if the data is already deleted from datastore.
PMGR1006E: Transaction is null.
Explanation:
Trasaction is null from the context.
User Response:
Check the availability of transaction in the context. The absence of a transaction usually indicates an internal logic error within WebSphere's Container component.
PMGR1007E: Internal Error: Missing Finder for ExecuteFinderForLink. The deployed code may have errors.
Explanation:
Missing the finder in executeFinderForLink.
User Response:
Check the code generation of ConcretexxxBean (generated by the Deploy tool)to see if the given finder method is properly defined there.
PMGR1008E: Related home not found for name: {0}.
Explanation:
The PMHomeInfo does not exist for a given name.
User Response:
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.
PMGR1009E: Error Creating Data Access Spec from BAB: {0}.
Explanation:
Exception occurred when creating DataAccessSpec from the generated xxxAdapterBinding class (generated by the Deploy tool).
User Response:
Check the generated xxxAdapterBinding class.
PMGR1010E: The current backend id,{0}, does not have equivalent deployed code in the jar.
Explanation:
The current backend id in the ibm-ejb-jar-bnd.xml does not have a matching deployed xxxAdapterBinding class (generated by the Deploy tool).
User Response:
Check the deploy process.
PMGR1011E: The current backend id is null.
Explanation:
The current backend id in the ibm-ejb-jar-bnd.xml is null.
User Response:
Check the deploy process.
PMGR1012E: The current backend id {0}, does not match the datasource connected to.
Explanation:
The current backend id in the ibm-ejb-jar-bnd.xml does not match the datasource it connected to.
User Response:
Check the deploy process or the datasource definition.
PMGR1013E: Exception occured when verifying current backend id {0}: {1}
Explanation:
See the nested exception .
User Response:
Check the nested exception to find out the reason.
PMGR1101E: Illegal state.
Explanation:
The state of the concrete bean is not correct for a given lifecycle method.
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/.
PMGR1102E: Error looking up AccessIntentService--{0}.
Explanation:
Exception occurred when look up of AccessIntenetService.
User Response:
Check if the runtime AccessIntentService is defined. See "AccessIntent" in the documentation.
PMGR1103E: update instance level read only bean -- {0}.
Explanation:
Exception occured when ejbCreate/ejbStore/ejbRemove a bean , which load as read intent.
User Response:
Check the AccessIntent setting for the method which loads the bean.
PMGR1104E: Illegal state due to ejbRemove/ejbLoad/ejbStore called before calling ejbPostCreateor ejbActivate.
Explanation:
Illegal state due to ejbRemove/ejbLoad/ejbStore called before calling ejbPostCreateor ejbActivate.
User Response:
Check the deployed code or container for problems
PMGR1105E: Illegal state due to ejbActivate/ejbCreate called to a ready bean.
Explanation:
Illegal state due to ejbActivate/ejbCreate called to a ready bean.
User Response:
Check the deployed code or container for problems
PMGR1106E: Update class level read only bean.
Explanation:
Exception occured when ejbCreate/ejbStore/ejbRemove a bean , which is class level read only
User Response:
Check the ibm-ejb-jar-ext for DataCache setting.
PMGR1107E: Find class level read only bean for update -- {0}.
Explanation:
Exception occured when ejbFind<>/ejbLoad a bean , which is class level read only, but the AccessIntent is set as for update.
User Response:
Check the ibm-ejb-jar-ext for DataCache setting and AccessIntent and the AccessIntent setting for the method which loads the bean..
PMGR1108E: Get NULL AccessIntent.
Explanation:
Get NULL AccessIntent from EntityContext.
User Response:
Check with container component owner.
PMGR2000E: Link metadata does not contain a valid link type
Explanation:
The asscociations framework did not find a legal link type in the associated metadata
User Response:
The associations framework and Deploy tool code generation are probably out of synch
PMGR2010E: Cascade delete produced RemoveException
Explanation:
Container threw RemoveException when PersistenceManager tried to cascade remove to an associated bean
User Response:
Try to determine the underlying cause of the RemoveException
PMGR5010E: Bean (DataAccessSpec) was generated with complete associations in its list but without DataCacheEntry support for them.
Explanation:
The DataAccessSpec for a finder method included a CompleteAssociationList but the xxxDataCacheEntry was not generated to make use of it.
User Response:
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.
PMGR5020E: The given bean type has Lifetime In Cache Usage OFF, so there is no cache to invalidate. The invalidate request is ignored.
Explanation:
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.
User Response:
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.
PMGR5021E: PM's invalidation listener received a message but the message parameter was not a PMCacheInvalidationRequest object as required.
Explanation:
Caused when client code sends an incorrect JMS message to the PM cache invalidate topic.
User Response:
Find the application code that sends to the PM cache invalidate topic and fix it so it follows the documented interface for "Cache Invalidation".
PMGR5022E: Bean home JNDI name {0} not found among the names for beans currently installed on this appserver.
Explanation:
Caused when client code sends an incorrect JMS message to the PM cache invalidate topic.
User Response:
Find the application code that sends to the PM cache invalidate topic and set the beanHomeJNDIName parameter to a correct value.
PMGR5023E: Bean home JNDI name {0} was used for more than one bean currently installed on this appserver. Bean home JNDI names must be unique for CMP beans.
Explanation:
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.
User Response:
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.
PMGR5024E: IOException while accessing byte-array-ized key object {0}
Explanation:
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.
User Response:
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.
PMGR5025E: ClassNotFoundException while deserializing bean primary key object passed by client code. Key object is not of the correct class for bean type with JNDI home name = {0}.
Explanation:
Caused when client code sends an incorrect JMS message to the PM cache invalidate topic.
User Response:
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.
PMGR5026E: Exception during invalidate listener initialization
Explanation:
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.
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/.
PMGR5027E: Exception while trying to receive a PM cache invalidation message
Explanation:
Internal PMCacheInvalidationMessageHandler thread caught an exception while receiving invalidation messages.
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/.
PMGR6020E: Error connecting to adapter {0}
Explanation:
An exception was thrown while requesting a connection from the Resource Adapter
User Response:
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.
PMGR6022E: Error using adapter to create or execute an Interaction. {0}
Explanation:
An exception was thrown while requesting a connection from the Resource Adapter
User Response:
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.
PMGR6023E: Possible conflict between this transaction and another while accessing the same data, probably due to application design.
Explanation:
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.
User Response:
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".
PMGR6024E: DuplicateKeyException thrown during interaction.execute(...), inputRecord = {0}
Explanation:
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.
User Response:
Your application should be written to accept this exception and communicate this to your end user.
PMGR6025E: At attempted update under optimistic concurrency control failed because the bean data has changed in the datastore since this transaction read it. Either a predicate field has changed value or the bean itself has been removed.
Explanation:
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.
User Response:
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.
PMGR6030E: EJBCompositeExtractor does not contain an AbstractEJBExtractor for the current result row.
Explanation:
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)
User Response:
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.
PMGR6031E: SQLException when trying to get resultSet column {0} as a {1}. RawBeanData={2}
Explanation:
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.
User Response:
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.
PMGR6032E: SQLException when trying to perform {0}: {1}
Explanation:
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.
User Response:
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.
PMGR6033E: Method cannot be called until after extractData() has been called.
Explanation:
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().
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/.
PMGR6034E: An error occured while extracting data from a row of finder results (for example, the value found in a discrimination column was not recognized by the Extractor processing it).
Explanation:
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.
User Response:
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.
PMGR6035E: SQLException occurred while calling ResultSet.next(). ResultSet is: {0}
Explanation:
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.
User Response:
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.
PMGR6036E: Unexpected exception occurred while calling ResultSet.next(). ResultSet is: {0}
Explanation:
Calling next() on the javax.resource.cci.ResultSet returned by the ResourceAdapter failed.
User Response:
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.
PMGR6038E: In RawBeanData, both resultRecord and resultSet were null. This should never happen, internal logic error.
Explanation:
Internal error in the logic which creates and initialized a ResultCollection.
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/.
PMGR6040E: resultSet was found to be closed on first call to resultSet.next(). ResultSet is: {0}
Explanation:
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).
User Response:
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.
PMGR6041E: SQLException on first call to resultSet.next(). ResultSet is: {0}
Explanation:
Some unknown SQLException occurred while iterating through a ResultSet returned from a finder or select method.
User Response:
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.
PMGR6042E: Non-SQL error on first call to resultSet.next(). ResultSet is: {0}
Explanation:
Some unknown Exception (other than as in PMGR6040 or PMGR6041) occurred while iterating through a ResultSet returned from a finder or select method.
User Response:
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.
PMGR6043E: Problem closing connection after interaction.execute(...) normal completion. Throwable was: {0}
Explanation:
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.
User Response:
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.
PMGR6045E: Result is MappedRecord, which is not supported. See ResultCollection doc for Resource Adapter standards on results of type cci.Record.
Explanation:
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.
User Response:
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.
PMGR6046E: Result is of an unknown type. See ResultCollection doc for Resource Adapter standards on results of type cci.Record.
Explanation:
The Resource Adapter for this bean type returned the result of a finder or select method as an unknown type of object.
User Response:
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.
PMGR6050E: Collection is read-only, since it represents data from a backend data store.
Explanation:
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.
User Response:
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.
PMGR6051E: This generated extractor did not override the 'discriminate' method, although it should have since its bean is part of an inheritance hierarchy.
Explanation:
This generated extractor did not override the 'discriminate' method, although it should have since its bean is part of an inheritance hierarchy.
User Response:
If you changed the code generated by the deploy tool, check for errors in this code.
PMGR6052E: This generated extractor did not override the 'extractDiscriminationValues' method, although it should have since its bean is part of an inheritance hierarchy.
Explanation:
This generated extractor did not override the 'extractDiscriminationValues' method, although it should have since its bean is part of an inheritance hierarchy.
User Response:
If you changed the code generated by the deploy tool, check for errors in this code.
PMGR6053E: INTERNAL ERROR: ResultCollection.fieldResultRawData is null
Explanation:
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.
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/.
PMGR6054E: Cannot find local host IP address (by calling java.net.InetAddress.getLocalHost().getHostAddress()), used to generate unique key value.
Explanation:
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.
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/.
PMGR6055E: Function not supported.
Explanation:
Your application attempted to call a method which is not supported in this release of WebSphere Application Server.
User Response:
Change your application so it does not call methods which are not supported in this release.
PMGR6056E: 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.
Explanation:
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.
User Response:
If you changed the code generated by the deploy tool, especially the xxxAdapterBinding class, check for errors in this code.
PMGR6057E: Error in generation of BeanAdapterBinding contents. Either an internal error in ejbdeploy or generated code was modified afterward & an error was introduced.
Explanation:
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.
User Response:
If you changed the code generated by the deploy tool, check for errors in this code. Otherwise, report this error to IBM.
PMGR6101E: SerializableDVFieldExtractor encountered error while extracting a Dependent Value on behalf of an ejbSelect for a CMP field (the DV).
Explanation:
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.
User Response:
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.
PMGR6102E: SerializableDVFieldExtractor could not find the class for a Dependent Value, on behalf of an ejbSelect for a CMP field (the DV).
Explanation:
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.
User Response:
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 appserver just as the Persistence Manager does).
PMGR6501E: Caused by ErrorProcessingResultCollectionRow
Explanation:
Clarification of where the preceeding exception came from.
User Response:
See the preceeding exeception for what to do.
PMGR6502E: Caused by PersistenceManagerInternalError
Explanation:
Clarification of where the preceeding exception came from.
User Response:
See the preceeding exeception for what to do.
PMGR6503E: Caused by BeanGenerationException
Explanation:
Clarification of where the preceeding exception came from.
User Response:
See the preceeding exeception for what to do.
PMGR6504E: Caused by BeanDeploymentDescriptorException
Explanation:
Clarification of where the preceeding exception came from.
User Response:
See the preceeding exeception for what to do.
PMGR6999E: INTERNAL USE ONLY: attempt to access DataStore when access is turned off
Explanation:
You have altered the WebSphere INTERNAL USE ONLY flag "INTERNAL_USE_ONLY_throwOnDatastoreAccess". Doing so is a user error and is not supported.
User Response:
Remove the code in your application that altered the WebSphere INTERNAL USE ONLY flag "INTERNAL_USE_ONLY_throwOnDatastoreAccess".
Last updated:
Library | Support | Trademarks | Feedback