Express (Distributed operating systems), v8.0 > Reference > Messages
PMGR
PMGR0000E: Call stack:
{0}
Explanation The call stack exception that occured when the persistence manager created the original exception. Action See the preceeding error message, which caused this call stack exception to occur.
PMGR0001E: Caused by: {0}
Explanation Used to print the messageText of the exception(s) nested (a.k.a. chained) in the original exception. Action Read the chain of exceptions to help determine the problem. The last exception is often the root cause of the problem.
PMGR1000E: Exception occurred :{0}.
Explanation An exception occurred that is related to the nested or chained exceptions. Action For information about the error, see the nested or chained exceptions.
PMGR1001E: No such DataAccessSpec :{0}.
Explanation The DataAccessSpec <type>, which is part of the Deploy Tool-generated xxxAdapterBinding.java file, cannot be found for the given data access specification name and given access intent. For example, optimistic versus pessimistic or read versus update <access intentions?>. This error occurs for one of the following reasons: The back-end data source does not support the SQL Statement that is needed for the access intent. The deployed code is an earlier version that does not contain the new functions. Action Check in the generated xxxAdapterBinding class for the type of bean that is being used. The class contains the defintion for the data access specification. To resolve the issue, you might need to redeploy the EAR file.
PMGR1002E: Error in code generation
Explanation An error occurred in one or more of the .java source code files that are generated by the Deploy Tool. Action Verify that the generated files do not contain errors. Also, verify specified the correct information when you used the Deploy Tool.
PMGR1003E: No such LinkMetadata :{0}.
Explanation A relationship is not defined for the specified relationship role name. Action Check the code for the ConcretexxxBean bean, which is generated by the Deploy tool, to determine whether the specified role name is properly defined.
PMGR1004E: The EJB Object is null.
Explanation An Enterprise JavaBean (EJB) object does not exist in the context. Action Verify whether the EJB object is available in the context.
PMGR1005E: Record for load is null.
Explanation The data is already deleted from the data store, for example, your relational database. Action Verify whether the data is already deleted from data store.
PMGR1006E: Transaction is null.
Explanation The transaction from the context is null. Action Verify whether the transaction is available in the context. The absence of a transaction usually indicates a logic error within the internal container component.
PMGR1007E: Internal Error: Missing Finder for ExecuteFinderForLink. The deployed code may have errors.
Explanation The finder method is missing in the executeFinderForLink <type>. Action Check the code for the ConcretexxxBean bean, which is generated by the Deploy tool, to determine whether the given finder method is properly defined.
PMGR1008E: Related home not found for name: {0}.
Explanation The PMHomeInfo <type> does not exist for a given name. Action Check in the generated xxxAdapterBinding class, which is generated by the Deploy Tool, to determine whether the given name is the abstract schema name that is generated in this code.
PMGR1009E: Error Creating Data Access Spec from BAB: {0}.
Explanation An exception occurred when creating the DataAccessSpec <type> from the generated xxxAdapterBinding class, which is generated by the Deploy Tool. Action Check the generated xxxAdapterBinding class.
PMGR1010E: The current backend id,{0}, does not have equivalent deployed code in the jar.
Explanation The current back-end <server?> ID in the ibm-ejb-jar-bnd.xml file does not have a matching deployed xxxAdapterBinding class. The class is generated by the Deploy Tool. Action Check the deploy process.
PMGR1011E: The current backend id is null.
Explanation The current back-end <server?> ID in the ibm-ejb-jar-bnd.xml file is null. Action Check the deploy process.
PMGR1012E: The current backend id {0}, does not match the data source connected to.
Explanation The current back-end <server?> ID in the ibm-ejb-jar-bnd.xml file does not match the data source to which it is connected. Action Check the deploy process or the data source definition.
PMGR1013E: Exception occured when verifying current backend id {0}: {1}
Explanation An exception occurred that is related to the nested or chained exceptions. Action Read the chain of exceptions to help determine the problem. The last exception is often the root cause of the problem.
PMGR1014E: Exception occured when getting connection factory: {0}
Explanation An exception occurred that is related to the nested or chained exceptions. Action Read the chain of exceptions to help determine the problem. This exception usually occurs because of an error in the data source configuration.
PMGR1015E: Fail verification of read-only bean : (0).
Explanation The data in the data source has changed for the read-only bean. Action Re-drive the transaction or choose a different read-verification strategy.
PMGR1101E: Illegal state.
Explanation The state of the concrete bean is not correct for the specified life cycle method. Action More info at:
PMGR1102E: Error looking up AccessIntentService--{0}.
Explanation An exception occurred when <what does the look up?> looked up the AccessIntenetService <type>. Action Verify that the AccessIntentService <type> in the run time is defined. See "AccessIntent" in the documentation.
PMGR1103E: update instance level read only bean -- {0}.
Explanation An exception occured when the ejbCreate, ejbStore, or ejbRemove a bean , which load as read intent. Action Check the AccessIntent setting for the method that loads the bean.
PMGR1104E: Illegal state due to ejbRemove/ejbLoad/ejbStore called before calling ejbPostCreateor ejbActivate.
Explanation An illegal state exists because the ejbRemove, ejbLoad, or ejbStore are called before calling ejbPostCreate or ejbActivate. Action Check the deployed code or container for problems.
PMGR1105E: Illegal state due to ejbActivate/ejbCreate called to a ready bean.
Explanation An illegal state exists because the ejbActivate or ejbCreate have been called to a ready bean. Action Check the deployed code or container for problems.
PMGR1106E: Update class level read only bean.
Explanation An exception occured when the ejbCreate, ejbStore, ejbRemove a bean , which is class level read only Action Check the ibm-ejb-jar-ext.xml file for the data cache setting.
PMGR1107E: Find class level read only bean for update -- {0}.
Explanation An exception occured when the ejbFind, ejbLoad a bean , which is class level read only. However, the AccessIntent is set as for update. Action Check the ibm-ejb-jar-ext.xml file for the data cache setting. Also, check the AccessIntent setting for the method that loads the bean.
PMGR1108E: Get NULL AccessIntent.
Explanation A NULL value for the AccessIntent <type> was received from the EntityContext <type>. Action Check with the container component owner.
PMGR2000E: Link metadata does not contain a valid link type
Explanation The associations framework did not find a legal link type in the associated metadata. Action The associations framework and code that is generated by the Deploy Tool are probably not synchronized.
PMGR2010E: Cascade delete produced RemoveException
Explanation The container created a RemoveException error when the persistence manager attempted to cascade remove to an associated bean. Action Determine the underlying cause of the RemoveException error.
PMGR5010E: Bean (DataAccessSpec) was generated with complete associations in its list but without DataCacheEntry support for them.
Explanation The DataAccessSpec <type> for a finder method included a CompleteAssociationList <type>. However,the xxxDataCacheEntry <type> was not generated to make use of it. Action Check the xxxAdapterBinding class and the xxxCacheEntry class, which are generated by the Deploy tool, for the bean type that is being used. Examine the input that 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 The client code has sent a PMCacheInvalidationRequest request with abeanAbstractSchemaName name. Either configure the Lifetime In Cache Usage <option?> for this bean type or the beanAbstractSchemaName name for the request is associated with the wrong bean type. Action Use an assembly tool to update the Entity Bean configuration. For more information on the assembly tools, see the information center. Within an assembly tool, click the IBM Extensions tab and set the Lifetime In Cache Usage <option?> to an appropriate value other than Off. As an alternative, find the application code that sends the PMCacheInvalidationRequest <request?> and correct the value for the beanAbstractSchemaName name.
PMGR5021E: PM's invalidation listener received a message but the message parameter was not a PMCacheInvalidationRequest object as required.
Explanation The client code has sent an incorrect JMS message to the cache invalidate topic for the persistence manager. Action Find the application code that sends <sends what?> to the PM cache invalidate topic and verify that 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 application server.
Explanation The client code has sent an incorrect JMS message to the cache invalidate topic for the persistence manager. Action Find the application code that sends <sends what?> to the PM cache invalidate topic. 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 application server. Bean home JNDI names must be unique for CMP beans.
Explanation The container-managed persistence (CMP) entity beans did not ensure that each entity bean uses a unique JNDI name for the bean home. Action Examine the JNDI name for the bean home used by installed beans and remove any duplicate names. We can find the installed beans in the deployment descriptor and other places.
PMGR5024E: IOException while accessing byte-array-ized key object {0}
Explanation A PM cache invalidation request caused an error when a primary key object was serialized into a byte[]. If the key class for the bean is at fault, other errors should have ocurred elsewhere. Action Confirm that the primary key class for you bean correctly serializes and deserializes itself as required by the Enterprise JavaBean (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 The client code sent an incorrect JMS message to the cache invalidate topic for the persistence manager. Action Find the application code that sends the JMS message to the PM cache invalidate topic. Make sure that the application code follows the documented interface for Cache Invalidation. Especially, ensure that the key objects that you pass in the request are the correct type for the beanHomeJNDIName name that you pass in the request.
PMGR5026E: Exception during invalidate listener initialization
Explanation The PM cache invalidation was not set up correctly during server startup. An internal error probably occurred in the installation of the JMS TopicConnectionFactory or TopicDestination topic. Action I understand that you are using If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/ to point to the online problem determination information. If possible, attempt to provide some type of help so that a customer can self-diagnose the problem.
PMGR5027E: Exception while trying to receive a PM cache invalidation message
Explanation The PMCacheInvalidationMessageHandler thread caught an exception while receiving invalidation messages. Action I understand that you are using If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/ to point to the online problem determination information. If possible, attempt to provide some type of help so that a customer can self-diagnose the problem.
PMGR6020E: Error connecting to adapter {0}
Explanation The resource adapter created an exception when it received a request for a connection. Action Verify that the Java EE Connector, or resource adapter, that is configured for use with the current bean type is a valid resource adapter. The error results from a failure with the connection factory.
PMGR6022E: Error using adapter to create or execute an Interaction. {0}
Explanation The resource adapter created an exception when it received a request for a connection. Action Verify that the Java EE Connector, or resource adapter, that is configured for use with the current bean type is a valid resource adapter. The error results from a failure with the connection.getInteraction method or the interaction itself.
PMGR6023E: Possible conflict between this transaction and another while accessing the same data, probably due to application design.
Explanation The most common cause for this exception is when Enterprise JavaBean (EJB) v2.0 applications deadlock with another transaction in this application or another application on this or another computer. In this context, Deadlock means that 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 attempt to access the data for a bean or sometimes for a nearby bean in the same database table. Action Correct the application logic or data access pattern for this application or the other application so that the conflict does not occur. For more information on when and how locks are obtained, see the documentation for your particular database or other data store. For more information on how to configure the applications to avoid a deadlock, see the Access Intent documentation.
PMGR6024E: DuplicateKeyException thrown during interaction.execute(...), inputRecord = {0}
Explanation The resource adapter that is configured for this bean type indicates that the supplied key is a duplicate of a key that already exists in the data store. This error might occur during normal application execution. Action Your application should accept this exception and communicate it to your end user.
PMGR6025E: At attempted update under optimistic concurrency control failed because the bean data has changed in the data store 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. Your application uses optimistic concurrency control, for example Access Intent = optimisticUpdate, and this error occurs despite the benefits of this control. Action Write the application to handle this exception. Either retry the update or communicate the failure to your end user and let the user decide whether to retry the update.
PMGR6030E: EJBCompositeExtractor does not contain an AbstractEJBExtractor for the current result row.
Explanation The bean type used is part of an inheritance hierarchy. A finder method returned data for a bean subclass that is not recognized by the extractor subclasses, which are generated by the Deploy Tool. Action Ensure that we have a deployment descriptor entry for all of the possible bean types in this inheritance hierarchy. Then, verify that 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 As the result of a finder or select method, an error occurred in retrieving data from the resource adapter or its data store. Action Verify that the mapping information or the bean attribute types to data store types mapping is correct. If this information is correct, examine the xxxExtractor classes, which are generated by the Deploy Tool. In particular, examine the extractXXX() methods.
PMGR6032E: SQLException when trying to perform {0}: {1}
Explanation As the result of a finder or select method, the data that was returned from your resource adapter or its data store resulted in an error. Action Review the documentation for the resource adapter that you are using to see if it is compatible for use as the data store for container-managed persistence (CMP) v2.0 beans. If you are using the relational resource adapter, which is the default, this error 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 that does not work until after the bean data is extracted from this result row. The data is extracted using the xxxExtractor.extractData method. Action I understand that you are using If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/ to point to the online problem determination information. If possible, attempt to provide some type of help so that a customer can self-diagnose the problem.
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 that was retrieved from the data store for a bean does not match the generated extractor code for that bean type. Thus, the method cannot properly process the data for use as an entity bean. Action An internal error occurred in the tool that generated the extractor for this bean type. This error does not occur as a result of user error during data mappping or other configuration.
PMGR6035E: SQLException occurred while calling ResultSet.next(). ResultSet is: {0}
Explanation As the result of a finder or select method, an error occurred in iterating through the javax.resource.cci.ResultSet result that was returned from your resource adapter or its data store. Action Review the documentation for the resource adapter that you are using to see if it is compatible for use as the data store for container-managed persistence (CMP) v2.0 beans. If you are using the relational resource adapter, which is the default, this error is an internal error.
PMGR6036E: Unexpected exception occurred while calling ResultSet.next(). ResultSet is: {0}
Explanation The resource adapter returned the javax.resource.cci.ResultSet result. A call to the next method failed on the result. Action Review the documentation for the resource adapter that you are using to see if it is compatible for use as the data store for container-managed persistence (CMP) v2.0 beans. If you are using the relational resource adapter, which is the default, this error is an internal error.
PMGR6038E: In RawBeanData, both resultRecord and resultSet were null. This should never happen, internal logic error.
Explanation An internal error resulted from the logic that creates and initializes a ResultCollection collection. Action I understand that you are using If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/ to point to the online problem determination information. If possible, attempt to provide some type of help so that a customer can self-diagnose the problem.
PMGR6040E: resultSet was found to be closed on first call to resultSet.next(). ResultSet is: {0}
Explanation The connection used to obtain the ResultSet result might be broken, which might trigger a close of ResultSets results. This error also results when the Java 2 Connection (J2C) connection manager has prematurely closed a connection. Action Check for a dropped connection to your data store. Review the documentation for the resource adapter that you are using to see if it is compatible as the data store for container-managed persistence (CMP) v2.0 beans. f you are using the relational resource adapter, which is the default, this error is an internal error.
PMGR6041E: SQLException on first call to resultSet.next(). ResultSet is: {0}
Explanation An SQLException exception was created when <the Application Server?> iterated through a ResultSet result that has been returned from a finder or select method. Action Review the documentation for the resource adapter that you are using to see if it is compatible for use as the data store for container-managed persistence (CMP) v2.0 beans. If you are using the relational resource adapter, which is the default, this error is an internal error.
PMGR6042E: Non-SQL error on first call to resultSet.next(). ResultSet is: {0}
Explanation An exception occurred that is not related to the PMGR6040 or PMGR6041 message when <the Application Server> iterated through a ResultSet result that has been returned from a finder or select method. Action Review the documentation for the resource adapter that you are using to see if it is compatible for use as the data store for container-managed persistence (CMP) v2.0 beans. If you are using the relational resource adapter, which is the default, this error is an internal error.
PMGR6043E: Problem closing connection after interaction.execute(...) normal completion. Throwable was: {0}
Explanation A connection attempted to close when it was in use by a method other than a find or select method. These methods include the create, update or remove method. Action Check for a dropped connection to your data store or another problem with database connections. Review the documentation for the resource adapter that you are using to see if it is compatible as the data store for container-managed persistence (CMP) v2.0 beans. If you are using the relational resource adapter, which is the default, this error 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 The persistence manger requires that the resource adapters return the result of a finder or select method as either javax.resource.cci.ResultSet or javax.resource.cci.IndexedRecord. The javax.resource.cci.MappedRecord result is not supported. Action Review the documentation for the resource adapter that you are using to see if it is compatible for use as the data store for container-managed persistence (CMP) v2.0 beans. There might be an error or omission in the EJBToRAAdapter subclass that is supplied with or added to your resource adapter. If you are using the relational resource adapter, which is the default, this error 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. Action Review the documentation for the resource adapter that you are using to see if it is compatible for use as the data store for container-managed persistence (CMP) v2.0 beans. There might be an error or omission in the EJBToRAAdapter subclass that is supplied with or added to your resource adapter. If you are using the relational resource adapter, which is the default, this error is an internal error.
PMGR6050E: Collection is read-only, since it represents data from a backend data store.
Explanation Collections that are 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 that attempts to update the content. Action Change the application so it does not call collection methods that attempts to update the content. If you need a collection that has some, but not all, of the beans in the returned collection, copy the desired elements into a collection you can create.
PMGR6051E: This generated extractor did not override the 'discriminate' method, although it should have since its bean is part of an inheritance hierarchy.
Explanation The generated extractor did not override the discriminate method. The extractor should have overridden the method because its bean is part of an inheritance hierarchy. Action If you changed the code that is 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. The extractor should have overridden the method because its bean is part of an inheritance hierarchy. Action If you changed the code that is generated by the Deploy Tool, check for errors in this code.
PMGR6053E: INTERNAL ERROR: ResultCollection.fieldResultRawData is null
Explanation The fieldResultRawData wrapper is a wrapper for the result set or the indexed record that is returned from a finder or select method. This wrapper is set to a non-null value. There must be an internal logic error in the code that initialized the ResultCollection collection. Action I understand that you are using If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/ to point to the online problem determination information. If possible, attempt to provide some type of help so that a customer can self-diagnose the problem.
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 to generate unique key values for use with beans that are defined with the unknown primary key type. This IP address is used and not the z/OS operating system. Without the IP addresss, the persistence manager cannot support the unknown key type. Action I understand that you are using If the problem persists, see problem determination information on the WAS Support page at //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support/ to point to the online problem determination information. If possible, attempt to provide some type of help so that a customer can self-diagnose the problem.
PMGR6055E: Function not supported.
Explanation Your application attempted to call a method that is not supported. Action Change the application so it does not call methods that are not supported.
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 The generated DataAccessSpec <specification?> has a WholeRowExtractor <type?> with more than one extractor, which indicates that other bean data will be read first. However, the <specification?> does not have a ReadAheadHint <type?> to specify which other bean data to read first. Action If you changed the code that is 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 the data in the generated BeanAdapterBinding subclass for a container-managed persistence (CMP) bean does not match the data that the persistence manager runtime expects. This error might result from an error in ejbdeploy command or in the persistence manager run time. The error might also result when the generated code is incorrectly edited. Action If you changed the code that is generated by the Deploy Tool, check for errors in this code. Otherwise, report this error to IBM." Do not tell customers to report the error to IBM. If you cannot provide another solution, add the following information: "See the problem determination information on the WAS Support Web page: //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ ://www.ibm.com/software/webservers/appserv/was/support
PMGR6101E: SerializableDVFieldExtractor encountered error while extracting a Dependent Value on behalf of an ejbSelect for a CMP field (the DV).
Explanation A low-level error occurred in retrieving data from your resource adapter or its data store 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 it was asserted. Also, the error might occur due to a mapping of this back-end column to a bean attribute. Action Verify that the value of this column in your data store is a serialized or externalized Java object. If it is a serialized or externalized Java object, examine the classes that are 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 that results from a finder or select method, the Java class of the object that previously serialized into this column cannot be found. Action Examine the Java class path, the JAR file and so on that is associated with the application to determine why this class cannot be found. This class is typically provided by you. As a test, attempt to create an instance of this class, or otherwise refer to it, within a servlet that we have written. The servlet needs to run on the application server just as the persistence manager runs.
PMGR6501E: Caused by ErrorProcessingResultCollectionRow
Explanation This error clarifies the origin of the preceeding exception. Action See the preceeding exeception to determine the appropriate action.
PMGR6502E: Caused by PersistenceManagerInternalError
Explanation This error clarifies the origin of the preceeding exception. Action See the preceeding exeception to determine the appropriate action.
PMGR6503E: Caused by BeanGenerationException
Explanation This error clarifies the origin of the preceeding exception. Action See the preceeding exeception to determine the appropriate action.
PMGR6504E: Caused by BeanDeploymentDescriptorException
Explanation This error clarifies the origin of the preceeding exception. Action See the preceeding exeception to determine the appropriate action.
PMGR6999E: INTERNAL USE ONLY: attempt to access DataStore when access is turned off
Explanation The INTERNAL_USE_ONLY_throwOnDatastoreAccess flag, which is internal to the product, has been altered. Altering this flag is a user error and is not supported. Action Remove the application code alters the INTERNAL_USE_ONLY_throwOnDatastoreAccess flag.