JDO

JDO7000 Cannot get policy for {0}.

Cause:

Error loading the default mapping policy which is used by database schema generation.

Solution:

Check that the classpath settings are not corrupted.

JDO74003 Caught ModelException on setDeleteAction:

Cause:

Internal error in CMP module.

Solution:

This is an Unexpected Internal Error. Please contact Sun with your application and the complete error log message.

JDO74005 Bean ''{0}'' is not persistent during call to {1}.

Cause:

CMR field is accessed in ejbCreate.

Solution:

Change bean code to access CMR fields in ejbPostCreate.

JDO74006 Bean ''{0}'' method {1}: Cannot set Collection value to null.

Cause:

Parameter passed to Collection CMR set method is null.

Solution:

Use Collection.remove() method to remove all related beans from this Collection.

JDO74019 Bean {0} is not loaded. Persistence manager in this instance is null.

Cause:

Possible error in EJB Container and CMR runtime life cycle.

Solution:

This is an Unexpected Internal Error. Please turn on JDO and CMP logging and contact Sun with the complete error log message.

JDO74020 Cannot use bean {0} in more than one transaction. Persistence manager in this instance is not null.

Cause:

Possible error in EJB Container and CMR runtime life cycle.

Solution:

This is an Unexpected Internal Error. Please turn on JDO and CMP logging and contact Sun with the complete error log message.

JDO74021 Bean {0} participates in a container transaction but persistence manager in this instance is null.

Cause:

ejbRemove or ejbStore is called in an active transaction without bean being loaded in the same transaction. Possible error in EJB Container and CMR runtime life cycle.

Solution:

This is an Unexpected Internal Error. Please turn on JDO and CMP logging and contact Sun with the complete error log message.

JDO74043 Bean ''{0}'' method {1}: Update operations are not allowed for this bean type.

Cause:

Create, remove, or update is called on a read-only bean.

Solution:

Do not attempt to update read-only beans.

Solution:

If update is required, the bean must be deployed as two different EJBs: as a read-only bean, and as an updateable bean. All updates must be done on the second bean.

JDO74045 Cannot clone bean ''{0}'' instance with key {1}.

Cause:

State class is not generated properly for this CMP bean.

Solution:

This is an Unexpected Internal Error. Please contact Sun with your application and the complete error log message.

JDO75007 Fatal internal exception while parsing EJBQL:\n\

Cause:

Internal error in CMP module.

Solution:

This is an Unexpected Internal Error. Please contact Sun with your application and the complete error log message.

JDO76604 JNDI lookup for cmp-resource ''{0}'' failed.

Cause:

CMP resource with this JNDI name is not registered with this instance.

Cause:

JNDI name for the CMP resource is misspelled.

Solution:

Check JNDI name for the resource you plan to use.

Solution:

Check JNDI name of the CMP resource specified in the module.

JDO76605 JNDI lookup for cmp-resource ''{0}'' returned an instance of an unexpected type: {1}.

Cause:

CMP resource with this JNDI name does not reference jdbc-resource or persistence-manager-factory-resource.

JDO7704 This error (\

Cause:

Cannot identify related field.

Cause:

Cannot identify related class.

Solution:

Verify that relationship definition is correct.

JDO82000 Exception creating logger {0}

Cause:

System was not able to create specified logger.

Cause:

Error loading message bundle that corresponds to this logger.

Solution:

Check that the classpath settings are not corrupted.

Solution:

Check error log for the detailed reason.