Error 54 of expected

error 54 of expected

"##" may not be last in a macro definition. expected a macro parameter name. expected a ":". too few arguments in invocation of. Learn about the "class, interface, or enum expected" Java compiler error and how to fix it. Error: KMA did not run as expected. Create issue. Issue #54 resolved. Anto created an issue KMA seems to be running into a.

Error 54 of expected - not absolutely

This section lists each TopLink error code. Each error entry contains a description of the error, the probable cause, and the recommended action. Each error code corresponds to an exception class. See "Runtime and Development Exceptions" for more information.

A description shown in the actual exception thrown.

Cause: The most probable cause for the error.

Action: Suggestions for resolving the error.

ATTRIBUTE_AND_MAPPING_WITH_INDIRECTION_ MISMATCH

Cause: <attributeName> is not declared as type but the mapping uses indirection. Mapping is set to use indirection but the related attribute is not defined as type . It is thrown on foreign reference mappings.

Action: If you want to use indirection on the mapping, change the attribute to type . Otherwise, change the mapping associated with the attribute so that it does not use indirection.

ATTRIBUTE_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: <attributeName> is declared as type but the mapping is not using indirection. Attribute is defined to be of type but the mapping is not set to use indirection. It is thrown on foreign reference mappings.

Action: If you do not want to use indirection on the mapping, change the attribute to not be of type . Otherwise, change the mapping associated with the attribute to use indirection.

ATTRIBUTE_NAME_NOT_SPECIFIED

Cause: Attribute name is missing or not specified in the mapping definition.

Action: Specify the attribute name in the mapping by calling method .

ATTRIBUTE_TYPE_NOT_VALID

Cause: <attributeName> should be defined as type Vector, or a type that implements Map or Collection if using Java 2. It happens in one to many mapping, many to many mapping and collection mapping when mapping is set not to use indirection and attribute type is not declared of type .

Action: Declare the attribute to be of type .

CLASS_INDICATOR_FIELD_NOT_FOUND

Cause: The class indicator field has not been defined, however the descriptor has been set to use inheritance. When using inheritance, a class indicator field or class extraction method must be set. The class indicator field is used to create the right type of domain object

Action: Either a class indicator field or class extraction method must be set.

DIRECT_FIELD_NAME_NOT_SET

Cause: The direct field name from the target table is not set in the direct collection mapping. The field values form the collection in this mapping.

Action: Specify the direct field name by calling method .

FIELD_NAME_NOT_SET_IN_MAPPING

Cause: The field name is not set in the mapping. It is thrown from direct to field mapping, array mapping and structure mapping.

Action: Specify the field name by calling method .

FOREIGN_KEYS_DEFINED_INCORRECTLY

Cause: One to one mapping foreign key defined incorrectly. Multiple foreign key fields were set for one to one mapping by calling method .

Action: Use method to add multiple foreign key fields.

IDENTITY_MAP_NOT_SPECIFIED

Cause: The descriptor must use an identity map to use the Check cache does exist option. Descriptor has been set to not use identity map but the existence checking is set to be done on identity map.

Action: Either use identity map or set the existence checking to some other option.

ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: <attributeName> instance variable in object <objectName> is inaccessible. Instance variable in the domain object is not accessible. This exception is thrown when TopLink tries to access the instance variable using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_CLONING

Cause: Problem in cloning the object <domainObject>. Clone method <methodName> is not accessible. The method name specified using or the method to create clone on the domain object is not accessible by TopLink using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: The domain class does not define a public default constructor, which is needed by TopLink to create new instances of the domain class.

Action: Define one or use different instantiation policy.

ILLEGAL_ACCESS_WHILE_EVENT_EXECUTION

Cause: The descriptor callback method <eventMethodName> with as argument, is not accessible. This exception is thrown when TopLink tries to access the event method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke inaccessible <methodName> on the object <objectName>. The underlying get accessor method to access an attribute in the domain object is not accessible. This exception is thrown when TopLink tries to access an attribute through method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INSTANTIATING_METHOD_ BASED_PROXY

Cause: The method used by the Transformation mapping using a is illegal. This exception is thrown when TopLink tries to access the method using Java reflection. The problem is caused when method base value holder is getting instantiated.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_ATTRIBUTE_METHOD

Cause: On transformation mapping the underlying attribute method used to retrieve value from the database row while reading transformation mapped attribute is not accessible.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_FIELD_TO_METHOD

Cause: On transformation mapping the method <methodName> used to retrieve value from the object while writing transformation mapped attribute is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_INVOKING_ROW_EXTRACTION_ METHOD

Cause: Problem in extracting class from <row>; Static method <method> with <databaseRow> as argument, is not accessible. The method to extract class from row on the domain object is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance; the method <methodName> to create instances on the domain class is not accessible. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_OBSOLETE_EVENT_EXECUTION

Cause: The descriptor callback method <eventMethodName> with Session as argument, is inaccessible. This exception is thrown when TopLink tries to access the event method using Java reflection. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: The <attributeName> instance variable in the object <objectName> is not accessible through Java reflection. The error is thrown by Java and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ACCESS_WHILE_SETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke inaccessible method <setMethodName> on the object with parameter <parameter>. The attribute's set accessor method is not accessible through Java reflection. The error is thrown by Java and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_ THRU_INSTANCE_VARIABLE_ACCESSOR

Cause: Trying to get a value for an instance variable <attributeName> of type <typeName> from the object. The specified object is not an instance of the class or interface declaring the underlying field. An object is accessed to get the value of an instance variable that does not exist.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Trying to invoke method <methodName> on the object <objectName>. The get accessor method declaration on the domain object differs from the one that is defined. The number of actual and formal parameters differ, or an unwrapping conversion has failed.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INSTANTIATING_METHOD_ BASED_PROXY

Cause: The method used by the method-based proxy in a Transformation mapping is getting illegal arguments when the value holder is getting instantiated. This exception is thrown when TopLink tries to access the method using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INVOKING_ATTRIBUTE_ METHOD

Cause: The number of actual and formal parameters differ, or an unwrapping conversion has failed. On transformation mapping the method used to retrieve value from the database row while reading transformation mapped attribute is getting illegal argument.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_INVOKING_FIELD_TO_ METHOD

Cause: The number of actual and formal parameters differ for method <methodName> or an unwrapping conversion has failed. On transformation mapping the method used to retrieve value from the object while writing transformation mapped attribute is getting illegal argument. The error is purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_OBSOLETE_EVENT_ EXECUTION

Cause: he number of actual and formal parameters for the descriptor callback method <eventMethodName> differs, or an unwrapping conversion has failed. The callback event method is invoked with illegal argument. This exception is thrown when TopLink tries to invoke the event method using Java reflection. The error is a purely Java exception and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: Illegal value is being assigned to the attribute instance variable. Trying to set a value <value> for an instance variable <attributeName> of type <typeName> in the object. The specified object is not an instance of the class or interface declaring the underlying field, or an unwrapping conversion has failed.

TopLink does the assignment of value by using Java reflection. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

ILLEGAL_ARGUMENT_WHILE_SETTING_VALUE_THRU _METHOD_ACCESSOR

Cause: Illegal argument is being passed to the attribute's set accessor method. Trying to invoke method <setMethodName> on the object. The number of actual and formal parameters differs, or an unwrapping conversion has failed. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

INSTANTIATION_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: he class does not define a public default constructor, or the constructor raised an exception. The default constructor for the domain object is invoked to create new instance of the object while building new domain objects. If this Class represents an abstract class, an interface, an array class, a primitive type, or void; or if the instantiation fails for some other reason. Java throws the error and TopLink only wraps the reflection exception.

Action: Inspect the internal exception and check the Java manuals.

INVALID_DATA_MODIFICATION_EVENT

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. In cases where one writes new mapping it is possible to get this exception. In direct collection mapping and many to many mapping the target table and relational table are populated at the end of the commit process and if data modification event is sent to any other mapping then this exception is thrown.

Action: Contact Technical Support.

INVALID_DATA_MODIFICATION_EVENT_CODE

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. In cases where one writes new mapping it is possible to get this exception. In direct collection mapping and many to many mapping the target table and relational table are populated at the end of the commit process and if data modification event is sent to these two mappings with wrong event code then this exception is thrown.

Action: Contact Technical Support.

INVALID_DESCRIPTOR_EVENT_CODE

Cause: This is an exception that an application should never encounter. The exception can occur at the time of developing TopLink. The exception means that descriptor event manager does not support the event code passed in the event.

Action: Contact Technical Support.

INVALID_IDENTITY_MAP

Cause: Identity map constructor failed because an invalid identity map was specified. The identity map class given in the descriptor cannot be instantiated. The exception is Java exception thrown by Java reflection when TopLink is instantiating the identity map class. TopLink only wraps the Java exception.

Action: Inspect the internal exception and check the Java manuals.

JAVA_CLASS_NOT_SPECIFIED

Cause: The descriptor does not define a Java class. The Java class is not specified in the descriptor.

Action: Specify the Java Class

DESCRIPTOR_FOR_INTERFACE_IS_MISSING

Cause: A descriptor for the referenced interface is not added to the session.

Action: Add that descriptor to the session.

MAPPING_FOR_SEQUENCE_NUMBER_FIELD

Cause: A non-read-only mapping is not defined for the sequence number field. A mapping is required so that TopLink can put and extract values for the primary key.

Action: Define a mapping.

MISSING_CLASS_FOR_INDICATOR_FIELD_VALUE

Cause: Missing class for indicator field value <classFieldValue> of type <type>. There was no class entry found in the inheritance policy for the indicator field value read from the database. Probably the method was not called for the field value. The class and typeValue is stored in the hashtable and later on the class is extracted from the hashtable by passing as a key. Remember Integer(1) is not equal to Float(1), this is another major reason for this problem when the type of typeValue is different.

Action: Check descriptor.

MISSING_CLASS_INDICATOR_FIELD

Cause: The class indicator field is missing from the database row <row> that was read from the database. This is done in inheritance model where after reading rows from the database, child domain objects are to be constructed depending upon the type indicator values.

Action: Check the printed row to make sure the spelling is correct.

MISSING_MAPPING_FOR_FIELD

Cause: Missing mapping for field <field>; a mapping for the field is not specified.

Action: Define a mapping for the field.

NO_MAPPING_FOR_PRIMARY_KEY

Cause: A mapping for the primary key is not specified. There should be one non-read-only mapping defined for the primary key field.

Action: efine a mapping for the primary key.

MULTIPLE_TABLE_PRIMARY_KEY_NOT_SPECIFIED

Cause: The multiple table primary key mapping must be specified when a custom multiple table join is used. If multiple tables are specified in the descriptor and the join expression is customized then the primary keys for all the tables must be specified. If the primary keys are not specified then the exception is caused.

Action: Call method on the descriptor to set the primary keys.

MULTIPLE_WRITE_MAPPINGS_FOR_FIELD

Cause: There are multiple writable mappings for the field <fieldName> in the descriptor. Exactly one must be defined writable. The others must be specified as read-only. When multiple write mappings are defined for the field, TopLink cannot decide on which mapping to pick up for writing the value of the field in the database row hence the exception is thrown during the validation process of descriptors. The most common site for this problem is that sometimes the field has direct-to-field mapping and also one-to-one mapping. In this case if direct-to-field mapping has to be kept then one-to-one mapping should either be read-only or it should be target foreign key reference.

Action: Make one of those mappings read only.

NO_ATTRIBUTE_TRANSFORMATION_METHOD

Cause: The attribute transformation method name in the transformation mapping is not specified. This method is invoked internally by TopLink to retrieve value to store in the domain object.

Action: Define a method and set the method name on the mapping by calling method .

NO_FIELD_NAME_FOR_MAPPING

Cause: No field name is specified in direct-to-field mapping.

Action: Set the field by calling .

NO_FOREIGN_KEYS_ARE_SPECIFIED

Cause: Neither the selection criteria nor the foreign keys were specified on one-to-one mapping. If the selection criterion is not specified then TopLink tries to build one from the foreign keys specified in the mapping.

Action: Specify the fields.

NO_REFERENCE_KEY_IS_SPECIFIED

Cause: No query key named: <queryKey> found in: <descriptor>; no reference key from the target table is specified on direct collection mapping.

Action: Specify the fields by calling method .

NO_RELATION_TABLE

Cause: The relation table name is not set in this many-to-many mapping.

Action: Set relation table name by calling method .

NO_SOURCE_RELATION_KEYS_SPECIFIED

Cause: There are no source relation keys specified in this many-to-many mapping.

Action: Add source relation keys to the mapping.

NO_SUCH_METHOD_ON_FIND_OBSOLETE_METHOD

Cause: The descriptor callback method <selector> on the domain class was not found. It must take a or a as its argument. TopLink tries to invoke the method using Java reflection. It is a Java exception and TopLink is only wrapping the main exception.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_ON_INITIALIZING_ ATTRIBUTE_METHOD

Cause: The method <attributeMethodName> with parameters <databaseRow> or <databaseRow, session> is not found. TopLink wraps the Java reflection exception that is caused when the method is being created from the method name. This method is set by calling.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_CONSTRUCTOR_ INSTANTIATION

Cause: Inaccessible constructor. TopLink wraps the Java reflection exception that is caused when it is creating a new instance of the domain.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_CONVERTING_TO_METHOD

Cause: Method <methodName> not found with parameters () or (Session). TopLink wraps the Java reflection exception that is caused when it is creating a Method type from the method names in transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_FIELD_WHILE_INITIALIZING_ATTRIBUTES_ IN_INSTANCE_VARIABLE_ACCESSOR

Cause: The instance variable <attributeName> is not defined in the domain class or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Field type from the attribute name.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ ATTRIBUTES_IN_METHOD_ACCESSOR

Cause: The accessor method <setMethodName> or <getMethodName> is not defined for the attribute in the domain class <javaClassName>, or it is not accessible. TopLink wraps the Java reflection exception that is caused when it is creating a Method type from the method name.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ CLASS_EXTRACTION_METHOD

Cause: The static class extraction method <methodName> with <databaseRow> as argument does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when class extraction method is being created from the method name in inheritance policy.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_COPY_POLICY

Cause: The clone method <methodName> with no arguments does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when a method to create clones is being created from the method name in copy policy.

Action: Inspect the internal exception and check the Java manuals.

NO_SUCH_METHOD_WHILE_INITIALIZING_ INSTANTIATION_POLICY

Cause: The instance creation method <methodName> with no arguments does not exist, or is not accessible. Java reflection exception wrapped in TopLink exception is thrown when a method to create new instances is being created from the method name in instantiation policy.

Action: Inspect the internal exception and check the Java manuals.

NO_TARGET_FOREIGN_KEYS_SPECIFIED

Cause: The foreign keys in the target table are not specified in one-to-many mappings. These fields are not required if a selection criterion is given in the mapping but otherwise they must be specified.

Action: Set target foreign keys or selection criteria.

NO_TARGET_RELATION_KEYS_SPECIFIED

Cause: There are no target relation keys specified in many-to-many mappings.

Action: Call method to set the fields.

NOT_DESERIALIZABLE

Cause: The object cannot be de-serialized from the byte array read from the database. The exception is thrown when serialized object mapping is converting byte array into object.

Action: Inspect the internal exception and check the Java manuals.

NOT_SERIALIZABLE

Cause: The object cannot be serialized into byte array. The exception is thrown when serialized object mapping is object into byte array.

Action: Inspect the internal exception and check the Java manuals.

NULL_FOR_NON_NULL_AGGREGATE

Cause: Value of aggregate in the source object <object> is null. Null values not allowed for aggregate mappings unless allow null is specified in aggregate mapping.

Action: Call method ) on the mapping.

NULL_POINTER_WHILE_GETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: An object is accessed to get the value of an instance variable through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_GETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: The get accessor method is invoked to get the value of attribute through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_SETTING_VALUE_THRU_ INSTANCE_VARIABLE_ACCESSOR

Cause: Null Pointer Exception is thrown while setting value of <attributeName> instance variable in the object to value. An object is accessed to set the value of an instance variable through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_SETTING_VALUE_THRU_ METHOD_ACCESSOR

Cause: Null Pointer Exception is thrown while setting value through <setMethodName> method in the object with argument <argument>. The set accessor method is invoked to set the value of attribute through Java reflection. This exception is thrown only on some VMs.

Action: Inspect the internal exception and check the Java manuals.

PARENT_DESCRIPTOR_NOT_SPECIFIED

Cause: Cannot find descriptor for parent class. The descriptor of a subclass has no parent descriptor.

Action: The method on the subclass descriptor must be called.

PRIMARY_KEY_FIELDS_NOT_SPECIFIED

Cause: The primary key fields are not set for this descriptor.

Action: Add primary key field names using method or .

REFERENCE_CLASS_NOT_SPECIFIED

Cause: The reference class is not specified in the foreign reference mapping.

Action: Set reference class by calling method

REFERENCE_DESCRIPTOR_IS_NOT_AGGREGATE

Cause: The referenced descriptor for <className> should be set to aggregate descriptor. An aggregate mapping should always reference a descriptor that is aggregate.

Action: Call method on the referenced descriptor.

REFERENCE_KEY_FIELD_NOT_PROPERLY_SPECIFIED

Cause: The table for the reference field must be the reference table. If the reference field name specified in the direct collection mapping is qualified with the table name then the table name should match the reference table name.

Action: Qualify the field with the proper name or change the reference table name.

REFERENCE_TABLE_NOT_SPECIFIED

Cause: The reference table name in the direct collection mapping is not specified.

Action: Use method on the mapping to set the table name.

RELATION_KEY_FIELD_NOT_PROPERLY_SPECIFIED

Cause: The table for the relation key field must be the relation table. If the source and target relation fields name specified in the many to many mapping are qualified with the table name then the table name should match the relation table name.

Action: Qualify the field with the proper name or change the relation table name.

RETURN_TYPE_IN_GET_ATTRIBUTE_ACCESSOR

Cause: The method <attributeMethodName> specified in the transformation mapping should have a return type set in the attribute because this method is used to extract value from the database row.

Action: Check the method and make appropriate changes.

SECURITY_ON_FIND_METHOD

Cause: The descriptor callback method <selector> with DescriptorEvent as argument is not accessible. Java throws security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object that takes DescriptorEvent as its parameter.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_ON_FIND_OBSOLETE_METHOD

Cause: The descriptor callback method <selector> with <session> as argument is not accessible. Java throws security exception when a Method type is created from the method name using Java reflection. The method is a descriptor event callback on the domain object which takes class and session as its parameters.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_ON_INITIALIZING_ATTRIBUTE_METHOD

Cause: Access to the method <attributeMethodName> with parameters <databaseRow> or <databaseRow, Session> has been denied. Java throws security exception when a Method type is created from the attribute method name using Java reflection. The attribute method specified in the transformation mapping is used to extract value from the database row and set by calling .

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_CONVERTING_TO_METHOD

Cause: Method: <methodName> ACCESS DENIED with <> or <session> parameters. Java throws security exception when a Method type is created from the method name using Java reflection. These are the methods that will extract the field value from the domain object in the transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_ INSTANCE_VARIABLE_ACCESSOR

Cause: Access to the instance variable, <attributeName> in the class <javaClassName> is denied. Java throws security exception when creating Field type from the given attribute name using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_ATTRIBUTES_IN_ METHOD_ACCESSOR

Cause: The methods <setMethodName> and <getMethodName> in the object <javaClassName> are inaccessible. Java throws security exception when creating Method type from the given attribute accessor method name using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_CLASS_ EXTRACTION_METHOD

Cause: The static class extraction method <methodName> with DatabaseRow as argument is not accessible. Java throws security exception when creating Method type from the given class extraction method name using Java reflection. The method is used to extract class from the database row in inheritance policy.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_COPY_POLICY

Cause: The clone method <methodName> with no arguments is not accessible. Java throws security exception when creating Method type from the given method name using Java reflection. This method on copy policy is used to create clones of the domain object.

Action: Inspect the internal exception and check the Java manuals.

SECURITY_WHILE_INITIALIZING_INSTANTIATION_POLICY

Cause: The instance creation method <methodName> with no arguments is not accessible. Java throws security exception when creating Method type from the given method name using Java reflection. This method on instantiation policy is used to create new instances of the domain object.

Action: Inspect the internal exception and check the Java manuals.

SEQUENCE_NUMBER_PROPERTY_NOT_SPECIFIED

Cause: Either the sequence field name or the sequence number name is missing. To use sequence generated ids both the sequence number name and field name properties must be set.

Action: To use sequence-generated ids, both the sequence number name and field name properties must be set.

SIZE_MISMATCH_OF_FOREIGN_KEYS

Cause: The size of the primary keys on the target table does not match the size of the foreign keys on the source in one to one mapping.

Action: Check the mapping and the reference descriptor's primary keys.

TABLE_NOT_PRESENT

Cause: The table <tableName> is not present in the descriptor.

Action: Check the qualified field names specified in the mappings and descriptor, if these fields are qualified with the table name then those fields should have right table.

TABLE_NOT_SPECIFIED

Cause: No table is specified in the descriptor. Descriptor must have a table name defined.

Action: Call method or to set the tables on the descriptor.

TARGET_FOREIGN_KEYS_SIZE_MISMATCH

Cause: The size of the foreign keys on the target table does not match the size of the source keys on the source table in one to many mapping.

Action: Check the mapping.

TARGET_INVOCATION_WHILE_CLONING

Cause: Problem in cloning the object <domainObject> clone method. <methodName> triggered an exception. Java is throwing exception when clone method is invoked using Java reflection while cloning object. The clone method is specified on the copy policy that is usually invoked to create clones in unit of work.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_EVENT_EXECUTION

Cause: The underlying descriptor callback method <eventMethodName> with DescriptorEvent as argument, throws an exception. Java is throwing exception when descriptor event method is invoked using Java reflection.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_GETTING_VALUE_ THRU_METHOD_ACCESSOR

Cause: The method <methodName> on the object <objectName> is throwing an exception. Java is throwing exception while getting an attribute value from the object through method accessor.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INSTANTIATING_ METHOD_BASED_PROXY

Cause: Method has thrown an exception. Java is throwing exception while instantiating method based proxy. This happens while instantiating transformation mapping.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_ ATTRIBUTE_METHOD

Cause: The underlying method throws an exception. Java is throwing exception while invoking attribute transformation method on transformation mapping. The method is invoked to extract value from the database row to set into the domain object.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_FIELD_ TO_METHOD

Cause: The method <methodName> is throwing an exception. Java is throwing exception while invoking field transformation method on transformation mapping. The method is invoked to extract value from the domain object to set into the database row.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_INVOKING_ROW_ EXTRACTION_METHOD

Cause: Problem in extracting class from row <row>, static method, <method> with <databaseRow as argument>. An exception was triggered Java is throwing exception while invoking class extraction method. The method is used to extract class type so that right kind of object can be created in inheritance model.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance. Creation method <methodName> caused an exception. Java is throwing exception while invoking instantiation method. The method is used to create new instances of the domain objects.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_OBSOLETE_ EVENT_EXECUTION

Cause: The underlying descriptor callback method <eventMethodName> with <session> as argument, throws an exception. Java is throwing exception while invoking descriptor event method that takes session as its parameter.

Action: Inspect the internal exception and check the Java manuals.

TARGET_INVOCATION_WHILE_SETTING_VALUE_THRU_ METHOD_ACESSOR

Cause: The method <setMethodName> on the object is throwing an exception. Java is throwing exception while invoking set accessor method on the domain object to set an attribute value into the domain object.

Action: Inspect the internal exception and check the Java manuals.

VALUE_NOT_FOUND_IN_CLASS_INDICATOR_MAPPING

Cause: The indicator value is not found in the class indicator mapping in the parent descriptor for the class.

Action: Check on the inheritance policy.

WRITE_LOCK_FIELD_IN_CHILD_DESCRIPTOR

Cause: The child descriptor should not have a write lock field defined because it gets it from the parent descriptor.

Action: Check your child descriptor and remove the field.

DESCRIPTOR_IS_MISSING

Cause: The descriptor for the reference class <className> is missing from the mapping.

Action: Check session to see if the descriptor for the reference class was added.

MULTIPLE_TABLE_PRIMARY_KEY_MUST_BE_ FULLY_QUALIFIED

Cause: Multiple table primary key field names must be fully qualified. These fields names are given on the descriptor if it has more than one table.

Action: Specify the field names with table name.

ONLY_ONE_TABLE_CAN_BE_ADDED_WITH_THIS_METHOD

Cause: Only one table can be added through this method.

Action: Use to add multiple tables to descriptor.

NULL_POINTER_WHILE_CONSTRUCTOR_INSTANTIATION

Cause: Inaccessible constructor. Java is throwing this exception while invoking a default constructor to create new instances of the domain object.

Action: Inspect the internal exception and check the Java manuals.

NULL_POINTER_WHILE_METHOD_INSTANTIATION

Cause: Problem in creating new instance <methodName> creation method is not accessible. Java is throwing an exception while calling a method to build new instance of the domain object. This method is given by the user to override the default behavior of creating new instances through class constructor.

Action: Inspect the internal exception and check the Java manuals.

NO_ATTRBUTE_VALUE_CONVERSION_TO_FIELD_VALUE_PROVIDED

Cause: The field conversion value for the attribute value <attributeValue> was not given in the object type mapping.

Action: Check the attribute value and provide a corresponding field value in the mapping.

NO_FIELD_VALUE_CONVERSION_TO_ATTRIBUTE_ VALUE_PROVIDED

Cause: The attribute conversion value for the <fieldValue> was not given in the object type mapping.

Action: Check the field value and provide a corresponding attribute value in the mapping.

LOCK_MAPPING_CANNOT_BE_READONLY

Cause: The domain object <className> cannot have a read only mapping for the write lock fields when the version value is stored in the object.

Action: Check the mappings on write lock fields.

LOCK_MAPPING_MUST_BE_READONLY

Cause: The domain object <className> should have a read only mapping for the write lock fields when the version value is stored in the cache.

Action: Check the mappings on write lock fields.

CHILD_DOES_NOT_DEFINE_ABSTRACT_QUERY_KEY

Cause: The queryKey <queryKeyName> is defined in the parent descriptor but not in the child descriptor. The descriptor has not defined abstract query key.

Action: Any implementors of interface descriptor must define the query key defined by abstract query key in the interface descriptor.

SET_EXISTENCE_CHECKING_NOT_UNDERSTOOD

Cause: The interface descriptor <parent> must have at least one abstract query key defined. The string given to the method is not understood.

Action: The string passed should be one of the following:

  • Check cache
  • Check database
  • Assume existence
  • Assume non-existence

VALUE_HOLDER_INSTANTIATION_MISMATCH

Cause: The mapping for the attribute uses indirection and must be initialized to a new ValueHolder.

Action: Ensure the mapping uses indirection and the attribute is initialized to a new .

NO_SUB_CLASS_MATCH

Cause: No sub-class matches this class <theClass> when inheritance is in aggregate relationship mapping.

Action: Verify the sub-class and the relationship mapping.

RETURN_AND_MAPPING_WITH_INDIRECTION_MISMATCH

Cause: The get method return type for the attribute () is not declared as type , but the mapping is using indirection.

Action: Ensure the get method returns a or change the mapping to not use indirection.

RETURN_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: The get method return type for the attribute is declared as type , but the mapping is not using indirection.

Action: Ensure the mapping is using indirection or change the return type from

PARAMETER_AND_MAPPING_WITH_INDIRECTION_ MISMATCH

Cause: The set method parameter type for the attribute is not declared as type , but the mapping is using indirection.

Action: Ensure the set method parameter is declared as a or the mapping is changed to not use indirection.

PARAMETER_AND_MAPPING_WITHOUT_INDIRECTION_ MISMATCH

Cause: The set method parameter type for the attribute is declared as type , but the mapping is not using indirection.

Action: Ensure the mapping is changed to use indirection or the set method parameter is not declared as a .

GET_METHOD_RETURN_TYPE_NOT_VALID

Cause: he get method return type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

Action: The get method return type for the attribute should be declared as type Vector (or a type that implementsMap or Collection, if using Java2).

SET_METHOD_PARAMETER_TYPE_NOT_VALID

Cause: The set method parameter type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

Action: The set method parameter type for the attribute should be declared as type Vector (or a type that implements Map or Collection, if using Java2).

ILLEGAL_TABLE_NAME_IN_MULTIPLE_TABLE_ FOREIGN_KEY

Cause: The table in the multiple table foreign key relationship refers to an unknown table.

Action: Verify the table name.

ATTRIBUTE_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The attribute is not declared as a super-type of , but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

RETURN_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The get method return type for the attribute is not declared as a super-type of , but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

PARAMETER_AND_MAPPING_WITH_TRANSPARENT_ INDIRECTION_MISMATCH

Cause: The set method parameter type for the attribute is not declared as a super-type of , but the mapping is using transparent indirection.

Action: Verify the attribute's type and the mapping setup.

FIELD_IS_NOT_PRESENT_IN_DATABASE

Cause: Field <fieldname> is not present in the table <tableName> in the database.

Action: Verify the field name for the attribute.

TABLE_IS_NOT_PRESENT_IN_DATABASE

Cause: is not present in the database.

Action: Verify the table name for the descriptor.

MULTIPLE_TABLE_INSERT_ORDER_MISMATCH

Cause: The multiple table insert order Vector specified , has more/fewer tables than are specified in the descriptor . All the tables must be included in the insert order Vector.

Action: Verify that all table names for the descriptor are present and that there are no extras.

INVALID_USE_OF_TRANSPARENT_INDIRECTION

Cause: Transparent Indirection can only be used with CollectionMappings.

Action: Verify the mapping. It must be a collection mapping.

MISSING_INDIRECT_CONTAINER_CONSTRUCTOR

Cause: The indirect container class must implement the constructor.

Action: Implement the constructor for the container.

COULD_NOT_INSTANTIATE_INDIRECT_CONTAINER_CLASS

Cause: The indirect container class could not be instantiated using the constructor.

Action: Validate the constructor for the indirect container class.

INVALID_CONTAINER_POLICY

Cause: This container policy should only be used in JDK containerPolicy. It was instantiated for javaClass.

Action: Validate the container policy being used.

INVALID_CONTAINER_POLICY_WITH_TRANSPARENT_ INDIRECTION

Cause: The container policy is incompatible with transparent indirection.

Action: Change the container policy to be compatible with transparent indirection or do not use transparent indirection.

INVALID_USE_OF_NO_INDIRECTION

Cause: No Indirection should not receive this message.

Action: Change to use no indirection.

INDIRECT_CONTAINER_INSTANTIATION_MISMATCH

Cause: The mapping for the attribute uses transparent indirection and must be initialized to an appropriate container.

Action: Initialize the mapping to an appropriate container.

INVALID_MAPPING_OPERATION

Cause: Invalid mapping operation.

Action: Check the documentation for valid mapping operations.

INVALID_INDIRECTION_POLICY_OPERATION

Cause: Invalid indirection policy operation.

Action: Check the documentation for valid indirection policy operations.

REFERENCE_DESCRIPTOR_IS_NOT_ AGGREGATECOLLECTION

Cause: The reference descriptor for <className> should be set to aggregate collection descriptor.

Action: Set the reference descriptor to an aggregate collection descriptor.

INVALID_INDIRECTION_CONTAINER_CLASS

Cause: Invalid indirection container class.

Action: Verify the container class.

MISSING_FOREIGN_KEY_TRANSLATION

Cause: The mapping does not include a foreign key field linked to the primary key field.

Action: Link the foreign key to the appropriate primary key.

TRUCTURE_NAME_NOT_SET_IN_MAPPING

Cause: The structure name is not set.

Action: Set the structure name appropriately.

NORMAL_DESCRIPTORS_DO_NOT_SUPPORT_ NON_RELATIONAL_EXTENSIONS

Cause: Normal descriptors do not support non-relational extensions.

Action: Contact Technical Support.

PARENT_CLASS_IS_SELF

Cause: The descriptor's parent class has been set to itself.

Action: Contact Technical Support.

PROXY_INDIRECTION_NOT_AVAILABLE

Cause: An attempt to use proxy indirection has been made but JDK is not being used.

Action: Proxy indirection is only supported in JDK

INVALID_ATTRIBUTE_TYPE_FOR_PROXY_INDIRECTION

Cause: The attribute wasn't specified in the list of interfaces given to use Proxy Indirection.

Action: Verify the attribute

INVALID_GET_RETURN_TYPE_FOR _PROXY_INDIRECTION

Cause: The return type for the indirection policy is invalid for the indirection policy.

Action: Verify that the parameter type of the attribute's get method is correct for the indirection policy.

INVALID_SET_PARAMETER_TYPE_FOR_PROXY_ INDIRECTION

Cause: The parameter for the set method is incorrect for the indirection type.

Action: Verify that the parameter type of the attribute's set method is correct for the indirection policy.

INCORRECT_COLLECTION_POLICY

Cause: The container policy is invalid for the collection type.

Action: Check that the container policy is correct for the collection type.

INVALID_AMENDMENT_METHOD

Cause: The amendment method provided is invalid, not public, or cannot be found.

Action: Ensure the amendment method is public, static, returns void and has a single argument: Descriptor.

ERROR_OCCURRED_IN_AMENDMENT_METHOD

Cause: The specified amendment method threw an exception.

Action: Examine the returned exception for further details.

VARIABLE_ONE_TO_ONE_MAPPING_IS_NOT_DEFINED

Cause: There is no mapping for attribute.

Action: Validate the mapping and attribute.

TARGET_INVOCATION_WHILE_CONSTRUCTOR_ INSTANTIATION

Cause: Constructor is missing.

Action: Make the required constructor.

TARGET_INVOCATION_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: Constructor is missing.

Action: Make the required constructor.

ILLEGAL_ACCESS_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: Permissions do not permit access to the constructor.

Action: Adjust the Java security permissions to permit access to the constructor.

INSTANTIATION_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: An instantiation failed inside the associated constructor.

Action: Determine which objects are being instantiated, and ensure all are being done properly.

NO_SUCH_METHOD_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: A message send invoked from inside the constructor is invalid because the method does not exist.

Action: Correct the message send ensuring that the message exists.

NULL_POINTER_WHILE_CONSTRUCTOR_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent from inside a constructor to a null object.

Action: Avoid sending a message to an object that is null.

ILLEGAL_ACCESS_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent to an object from inside a factory instantiation. Java has determined this message to be illegal.

Action: Determine why the message send is illegal, and replace the message with the proper legal one.

TARGET_INVOCATION_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: Error inside the factory associated with the invocation of a target.

Action: Determine the faulty target, and replace with the correct target, or proper message send.

NULL_POINTER_WHILE_METHOD_ INSTANTIATION_OF_FACTORY

Cause: A message is being sent to null inside a factory instantiation.

Action: Avoid sending a message to null.

No such method

Cause: Tokens in the builder generated files are the subsets of all the tokens a Project Reader can understand. Each token has a related public method on TopLink. The exception would mean that the method name is incorrect.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not find post load method <methodName> on class <aClass>

Cause: The post load method defined in descriptor properties is not defined on the related domain class.

Action: Must define the method on the specified class.

Cannot write parameter <object> of class <type>

Cause: While creating project class the parameter tokens are read from the file and are converted to actual types before sending them to the methods. An unknown type will cause this exception.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not access method <method>

Cause: Java is throwing an illegal access reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invoking <applyResultMethod> raised exception <exception>

Cause: Java is throwing an invocation reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invalid arguments invoking: <applyResultMethod> with <receiver>

Cause: Java is throwing an invalid argument reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not access <applyResultMethod> with <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Parameter mismatch <method>; received <size> parameters

Cause: The number of parameters for the token read from the project or descriptor file do not match the number of parameters a related method can take.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Accessing <methodName> on <className> with <parameters>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not find section definition <section> when building section definitions for <target>

Cause: Invalid section name was found in the project or descriptor file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Could not convert <object> into an accessible Java class.

Cause: The parameter read from the file cannot be converted to a appropriate type.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

File not found

Cause: The project or descriptor file was not found.

Action: Check that the path was given correctly in a project reader and also the path is correct in project file.

Invalid class/method name format.

Cause: No one should actually be using the URL way of reading INI files. This is untested and undocumented feature.

Action: Use other ways of reading files.

Open failed for URL <url>

Cause: Open failed for URL.

Action: Inspect the internal exception and check the Java manuals.

Could not resolve INIFile location: <sourceString> using search paths <searchPaths>

Cause: The file was not found on the given search paths.

Action: Check your search paths.

Invoking <method> on <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invoking <method> on <receiver>

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Invalid character value; expecting $* format

Cause: An invalid character format was written to the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected character: {

Cause: Unexpected character { found while reading vector values from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected character: }

Cause: Unexpected character } found while reading vector values from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Expecting object, found token <nextToken>

Cause: Unexpected token found while reading from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Unexpected word

Cause: Unexpected token found while reading from the file.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

setExistenceChecking <token>; not understood

Cause: Existence checking string specified on the descriptor is not understood.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Class <className> not found

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals. If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Not enough INI elements. Found <count>.

Cause: If the line in an INI file is incomplete, i.e., it does not have enough tokens.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Too many INI elements. Found <count>.

Cause: If the line in an INI file has more tokens then needed.

Action: If the project files are not manually edited and corrupted then this is usually an internal exception to TopLink and must be reported to Technical Support. But if the file was manually edited or corrupted then the files must be generated again.

Error writing <writeString>

Cause: Could not write into the file. Perhaps are used and file or directory structure does not exist.

Action: Inspect the internal exception and check the Java manuals. Try using .

Illegal access exception

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Invocation target exception

Cause: Java is throwing reflection exception while invoking the method on the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Attempting to instantiate <className> with default constructor.

Cause: Java is throwing reflection exception while instantiating the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Attempting to instantiate <className> with default constructor.

Cause: Java is throwing reflection exception while instantiating the object. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

IO Exception in next token

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

IOException on close.

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Invalid INI(URL) Method: <method>. Should return a string.

Cause: No one should actually be using the URL way of reading INI files. This is untested and undocumented feature.

Action: Use other ways of reading files.

Could not cast using <castString>.

Cause: An error occurred during an attempt to cast using the

Action: Validate the

A writer or a target file name must be specified

Cause: A writer or a target file name is not specified.

Action: A writer or a target file name must be specified.

IOException on open.

Cause: Java is throwing reflection. TopLink only wraps that exception.

Action: Inspect the internal exception and check the Java manuals.

Post Load Method Not Static

Cause: The method specified is not static.

Action: Modify the method to be static.

Project Not Found.

Cause: No projects were found in the specified directory.

Action: Verify the directory.

Multiple Projects With Name.

Cause: More than one project with the same name was found.

Action: Verify the project name.

WAIT_WAS_INTERRUPTED

Cause: In a multi threaded environment one of the waiting thread was interrupted.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

WAIT_FAILURE_SERVER

Cause: Wait failure on ServerSession. When the number of non-pooled connections reach the threshold any more requests for such connection results in wait until some one releases the connection resource. If this wait was interrupted then an exception is thrown.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

WAIT_FAILURE_CLIENT

Cause: Wait failure on ClientSession. When the number of pooled connections reach the threshold any more requests for such connection results in wait until some one releases the connection resource. If this wait was interrupted then an exception is thrown.

Action: Usually such exceptions would mean restarting the application but it is totally dependent on the application.

SIGNAL_ATTEMPTED_BEFORE_WAIT

Cause: A signal was attempted before wait on concurrency manager. This normally means that an attempt was made to commit or rollback a transaction before it was started, or to rollback a transaction twice.

Action: Check transactions in the application.

COULD_NOT_BE_CONVERTED

Cause: The object <object> of class <objectClass> could not be converted to <javaClass>. The object cannot be converted to given type.

Action: Check that the object being converted is of right type or not.

INCORRECT_DATE_FORMAT

Cause: The date in <dateString> is in an incorrect format. Expected format is YYYY-MM-DD.

Action: Check the date format.

INCORRECT_TIME_FORMAT

Cause: The time in <timeString> is in an incorrect format. Expected format is HH:MM:SS.

Action: Check the time format.

INCORRECT_TIMESTAMP_FORMAT

Cause: The timestamp <timestampString> is in an incorrect format. Expected format is YYYY-MM-DD HH:MM:sprers.euNNN.

Action: Check the timestamp format.

COULD_NOT_CONVERT_TO_BYTE_ARRAY

Cause: The String object must be of even length to be converted to a ByteArray. This object could not be converted to a ByteArray

Action: Check the object being converted.

COULD_NOT_BE_CONVERTED_TO_CLASS

Cause: The object <object> of class <objectClass> could not be converted to <javaClass>. The class <javaClass> is not on the CLASSPATH.

Action: Check that the class <javaClass> is on the CLASSPATH.

SQL_EXCEPTION

Cause: An SQL exception was encountered, thrown by the underlying JDBC bridge. TopLink only wraps that exception.

Action: One must inspect the internal exception thrown.

CONFIGURATION_ERROR_CLASS_NOT_FOUND

Cause: The driver class name was not found.

Action: Check the class name given in JDBCLogin.

DATABASE_ACCESSOR_NOT_CONNECTED

Cause: Session is not connected to the database while doing reading or writing on the database.

Action: An application may have to login again because the connection to the database might have been lost.

ERROR_READING_BLOB_DATA

Cause: Error reading blob data from the database. There are two possibilities for this exception, first is that the blob data was not read properly from the result set or the TopLink could not process the blob data using .

Action: Check if the underlying driver support blobs properly or not and if it does then report this problem to Technical Support.

OULD_NOT_CONVERT_OBJECT_TYPE

Cause: Could not convert object type on internal error. sprers.eu = <type>. The object from the result set cannot be converted to the type returned from the metadata information.

Action: Check if the underlying driver support the conversion type properly or not and if it does then report this problem to Technical Support.

LOGOUT_WHILE_TRANSACTION_IN_PROGRESS

Cause: An attempt has been made to logout while the transaction is still in progress. You cannot logout while a transaction is in progress.

Action: Wait until the transaction is over.

SEQUENCE_TABLE_INFORMATION_NOT_COMPLETE

Cause: The sequence information given to TopLink is not sufficiently complete to get the set of sequence numbers from the database. This usually happens on native sequencing on oracle database.

Action: Check the data given specially the sequence name given in TopLink.

ERROR_PREALLOCATING_SEQUENCE_NUMBERS

Cause: Error preallocating sequence numbers on the database; the sequence table information is not complete.

Action: Check if the sequence table was created on the database properly or not.

CANNOT_REGISTER_SYNCHRONIZATIONLISTENER_ FOR_UNITOFWORK

Cause: Cannot register Synchronization Listener: underlying_exception_string. When the TopLink Session is configured with an , any unit of work requested by a client must operate within the context of a JTS external global transaction. When a unit of work is created and the external global transaction is not in existence or if the system cannot acquire a reference to it, this error is reported.

Action: Ensure that a JTS transaction is in progress before acquiring the unit of work.

SYNCHRONIZED_UNITOFWORK_DOES_NOT_ SUPPORT_COMMITANDRESUME

Cause: Synchronized does not support the operation. When the TopLink Session is configured with an , any unit of work requested by a client must operate within the context of a JTS external global transaction (see Error code: ). The JTS specification does not support the concept of "checkpointing" a transaction, that is, committing the work done and then continuing to work within the same transaction context (JTS does not support nested transactions, either). Thus, if client code invokes on a "synchronized" unit of work, this error will be reported.

Action: None.

CONFIGURATION_ERROR_NEW_INSTANCE_ INSTANTIATION_EXCEPTION

Cause: Configuration error. Attempting to instantiate Driver: <javaClass>. Could not instantiate driver.

Action: Check the driver.

CONFIGURATION_ERROR_NEW_INSTANCE_ILLEGAL_ ACCESS_EXCEPTION

Cause: A configuration error occurred while attempting to instantiate . Could not instantiate driver.

Action: Check the driver.

TRANSACTION_MANAGER_NOT_SET_FOR_JTS_DRIVER

Cause: The transaction manager has not been set for the .

Action: Set a transaction manager for the .

NO_VERSION_NUMBER_WHEN_DELETING

Cause: An attempt was made to delete the object <object> but it has no version number in the identity map. This object either was never read or has already been deleted.

Action: Logging SQL is very helpful in understanding the reason why the exception is thrown. The last delete will show the object we are deleting that throws an exception.

OBJECT_CHANGED_SINCE_LAST_READ_WHEN_DELETING

Cause: The object state has changed in the database. The object <object> cannot be deleted because it has changed or been deleted since it was last read. This usually means that the row in the table was changed by some other application.

Action: Refreshing an object will refresh the object with the new data from the database.

NO_VERSION_NUMBER_WHEN_UPDATING

Cause: An attempt has been made to update the object <object> but it has no version number in the identity map. It may not have been read before being updated or has been deleted.

Action: Logging SQL is very helpful in understanding the reason why the exception is thrown. The last update will show the object we are updating that throws an exception.

OBJECT_CHANGED_SINCE_LAST_READ_WHEN_UPDATING

Cause: The object state has changed in the database. The object <object> cannot be updated because it has changed or been deleted since it was last read. This usually means that the row in the table was changed by some other application.

Action: Refreshing an object will refresh the object with the new data from the database.

MUST_HAVE_MAPPING_WHEN_IN_OBJECT

Cause: The object <aClass> must have a non-read-only mapping corresponding to the version lock field. The mapping was not defined for the locking field. It is needed when the lock value is stored in the domain object than in a cache.

Action: Define a mapping for the field.

NEED_TO_MAP_JAVA_SQL_TIMESTAMP

Cause: A write lock value which is stored in a domain object is not an instance of.

Action: Change the value of the attribute to be an instance of .

ADDITIONAL_SIZE_QUERY_NOT_SPECIFIED

Cause: Cursored SQL queries must provide an additional query to retrieve the size of the result set. Custom queries using cursor streams and not specifying the size query will cause this exception. The size query is used to retrieve the size of the number of object read from the database. This is done on JDBC compatible drivers because it provides no way to extract the size of the result set read. Non custom queries using cursor streams will have default queries generated by TopLink.

Action: Specify a size query.

AGGREGATE_OBJECT_CANNOT_BE_DELETED

Cause: Aggregated objects cannot be written or deleted independent of their owners. There is no identity maintained on such objects.

Action: Application's discretion.

ARGUMENT_SIZE_MISMATCH_IN_QUERY_AND_ QUERY_DEFINITION

Cause: The number of arguments provided to the query for execution does not match the number of arguments provided with the query definition.

Action: Check the query and query execution.

BACKUP_CLONE_IS_ORIGINAL_FROM_PARENT

Cause: The object of class with identity hashcode is not from this unit of work space but from the parent session. The object was never registered in this unit of work but read from the parent session and related to an object registered in the unit of work.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

BACKUP_CLONE_IS_ORIGINAL_FROM_SELF

Cause: The object clone of class with identity hashcode is the original to a registered new object. The unit of work clones registered new objects, so you must ensure that it is registered before it is reference by another object. If you do not want the new object to be cloned, used the U API.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

BATCH_READING_NOT_SUPPORTED

Cause: This mapping does not support batch reading. The optimization of batching the read of all the target rows is not supported for the mapping.

Action: The problem is a TopLink development problem and user should never encounter this unless the mapping is a new custom mapping. Contact Technical Support.

DESCRIPTOR_IS_MISSING

Cause: Missing descriptor for <reference Class>. The descriptor related to the class or the object is not found in the session.

Action: Check if the related descriptor was added to the session or the query is done on the right object or class.

DESCRIPTOR_IS_MISSING_FOR_NAMED_QUERY

Cause: Missing descriptor for <domain Class Name> for query named <queryName>. The descriptor where named query is defined is not added to the session.

Action: Check if the related descriptor was added to the session or the query is done on the right class.

INCORRECT_SIZE_QUERY_FOR_CURSOR_STREAM

Cause: The size query given on the queries returning cursor streams is not correct. The execution of the size query did not return any size.

Action: If the cursor stream query was custom query than check the size query specified else report this problem to Technical Support.

INVALID_QUERY

Cause: Objects cannot be written in unit of work using modify queries, they must be registered.

Action: Objects are registered in the unit of work and during commit unit of work will do the required changes to the database.

INVALID_QUERY_KEY_IN_EXPRESSION

Cause: The query key <key> does not exist. Usually this happens because of mis-spelled query key.

Action: Check the query key specified in the expression and make sure that a query key was added to the descriptor.

INVALID_QUERY_ON_SERVER_SESSION

Cause: Objects and the database cannot be changed through the server session; all changes must be done through a client session's unit of work. The objects cannot be changed on the server session by modifying queries. Objects are changed in the client sessions acquired from this server session.

Action: Use client session's unit of work to change the object.

NO_CONCRETE_CLASS_INDICATED

Cause: No concrete class indicated for the type in this row. The type indicator read from the database row has no entry in the type indicator hashtable or if class extraction method was used, it did not return any concrete class type. The exception is thrown when sub classes are being read.

Action: Check class extraction method if specified or check the descriptor to see if all the type indicator values were specified or not.

NO_CURSOR_SUPPORT

Cause: No cursor support provided for abstract class multiple table descriptors using expressions.

Action: Consider using custom SQL or multiple queries. <query>

OBJECT_TO_INSERT_IS_EMPTY

Cause: There are no fields to be insert into the table. The fields to insert into the table, <table> is empty. You must define at least one mapping for this table

Action: Must define at least one mapping for this table.

OBJECT_TO_MODIFY_NOT_SPECIFIED

Cause: An object to modify is required for a modify query.

Action: Ensure the query contains an object before executing.

QUERY_NOT_DEFINED

Cause: Query is not defined. When executing query on the session the parameter which takes query is null.

Action: Check if the query is passed properly.

QUERY_SENT_TO_INACTIVE_UNIT_OF_WORK

Cause: The unit of work has been released and is now inactive.

Action: The unit of work, once released, cannot be reused unless commitAndResume is called.

READ_BEYOND_QUERY

Cause: An attempt has been made to read from the cursor streams beyond its limits (beyond the end of the stream).

Action: Ensure the stream is being checked for an "end of stream" condition before attempting to retrieve more objects.

REFERENCE_CLASS_MISSING

Cause: The reference class in the query is not specified. A reference class must be provided.

Action: Check the query.

REFRESH_NOT_POSSIBLE_WITHOUT_CACHE

Cause: Refresh is not possible if caching is not set. The read queries which skip cache to read objects cannot be used to do refresh the object. Refreshing is not possible without identity.

Action: Check query.

SIZE_ONLY_SUPPORTED_ON_EXPRESSION_QUERIES

Cause: Did not find size query. Size only supported on expression queries, unless a size query is given.

Action: Cursor streams on custom query should also define size query.

SQL_STATEMENT_NOT_SET_PROPERLY

Cause: The SQL statement has not been properly set. The user should never encounter this unless queries have been customized.

Action: Contact Technical Support.

INVALID_QUERY_ITEM

Cause: Invalid query item expression.

Action: Validate the Expression being used.

SELECTION_OBJECT_CANNOT_BE_NULL

Cause: The selection object passed to a read object or refresh was null.

Action: Check on the read query.

UNNAMED_QUERY_ON_SESSION_BROKER

Cause: Data read and data modify queries is being executed without the session name. Only object-level queries can be directly executed by the session broker, unless the query is named.

Action: Session broker has no idea about such queries about which session to execute the query on. Specify the session name.

REPORT_RESULT_WITHOUT_PKS

Cause: ReportQuery without PKs cannot readObject. The report query result returned is without primary key values. An object from the result can only be created only if primary keys were also read.

Action: Check documentation on on report query.

NULL_PRIMARY_KEY_IN_BUILDING_OBJECT

Cause: The primary key read from the row, <databaseRow> during the execution of the query was detected to be null; primary keys must not contain null.

Action: Check query and also the table on the database.

NO_DESCRIPTOR_FOR_SUBCLASS

Cause: The subclass has no descriptor defined for it.

Action: Check session if the descriptor was added or not or else check class extraction method.

CANNOT_DELETE_READ_ONLY_OBJECT

Cause: Cannot delete an object of read-only class. The class <className> is declared read-only in this unit of work. Thrown in unit of work when trying to delete an object that is marked as read only.

Action: Contact Technical Support.

INVALID_OPERATOR

Cause: The operator <data> used in the expression is not valid.

Action: Check class to see a list of all of the operators supported.

ILLEGAL_USE_OF_GETFIELD

Cause: Illegal use of <data> in expression. This is a TopLink development exception that users should not encounter.

Action: Report this problem to Technical Support.

ILLEGAL_USE_OF_GETTABLE

Cause: Illegal use of <data> in expression. This is a TopLink development exception that users should not encounter.

Action: Report this problem to Technical Support.

REPORT_QUERY_RESULT_SIZE_MISMATCH

Cause: The number of attributes requested does not match the attributes returned from the database in report query. This usually happens if one gives custom query on the report query.

Action: Check the custom query if it is specified or report this problem to Technical Support.

CANNOT_CACHE_PARTIAL_OBJECT

Cause: Partial Objects are never put in the cache. Partial object queries are not allowed to maintain the cache or be edited. You must set .

Action: Call the method before executing the query.

OUTER_JOIN_ONLY_VALID_FOR_ONE_TO_ONE

Cause: An outer join () is only valid for one to one mappings, and cannot be used for the mapping.

Action: Do not attempt to use for mappings other than one to one.

CANNOT_ADD_TO_CONTAINER

Cause: Cannot add <anObject> to a <containerClass> using <policy>. This is TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

METHOD_INVOCATION_FAILED

Cause: The method invocation of <aMethod> on the object <anObject> threw a Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CANNOT_CREATE_CLONE

Cause: Cannot create a clone of <anObject> using <policy>. This is a TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Report this problem to Technical Support.

METHOD_NOT_VALID

Cause: The method <methodName> is not valid to call on object <aReceiver>. This is a TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

METHOD_DOES_NOT_EXIST_IN_CONTAINER_CLASS

Cause: The method named <methodName> was not found in class <aClass>. Thrown when looking for clone method on the container class. The clone is needed to create clones of the container in unit of work.

Action: Define clone method on the container class.

COULD_NOT_INSTANTIATE_CONTAINER_CLASS

Cause: The class <aClass> cannot be used as the container for the results of a query since it cannot be instantiated. Thrown when new interface container policy is being created using Java reflection.

Action: Check Java documentation on the internal exception.

MAP_KEY_NOT_COMPARABLE

Cause: Could not use object <anObject> of type <objectClass> as a key into <aContainer> which is of type <containerClass>. Key cannot be compared with the keys currently in the map. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CANNOT_ACCESS_METHOD_ON_OBJECT

Cause: Cannot reflectively access the method <aMethod> for object: <anObject> of type <anObjectClass>. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

CALLED_METHOD_THREW_EXCEPTION

Cause: The method <aMethod> was called reflectively on object <object> of class <objectClass> and threw an exception. Throws Java reflection exception while accessing method.

Action: Check Java documentation on the internal exception.

INVALID_OPERATION

Cause: Invalid operation <operation> on cursor. The operation is not supported.

Action: Check the class documentation and look for the corresponding method that should be used.

CANNOT_REMOVE_FROM_CONTAINER

Cause: Cannot remove <anObject> of type <anObjectClass> from <aContainerClass> using <policy>. This is TopLink development exception and user should never encounter this problem unless a custom container policy has been written.

Action: Contact Technical Support.

CANNOT_ADD_ELEMENT

Cause: Cannot add element to the collection container policy (cannot add <anObject> of type <anObjectClass> to a <aContainerClass>).

Action: Check Java documentation on the internal exception.

BACKUP_CLONE_DELETED

Cause: Deleted objects cannot have reference after being deleted. The object clone of class <sprers.euss()> with identity hashcode (sprers.eutyHashCode()) <sprers.eutyHashCode(clone)> has been deleted, but still has references.

Action: Ensure that you are correctly registering your objects. If you are still having problems, you can use the method to help debug where the error occurred. Please see the manual and FAQ for more information.

CANNOT_COMPARE_TABLES_IN_EXPRESSION

Cause: Cannot compare table reference to <data> in expression

Action: Check the expression

INVALID_TABLE_FOR_FIELD_IN_EXPRESSION

Cause: Field has invalid table in this context for field <data> in expression.

Action: Check the expression

INVALID_USE_OF_TO_MANY_QUERY_KEY_IN_EXPRESSION

Cause: Invalid use of a query key representing a to-many relationship <data> in expression. Use rather than .

Action: Use the operator instead of .

INVALID_USE_OF_ANY_OF_IN_EXPRESSION

Cause: Invalid use of for a query key not representing a to-many relationship <data> in expression. Use rather than .

Action: Use the operator instead of .

CANNOT_QUERY_ACROSS_VARIABLE_ONE_TO_ ONE_MAPPING

Cause: Querying across a variable one-to-one mapping is not supported.

Action: Change the expression such that the query in not done across a variable one to one mapping.

ILL_FORMED_EXPRESSION

Cause: Ill-formed expression in query, attempting to print an object reference into a SQL statement for <queryKey>.

Action: Contact Technical Support.

CANNOT_CONFORM_EXPRESSION

Cause: This expression cannot determine if the object conforms in memory, you must set the query to check the database.

Action: Change the query such that it does not attempt to conform to the results of the query.

INVALID_OPERATOR_FOR_OBJECT_EXPRESSION

Cause: Object comparisons can only use the or operators, other comparisons must be done through query keys or direct attribute level comparisons.

Action: Ensure the query uses only and if object comparisons are being used.

UNSUPPORTED_MAPPING_FOR_OBJECT_COMPARISON

Cause: Object comparisons can only be used with mappings; other mapping comparisons must be done through query keys or direct attribute level comparisons.

Action: Use a query key instead of attempting to compare objects across the mapping.

OBJECT_COMPARISON_CANNOT_BE_PARAMETERIZED

Cause: Object comparisons cannot be used in parameter queries.

Action: Change the query such that it does not attempt to use object when using parameterized queries.

INCORRECT_CLASS_FOR_OBJECT_COMPARISON

Cause: The class of the argument for the object comparison is incorrect.

Action: Ensure the class for the query is correct.

CANNOT_COMPARE_TARGET_FOREIGN_KEYS_ TO_NULL

Cause: Object comparison cannot be used for target foreign key relationships. Query on the source primary key instead.

Action: Query on source primary key.

INVALID_DATABASE_CALL

Cause: Invalid database call - the call must be an instance of DatabaseCall: <call>.

Action: Ensure the call being used is a DatabaseCall.

INVALID_DATABASE_ACCESSOR

Cause: Invalid database accessor - the accessor must be an instance of DatabaseAccessor: <accessor>.

Action: Ensure the accessor being used is a DatabaseAccessor.

METHOD_DOES_NOT_EXIST_ON_EXPRESSION

Cause: Method: <methodName> with argument types: <argTypes> cannot be invoked on Expression.

Action: Ensure the method being used is a supported method.

IN_CANNOT_BE_PARAMETERIZED

Cause: Queries using IN cannot be parameterized.

Action: Either disable the query prepare or binding.

REDIRECTION_CLASS_OR_METHOD_NOT_SET

Cause: The redirection query was not configured properly, the class or method name was not set.

Action: Check the configuration for the redirection class.

REDIRECTION_METHOD_NOT_DEFINED_CORRECTLY

Cause: The redirection query's method is not defined or define with the wrong arguments. It must be public static and have arguments DatabaseQuery, DatabaseRow, Session (the interface).

Action: Check the redirection query's method as above.

REDIRECTION_METHOD_ERROR

Cause: The redirection query's method invocation threw an exception.

Action: Check the redirection method for problems.

EXAMPLE_AND_REFERENCE_OBJECT_CLASS_MISMATCH

Cause: There is a class mismatch between the example object and the reference class specified for this query.

Action:

Why am I getting a or "Message rejected" error with the message "Email address is not verified" from Amazon SES?

To resolve or "Message rejected" errors with the message "Email address is not verified," check the following:

  • Open the Amazon SES console. Confirm that the identity that you're sending emails from has a verification status of verified, not pending or failure. If your identity is stuck in the pending state, see What can I do if my domain is stuck in the "pending verification" status or in the "failed" verification status in Amazon SES?
  • If your email address is verified, check that the email address on the message that resulted in the "Message rejected" error is correct. Email addresses are case-sensitive. The email address that you used to send the message must match your verified email address.
  • Check whether your account is in the Amazon SES sandbox for the AWS Region that you're using to send emails. If your account is in the Amazon SES sandbox, then you must verify the recipient email address in addition to verifying your sender identity. Or, you can request to move your account out of the Amazon SES sandbox.
    Note: If you're using sending authorization policies to delegate sending on behalf of your Amazon SES identity to a non-verified email address, then the delegate sender account must be out of the Amazon SES sandbox. For more information, see Moving out of the Amazon SES sandbox.
  • Confirm that your email-sending method is using the correct AWS Region. Email identity verification is separate for each Region. You must verify the identity that you use to send emails in each Region that you want to send emails from.
  • Confirm that you're connecting to the correct Amazon SES endpoint. Amazon SES has endpoints in several Regions. You must communicate with the endpoint for the Amazon SES SMTP interface or the Amazon SES API in the correct Region.

For more information on issues that can lead to errors when using Amazon SES, see Amazon SES email sending errors.


KMA seems to be running into a core-dumping issue when I’m trying to analyze my metagenomic paired-end reads (total=65 Mio reads) on ResFinder.

I have already rerun ‘python3 sprers.eu’ from inside db_resfinder and I did see filenames with suffix ‘.length.b’ being created there. Below is the command-line I used:

python3 /home/tools/resfinder/run_sprers.eu -o resfinder_output_reads -s “Other” -l -t --acquired -ifq ReadA_sprers.eu ReadA_sprers.eu -k /home/tools/resfinder/kma/kma

Below is the error message I got and under “KMA finished with the following response”, I found only a couple of blank lines. A core dumping file starting with 'sprers.eu” was found inside the main working directory after this error message was displayed.

“Error: KMA did not run as expected.

KMA finished with the following response:”

I tried to run the above on my computational cluster node with --mem=G --cpus-per-task= Resfinder works fine for me though when running in BLAST mode with a metagenomic assembly fasta file as the input. Any help here would be appreciated.

This section lists all errors that can occur when type checking is performed.

Error: Type mismatch

This can happen in many cases:
  • The variable you&#;re assigning to is of a different type than the expression in the assignment.
  • You are calling a function or procedure with parameters that are incompatible with the parameters in the function or procedure definition.
Error: Incompatible types: got &#;arg1&#; expected &#;arg2&#;

There is no conversion possible between the two types. Another possibility is that they are declared in different declarations:

 Var  
    A1 : Array[] Of Integer;  
    A2 : Array[] Of Integer;  
 
 Begin  
    A1:=A2; { This statement also gives this error. It  
              is due to the strict type checking of Pascal }  
 End.  
 

Error: Type mismatch between &#;arg1&#; and &#;arg2&#;

The types are not equal.
Error: Type identifier expected

The identifier is not a type, or you forgot to supply a type identifier.
Error: Variable identifier expected

This happens when you pass a constant to a routine (such as Inc var or Dec) when it expects a variable. You can only pass variables as arguments to these functions.
Error: Integer expression expected, but got &#;arg1&#;

The compiler expects an expression of type integer, but gets a different type.
Error: Boolean expression expected, but got &#;arg1&#;

The expression must be a boolean type. It should be return True or False.
Error: Ordinal expression expected

The expression must be of ordinal type, i.e., maximum a Longint. This happens, for instance, when you specify a second argument to Inc or Dec that doesn&#;t evaluate to an ordinal value.
Error: pointer type expected, but got &#;arg1&#;

The variable or expression isn&#;t of the type pointer. This happens when you pass a variable that isn&#;t a pointer to New or Dispose.
Error: class type expected, but got &#;arg1&#;

The variable or expression isn&#;t of the type class. This happens typically when
1.
The parent class in a class declaration isn&#;t a class.
2.
An exception handler (On) contains a type identifier that isn&#;t a class.
Error: Can&#;t evaluate constant expression

This error can occur when the bounds of an array you declared do not evaluate to ordinal constants.
Error: Set elements are not compatible

You are trying to perform an operation on two sets, when the set element types are not the same. The base type of a set must be the same when taking the union.
Error: Operation not implemented for sets

several binary operations are not defined for sets. These include: div, mod, **, = and =. The last two may be defined for sets in the future.
Warning: Automatic type conversion from floating type to COMP which is an integer type

An implicit type conversion from a real type to a comp is encountered. Since comp is a 64 bit integer type, this may indicate an error.
Hint: use DIV instead to get an integer result

When hints are on, then an integer division with the &#;/&#; operator will produce this message, because the result will then be of type real.
Error: String types have to match exactly in $V+ mode

When compiling in {$V+} mode, the string you pass as a parameter should be of the exact same type as the declared parameter of the procedure.
Error: succ or pred on enums with assignments not possible

If you declare an enumeration type which has C-like assignments in it, such as in the following:

   Tenum = (a,b,e:=5);  
 

then you cannot use the Succ or Pred functions with this enumeration.

Error: Can&#;t read or write variables of this type

You are trying to read or write a variable from or to a file of type text, which doesn&#;t support that variable&#;s type. Only integer types, reals, pchars and strings can be read from or written to a text file. Booleans can only be written to text files.
Error: Can&#;t use readln or writeln on typed file

readln and writeln are only allowed for text files.
Error: Can&#;t use read or write on untyped file.

read and write are only allowed for text or typed files.
Error: Type conflict between set elements

There is at least one set element which is of the wrong type, i.e. not of the set type.
Warning: lo/hi(dword/qword) returns the upper/lower word/dword

Free Pascal supports an overloaded version of lo/hi for longint/dword/int64/qword which returns the lower/upper word/dword of the argument. Turbo Pascal always uses a 16 bit lo/hi which always returns bits for lo and the bits for hi. If you want the Turbo Pascal behavior you have to type cast the argument to a word or integer.
Error: Integer or real expression expected

The first argument to str must be a real or integer type.
Error: Wrong type &#;arg1&#; in array constructor

You are trying to use a type in an array constructor which is not allowed.
Error: Incompatible type for arg no. arg1: Got &#;arg2&#;, expected &#;arg3&#;

You are trying to pass an invalid type for the specified parameter.
Error: Method (variable) and Procedure (variable) are not compatible

You cannot assign a method to a procedure variable or a procedure to a method pointer.
Error: Illegal constant passed to internal math function

The constant argument passed to a ln or sqrt function is out of the definition range of these functions.
Error: Can&#;t take the address of constant expressions

It is not possible to get the address of a constant expression, because they are not stored in memory. You can try making it a typed constant. This error can also be displayed if you try to pass a property to a var parameter.
Error: Argument cannot be assigned to

Only expressions which can be on the left side of an assignment can be passed as call by reference arguments.

Remark: Properties can be used on the left side of an assignment, nevertheless they cannot be used as arguments.

Error: Can&#;t assign local procedure/function to procedure variable

It&#;s not allowed to assign a local procedure/function to a procedure variable, because the calling convention of a local procedure/function is different. You can only assign local procedure/function to a void pointer.
Error: Can&#;t assign values to an address

It is not allowed to assign a value to an address of a variable, constant, procedure or function. You can try compiling with -So if the identifier is a procedure variable.
Error: Can&#;t assign values to const variable

It&#;s not allowed to assign a value to a variable which is declared as a const. This is normally a parameter declared as const. To allow changing the value, pass the parameter by value, or a parameter by reference (using var).
Error: Array type required

If you are accessing a variable using an index &#;[¡x¿]&#; then the type must be an array. In FPC mode a pointer is also allowed.
Error: interface type expected, but got &#;arg1&#;

The compiler expected to encounter an interface type name, but got something else. The following code would produce this error:

 Type  
   TMyStream = Class(TStream,Integer)  
 

Hint: Mixing signed expressions and longwords gives a 64bit result

If you divide (or calculate the modulus of) a signed expression by a longword (or vice versa), or if you have overflow and/or range checking turned on and use an arithmetic expression (+, -, *, div, mod) in which both signed numbers and longwords appear, then everything has to be evaluated in bit arithmetic which is slower than normal bit arithmetic. You can avoid this by typecasting one operand so it matches the result type of the other one.
Warning: Mixing signed expressions and cardinals here may cause a range check error

If you use a binary operator (and, or, xor) and one of the operands is a longword while the other one is a signed expression, then, if range checking is turned on, you may get a range check error because in such a case both operands are converted to longword before the operation is carried out. You can avoid this by typecasting one operand so it matches the result type of the other one.
Error: Typecast has different size (arg1 -¿ arg2) in assignment

Type casting to a type with a different size is not allowed when the variable is used in an assignment.
Error: enums with assignments cannot be used as array index

When you declared an enumeration type which has C-like assignments, such as in the following:

   Tenum = (a,b,e:=5);  
 

you cannot use it as the index of an array.

Error: Class or Object types &#;arg1&#; and &#;arg2&#; are not related

There is a typecast from one class or object to another while the class/object are not related. This will probably lead to errors.
Warning: Class types &#;arg1&#; and &#;arg2&#; are not related

There is a typecast from one class to another while the classes are not related. This will probably lead to errors.
Error: Class or interface type expected, but got &#;arg1&#;

The compiler expected a class or interface name, but got another type or identifier.
Error: Type &#;arg1&#; is not completely defined

This error occurs when a type is not complete: i.e. a pointer type which points to an undefined type.
Warning: String literal has more characters than short string length

The size of the constant string, which is assigned to a shortstring, is longer than the maximum size of the shortstring ( characters).
Warning: Comparison might be always false due to range of constant and expression

There is a comparison between a constant and an expression where the constant is out of the valid range of values of the expression. Because of type promotion, the statement will always evaluate to false. Explicitly typecast the constant or the expression to the correct range to avoid this warning if you think the code is correct.
Warning: Comparison might be always true due to range of constant and expression

There is a comparison between a constant and an expression where the constant is out of the valid range of values of the expression. Because of type promotion, the statement will always evaluate to true. Explicitly typecast the constant or the expression to the correct range to avoid this warning if you think the code is correct.
Warning: Constructing a class &#;arg1&#; with abstract method &#;arg2&#;

An instance of a class is created which contains non-implemented abstract methods. This will probably lead to a runtime error in the code if that routine is ever called. All abstract methods should be overridden.
Hint: The left operand of the IN operator should be byte sized

The left operand of the in operator is not an ordinal or enumeration which fits within 8 bits. This may lead to range check errors. The in operator currently only supports a left operand which fits within a byte. In the case of enumerations, the size of an element of an enumeration can be controlled with the {$PACKENUM} or {$Zn} switches.
Warning: Type size mismatch, possible loss of data / range check error

There is an assignment to a smaller type than the source type. This means that this may cause a range-check error, or may lead to possible loss of data.
Hint: Type size mismatch, possible loss of data / range check error

There is an assignment to a smaller type than the source type. This means that this may cause a range-check error, or may lead to possible loss of data.
Error: The address of an abstract method cannot be taken

An abstract method has no body, so the address of an abstract method cannot be taken.
Error: Assignments to formal parameters and open arrays are not possible

You are trying to assign a value to a formal (untyped var, const or out) parameter, or to an open array.
Error: Constant Expression expected

The compiler expects an constant expression, but gets a variable expression.
Error: Operation &#;arg1&#; not supported for types &#;arg2&#; and &#;arg3&#;

The operation is not allowed for the supplied types.
Error: Illegal type conversion: &#;arg1&#; to &#;arg2&#;

When doing a type-cast, you must take care that the sizes of the variable and the destination type are the same.
Hint: Conversion between ordinals and pointers is not portable

If you typecast a pointer to a longint (or vice-versa), this code will not compile on a machine using 64 bits addressing.
Warning: Conversion between ordinals and pointers is not portable

If you typecast a pointer to an ordinal type of a different size (or vice-versa), this can cause problems. This is a warning to help in finding the bit specific code where cardinal/longint is used to typecast pointers to ordinals. A solution is to use the ptrint/ptruint types instead.
Error: Can&#;t determine which overloaded function to call

You&#;re calling overloaded functions with a parameter that doesn&#;t correspond to any of the declared function parameter lists. e.g. when you have declared a function with parameters word and longint, and then you call it with a parameter which is of type integer.
Error: Illegal counter variable

The type of a for loop variable must be an ordinal type. Loop variables cannot be reals or strings.
Warning: Converting constant real value to double for C variable argument, add explicit typecast to prevent this.

In C, constant real values are double by default. For this reason, if you pass a constant real value to a variable argument part of a C function, FPC by default converts this constant to double as well. If you want to prevent this from happening, add an explicit typecast around the constant.
Error: Class or COM interface type expected, but got &#;arg1&#;

Some operators, such as the AS operator, are only applicable to classes or COM interfaces.
Error: Constant packed arrays are not yet supported

You cannot declare a (bit)packed array as a typed constant.
Error: Incompatible type for arg no. arg1: Got &#;arg2&#; expected &#;(Bit)Packed Array&#;

The compiler expects a (bit)packed array as the specified parameter.
Error: Incompatible type for arg no. arg1: Got &#;arg2&#; expected &#;(not packed) Array&#;

The compiler expects a regular (i.e., not packed) array as the specified parameter.
Error: Elements of packed arrays cannot be of a type which need to be initialised

Support for packed arrays of types that need initialization (such as ansistrings, or records which contain ansistrings) is not yet implemented.
Error: Constant packed records and objects are not yet supported

You cannot declare a (bit)packed array as a typed constant at this time.
Warning: Arithmetic &#;arg1&#; on untyped pointer is unportable to {$T+}, suggest typecast

Addition/subtraction from an untyped pointer may work differently in {$T+}. Use a typecast to a typed pointer.
Error: Can&#;t take address of a subroutine marked as local

The address of a subroutine marked as local cannot be taken.
Error: Can&#;t export subroutine marked as local from a unit

A subroutine marked as local cannot be exported from a unit.
Error: Type is not automatable: &#;arg1&#;

Only byte, integer, longint, smallint, currency, single, double, ansistring, widestring, tdatetime, variant, olevariant, wordbool and all interfaces are automatable.
Hint: Converting the operands to &#;arg1&#; before doing the add could prevent overflow errors.

Adding two types can cause overflow errors. Since you are converting the result to a larger type, you could prevent such errors by converting the operands to this type before doing the addition.
Hint: Converting the operands to &#;arg1&#; before doing the subtract could prevent overflow errors.

Subtracting two types can cause overflow errors. Since you are converting the result to a larger type, you could prevent such errors by converting the operands to this type before doing the subtraction.
Hint: Converting the operands to &#;arg1&#; before doing the multiply could prevent overflow errors.

Multiplying two types can cause overflow errors. Since you are converting the result to a larger type, you could prevent such errors by converting the operands to this type before doing the multiplication.
Warning: Converting pointers to signed integers may result in wrong comparison results and range errors, use an unsigned type instead.

The virtual address space on bit machines runs from $ to $ffffffff. Many operating systems allow you to allocate memory above $ For example both Windowsand linuxallow pointers in the range $ to $bfffffff. If you convert pointers to signed types, this can cause overflow and range check errors, but also $ ¡ $7fffffff. This can cause random errors in code like &#;if p¿q&#;.
Error: Interface type arg1 has no valid GUID

When applying the as-operator to an interface or class, the desired interface (i.e. the right operand of the as-operator) must have a valid GUID.
Error: Invalid selector name &#;arg1&#;

An Objective-C selector cannot be empty, must be a valid identifier or a single colon, and if it contains at least one colon it must also end in one.
Error: Expected Objective-C method, but got arg1

A selector can only be created for Objective-C methods, not for any other kind of procedure/function/method.
Error: Expected Objective-C method or constant method name

A selector can only be created for Objective-C methods, either by specifying the name using a string constant, or by using an Objective-C method identifier that is visible in the current scope.
Error: No type info available for this type

Type information is not generated for some types, such as enumerations with gaps in their value range (this includes enumerations whose lower bound is different from zero).
Error: Ordinal or string expression expected

The expression must be an ordinal or string type.
Error: String expression expected

The expression must be a string type.
Warning: Converting 0 to NIL

Use NIL rather than 0 when initialising a pointer.
Error: Objective-C protocol type expected, but got &#;arg1&#;

The compiler expected a protocol type name, but found something else.
Error: The type &#;arg1&#; is not supported for interaction with the Objective-C and the blocks runtime.

Objective-C and Blocks make extensive use of run time type information (RTTI). This format is defined by the maintainers of the run time and can therefore not be adapted to all possible Object Pascal types. In particular, types that depend on reference counting by the compiler (such as ansistrings and certain kinds of interfaces) cannot be used as fields of Objective-C classes, cannot be directly passed to Objective-C methods or Blocks, and cannot be encoded using objc_encode.
Error: Class or objcclass type expected, but got &#;arg1&#;

It is only possible to create class reference types of class and objcclass
Error: Objcclass type expected

The compiler expected an objcclass type
Warning: Coerced univ parameter type in procedural variable may cause crash or memory corruption: arg1 to arg2

univ parameters are implicitly compatible with all types of the same size, also in procedural variable definitions. That means that the following code is legal, because single and longint have the same size:

 {$mode macpas}  
 Type  
   TIntProc = procedure (l: univ longint);  
 
   procedure test(s: single);  
     begin  
       writeln(s);  
     end;  
 
   var  
     p: TIntProc;  
   begin  
     p:=test;  
     p(4);  
   end.  
 

This code may however crash on platforms that pass integers in registers and floating point values on the stack, because then the stack will be unbalanced. Note that this warning will not flag all potentially dangerous situations. when test returns.

Error: Type parameters of specializations of generics cannot reference the currently specialized type

Recursive specializations of generics like Type MyType = specialize MyGeneric MyType; are not possible.
Error: Type parameters are not allowed on non-generic class/record/object procedure or function

Type parameters are only allowed for methods of generic classes, records or objects
Error: Generic declaration of &#;arg1&#; differs from previous declaration

Generic declaration does not match the previous declaration
Error: Helper type expected

The compiler expected a class helper type.
Error: Record type expected

The compiler expected a record type.
Error: Derived class helper must extend a subclass of &#;arg1&#; or the class itself

If a class helper inherits from another class helper the extended class must extend either the same class as the parent class helper or a subclass of it
Error: Derived record or type helper must extend &#;arg1&#;

If a record helper inherits from another record helper it must extend the same record that the parent record helper extended.
Error: Invalid assignment, procedures return no value

This error occurs when one tries to assign the result of a procedure or destructor call. A procedure or destructor returns no value so this is not possible.
Warning: Implicit string type conversion from &#;arg1&#; to &#;arg2&#;

An implicit type conversion from an ansi string type to an unicode string type is encountered. To avoid this warning perform an explicit type conversion.
Warning: Implicit string type conversion with potential data loss from &#;arg1&#; to &#;arg2&#;

An implicit type conversion from an unicode string type to an ansi string type is encountered. This conversion can lose data since not all unicode characters may be represented in the codepage of destination string type.
Warning: Explicit string typecast from &#;arg1&#; to &#;arg2&#;

An explicit typecast from an ansi string type to an unicode string type is encountered. This warning is off by default. You can turn it on to see all suspicious string conversions.
Warning: Explicit string typecast with potential data loss from &#;arg1&#; to &#;arg2&#;

An explicit typecast from an unicode string type to an ansi string type is encountered. This conversion can lose data since not all unicode characters may be represented in the codepage of destination string type. This warning is off by default. You can turn it on to see all the places with lossy string conversions.
Warning: Unicode constant cast with potential data loss

Conversion from a WideChar to AnsiChar can lose data since now all unicode characters may be represented in the current system codepage You can nest function definitions only 31 levels deep.
Error: range check error while evaluating constants (arg1 must be between arg2 and arg3)

Warning: range check error while evaluating constants (arg1 must be between arg2 and arg3)

The constants are outside their allowed range.
Error: This type is not supported for the Default() intrinsic

Some types like for example Text and File Of X are not supported by the Default intrinsic.
Error: JVM virtual class methods cannot be static

Virtual class methods cannot be static when targeting the JVM platform, because the self pointer is required for correct dispatching.
Error: Final (class) fields can only be assigned in their class&#; (class) constructor

It is only possible to assign a value to a final (class) field inside a (class) constructor of its owning class.
Error: It is not possible to typecast untyped parameters on managed platforms, simply assign a value to them instead.

On managed platforms, untyped parameters are translated by the compiler into the equivalent of var x: BaseClassType. Non-class-based types passed to such parameters are automatically wrapped (or boxed) in a class, and after the call the potentially modified value is assigned back to the original variable. On the caller side, changing untyped var/out parameters happens by simply assigning values to them (either class-based or primitive ones). On the caller side, they will be extracted and if their type does not match the original variable&#;s, an exception will be raised.
Error: The assignment side of an expression cannot be typecasted to a supertype on managed platforms

Managed platforms guarantee type safety at the bytecode level. This means that the virtual machine must be able to statically determine that no type-unsafe assignments or operations occur. By assigning a parent class type to a variable of a child type by typecasting the assignment side to the parent class type, the type safety would no longer be guaranteed and the generated code would fail verification at run time time.
Warning: The interface method &#;arg1&#; raises the visibility of &#;arg2&#; to public when accessed via an interface instance

Error: The interface method &#;arg1&#; has a higher visibility (public) than &#;arg2&#;

All methods in an interface have always public visibility. That means that if an interface method is implemented using a (strict) protected or private method, this method is actually publicly accessible via the interface. On the JVM target this situation results in an error because the JVM rejects such attempts to circumvent the visibility rules. On other targets this is a warning that is disabled by default because such situations are common practice, but it can be enabled in case you are concerned with keeping your code compilable for the JVM target.
Error: TYPEOF can only be used on object types with VMT

Typeof() intrinsic returns pointer to VMT of its argument. It cannot be used on object types that do not have VMT.
Error: It is not possible to define a default value for a parameter of type &#;arg1&#;

Parameters declared as structured types, such as files, variants, non-dynamic arrays and TP-style objects, cannot have a default value.
Error: Type &#;arg1&#; cannot be extended by a type helper

Types like procedural variables cannot be extended by type helpers
Error: Procedure or function must be far in order to allow taking its address: &#;arg1&#;

In certain i memory models (medium, large and huge), procedures and functions have to be declared &#;far&#; in order to allow their address to be taken.
Warning: Creating an instance of abstract class &#;arg1&#;

The specified class is declared as abstract and thus no instance of this class should be created. This is merely a warning for Delphi compatibility.
Error: Subroutine references cannot be declared as &#;of object&#; or &#;is nested&#;, they can always refer to any kind of subroutine

Subroutine references can refer to any kind of subroutine and hence do not require specialisation for methods or nested subroutines.
Error: Procedure variables in that memory model do not store segment information

Warning: The first value of a set constructur range is greater then the second value, so the range describes an empty set.

If a set is constructed like this: s:=[];], then an empty set is generated. As this is something normally not desired, the compiler warns about it.
Error: C block reference must use CDECL or MWPASCAL calling convention.

When declaring a C block reference ensure that it uses either the cdecl or mwpascal calling convention either by adding the corresponding function directive or by using the {$Calling} compiler directive.

Imagine, you are developing Java software and suddenly you encounter an error? Where could you have possibly gone wrong?

There are many types oferrors that you will encounter while developing Java software, but most are avoidable. Some errors are minor lapses when writing codes but that is very much mendable. If you have an error monitoring tool such as Stackify Retrace, you can write codes with ease.

In this article you will find:

  • 50 of the most common Java software errors
  • Code examples and tutorials to help you work around common coding problems

Read on to learn about the most common issues and their workarounds.


New call-to-action

Compiler Errors

Compiler error messages are created when the Java software code is run through the compiler. It is important to remember that a compiler may throw many error messages for one error. So, fix the first error and recompile. That could solve many problems.

1. “… expected”

This error occurs when something is missing from the code. Often this is created by a missing semicolon or closing parenthesis.

private static double volume(String solidom, double alturam, double areaBasem, double raiom) { double vol; if (sprers.euIgnoreCase("esfera"){ vol=(/3)*sprers.eu*sprers.eu(raiom,3); } else { if (sprers.euIgnoreCase("cilindro") { vol=sprers.eu*sprers.eu(raiom,2)*alturam; } else { vol=(/3)*sprers.eu*sprers.eu(raiom,2)*alturam; } } return vol; }

Often this error message does not pinpoint the exact location of the issue. To find it:

  • Make sure all opening parenthesis have a corresponding closing parenthesis.
  • Look in the line previous to the Java code line indicated. This Java software error doesn’t get noticed by the compiler until further in the code.
  • Sometimes a character such as an opening parenthesis shouldn’t be in the Java code in the first place. So the developer didn’t place a closing parenthesis to balance the parentheses.

Check ut an example ofhow a missed parenthesis can create an error (@StackOverflow).

2. “unclosed string literal”

The “unclosed string literal” error message is created when the string literal ends without quotation marks and the message will appear on the sameline as the error. (@DreamInCode) A literal is a source code of a value.

public abstract class NFLPlayersReference { private static Runningback[] nflplayersreference; private static Quarterback[] players; private static WideReceiver[] nflplayers; public static void main(String args[]){ Runningback r = new Runningback("Thomlinsion"); Quarterback q = new Quarterback("Tom Brady"); WideReceiver w = new WideReceiver("Steve Smith"); NFLPlayersReference[] NFLPlayersReference; Run();// { NFLPlayersReference = new NFLPlayersReference [3]; nflplayersreference[0] = r; players[1] = q; nflplayers[2] = w; for ( int i = 0; i < sprers.eu; i++ ) { sprers.eun("My name is " + " nflplayersreference[i].getName()); nflplayersreference[i].run(); nflplayersreference[i].run(); nflplayersreference[i].run(); sprers.eun("NFL offensive threats have great running abilities!"); } } private static void Run() { sprers.eun("Not yet implemented"); } }

Commonly, this happens when:

  • The string literal does not end with quote marks. This is easy to correct by closing the string literal with the needed quote mark.
  • The string literal extends beyond a line. Long string literals can be broken into multiple literals and concatenated with a plus sign (“+”).
  • Quote marks that are part of the string literal are not escaped with a backslash (“\”).

Read adiscussion of the unclosed string literal Java software error message. (@Quora)

3. “illegal start of an expression”

There are numerous reasons why an “illegal start of an expression” error occurs. It ends up being one of the less-helpful error messages. Some developers say it’s caused by bad code.

Usually, expressions are created to produce a new value or assign a value to a variable. The compiler expects to find an expression and cannot find it because thesyntax does not match expectations. (@StackOverflow) It is in these statements that the error can be found.

} // ADD IT HERE public void newShape(String shape) { switch (shape) { case "Line": Shape line = new Line(startX, startY, endX, endY); sprers.eu(line); break; case "Oval": Shape oval = new Oval(startX, startY, endX, endY); sprers.eu(oval); break; case "Rectangle": Shape rectangle = new Rectangle(startX, startY, endX, endY); sprers.eu(rectangle); break; default: sprers.eun("ERROR. Check logic."); } } } // REMOVE IT FROM HERE }

Browse discussions ofhow to troubleshoot the “illegal start of an expression” error. (@StackOverflow)

4. “cannot find symbol”

This is a very common issue because all identifiers in Java need to be declared before they are used. When the code is being compiled, the compiler does not understand what the identifier means.

"cannot find symbol" Java software error

There are many reasons you might receive the “cannot find symbol” message:

  • The spelling of the identifier when declared may not be the same as when it is used in the code.
  • The variable was never declared.
  • The variable is not being used in the same scope it was declared.
  • The class was not imported.

Read a thoroughdiscussion of the “cannot find symbol” error and several code examples that create the same issue. (@StackOverflow)

5. “public class XXX should be in file”

The “public class XXX should be in file” message occurs when the class XXX and the Java program filenamedo not match. The code will only be compiled when the class and Java file are the same. (@coderanch)

package javaapplication3; public class Robot { int xlocation; int ylocation; String name; static int ccount = 0; public Robot(int xxlocation, int yylocation, String nname) { xlocation = xxlocation; ylocation = yylocation; name = nname; ccount++; } } public class JavaApplication1 { public static void main(String[] args) { robot firstRobot = new Robot(34,51,"yossi"); sprers.eun("numebr of robots is now " + sprers.eu); } }

To fix this issue:

  • Name the class and file the same.
  • Make sure the case of both names is consistent.

See anexample of the “Public class XXX should be in file” error. (@StackOverflow)

6. “incompatible types”

“Incompatible types” is an error in logic that occurs when an assignment statement tries to pair a variable with an expression of types. It often comes when the code tries to place atext string into an integer — or vice versa. This is not a Java syntax error. (@StackOverflow)

sprers.eu error: incompatible types return sprers.eung(); ^ required: int found: String 1 error

There really isn’t an easy fix when the compiler gives an “incompatible types” message:

  • There are functions that can convert types.
  • Developer may need to change what the code is expected to do.

Check out an example ofhow trying to assign a string to an integer created the “incompatible types.”  (@StackOverflow)

7. “invalid method declaration; return type required”

This Java software error message means the return type of a method was not explicitly stated in the method signature.

public class Circle { private double radius; public CircleR(double r) { radius = r; } public diameter() { double d = radius * 2; return d; } }

There are a few ways to trigger the “invalid method declaration; return type required” error:

  • Forgetting to state the type
  • If the method does not return a value then “void” needs to be stated as the type in the method signature.
  • Constructor names do not need to state type. But if there is an error in the constructor name, then the compiler will treat the constructor as a method without a stated type.

Follow an example ofhow constructor naming triggered the “invalid method declaration; return type required” issue. (@StackOverflow)

8. “method <X> in class <Y> cannot be applied to given types”

This Java software error message is one of the more helpful error messages. It explains how the method signature is calling the wrong parameters.

sprers.eu error: method generateNumbers in class RandomNumbers cannot be applied to given types; generateNumbers(); required: int[] found:generateNumbers(); reason: actual and formal argument lists differ in length

The method called is expecting certain arguments defined in the method’s declaration. Check the method declaration and call carefully to make sure they are compatible.

This discussion illustrateshow a Java software error message identifies the incompatibility created by arguments in the method declaration and method call. (@StackOverflow)

9. “missing return statement”

The “missing return statement” message occurs when a method does not have a return statement. Each method that returns a value (a non-void type) must have a statement that literally returns that value so it can be called outside the method.

public String[] OpenFile() throws IOException { Map<String, Double> map = new HashMap(); FileReader fr = new FileReader("sprers.eu"); BufferedReader br = new BufferedReader(fr); try{ while (sprers.eu()){ String str = sprers.eune(); String[] list = sprers.eu(" "); sprers.eun(list); } } catch (IOException e){ sprers.eun("Error - IOException!"); } }

There are a couple of reasons why a compiler throws the “missing return statement” message:

  • A return statement was simply omitted by mistake.
  • The method did not return any value but type void was not declared in the method signature.

Check out an example of how to fix the “missing return statement” Java software error. (@StackOverflow)

“possible loss of precision”

“Possible loss of precision” occurs when more information is assigned to a variable than it can hold. If this happens, pieces will be thrown out. If this is fine, then the code needs to explicitly declare the variable as a new type.

A “possible loss of precision” error commonly occurs when:

  • Trying to assign a real number to a variable with an integer data type.
  • Trying to assign a double to a variable with an integer data type.

This explanation of Primitive Data Types in Java shows how the data is characterized. (@Oracle)

“reached end of file while parsing”

This error message usually occurs in Java when the program is missing the closing curly brace (“}”). Sometimes it can be quickly fixed by placing it at the end of the code.

publicclass mod_MyMod extendsBaseModpublicStringVersion(){return"_02";}publicvoidAddRecipes(CraftingManager recipes){   sprers.euipe(newItemStack(sprers.eud),newObject[]{"#",sprers.euf('#'),sprers.eu});}

The above code results in the following error:

java reached endof file while parsing }

Coding utilities and proper code indenting can make it easier to find these unbalanced braces.

This example shows how missing braces can create the “reached end of file while parsing” error message. (@StackOverflow)

“unreachable statement”

“Unreachable statement” occurs when a statement is written in a place that prevents it from being executed. Usually, this is after a break or return statement.

for(;;){break;// unreachable statement}int i=1;if(i==1)else// dead codeOften simply moving the return statement will fix the error. Read the discussion of how to fix unreachable statement Java software error. (@StackOverflow)

“variable <X> might not have been initialized”

This occurs when a local variable declared within a method has not been initialized. It can occur when a variable without an initial value is part of an if statement.

int x;if(condition){x =5;}sprers.eun(x);// x may not have been initialized

Read this discussion of how to avoid triggering the “variable <X> might not have been initialized” error. (@reddit)

“Operator .. cannot be applied to <X>”

This issue occurs when operators are used for types, not in their definition.

operator< cannot be applied to sprers.eu,sprers.eu

This often happens when the Java code tries to use a type string in a calculation. To fix it, the string needs to be converted to an integer or float.

Read this example of how non-numeric types were causing a Java software error warning that an operator cannot be applied to a type. (@StackOverflow)

“inconvertible types”

The “inconvertible types” error occurs when the Java code tries to perform an illegal conversion.

sprers.eu inconvertible typesfound   : sprers.euist<sprers.eu<?sprers.euace1>>required: sprers.euist<sprers.eu<?>>lessRestrictiveClassList =(ArrayList<Class<?>>) classList;^

For example, booleans cannot be converted to an integer.

Read this discussion about finding ways to convert inconvertible types in Java software. (@StackOverflow)

“missing return value”

You’ll get the “missing return value” message when the return statement includes an incorrect type. For example, the following code:

publicclassSavingsAcc2{privatedouble balance;privatedouble interest;publicSavingsAcc2(){balance =;interest =;}publicSavingsAcc2(double initBalance,double interested){balance = initBalance;interest = interested;}publicSavingsAcc2 deposit(double amount){balance = balance + amount;return;}publicSavingsAcc2 withdraw(double amount){balance = balance - amount;return;}publicSavingsAcc2 addInterest(double interest){balance = balance *(interest /)+ balance;return;}publicdouble getBalance(){return balance;}}Returns the following error:sprers.eu missing returnvaluereturn;^sprers.eu missing returnvaluereturn;^sprers.eu missing returnvaluereturn;^3 errors

Usually, there is a return statement that doesn’t return anything.

Read this discussion about how to avoid the “missing return value” Java software error message. (@coderanch)

“cannot return a value from method whose result type is void”

This Java error occurs when a void method tries to return any value, such as in the following example:

publicstaticvoid move(){sprers.eun("What do you want to do?");Scanner scan =newScanner(sprers.eu);int userMove = sprers.eut();return userMove;}publicstaticvoid usersMove(String playerName,int gesture){int userMove = move();if(userMove ==-1){break;}

Often this is fixed by changing to method signature to match the type in the return statement. In this case, instances of void can be changed to int:

publicstaticint move(){sprers.eun("What do you want to do?");Scanner scan =newScanner(sprers.eu);int userMove = sprers.eut();return userMove;}

Read this discussion about how to fix the “cannot return a value from method whose result type is void” error. (@StackOverflow)

“non-static variable . . . cannot be referenced from a static context”

This error occurs when the compiler tries to access non-static variables from a static method (@javinpaul):

public class StaticTest {private int count=0;   public static void main(String args[]) throws IOException {count++; //compiler error: non-static variable count cannot be referenced from a static context}}

To fix the “non-static variable . . . cannot be referenced from a static context” error, try these two things:

  • Declare the variable as static in the signature.
  • Check on the code as it can create an instance of a non-static object in the static method.

Read this tutorial that explains what is the difference between static and non-static variables. (@sitesbay)

“non-static method . . . cannot be referenced from a static context”

This issue occurs when the Java code tries to call a non-static method in a non-static class. Here is an example:

class Sample{private int age;   public void setAge(int a)   {age=a;}public int getAge()   {return age;}public static void main(String args[])   {       System.out.println(“Age is:”+ getAge());}}

Would return this error:

Exception in thread “main” sprers.eu: Unresolved compilation problem:       Cannot make a static reference to the non–static method getAge() from the type Sample

To call a non-static method from a static method is to declare an instance of the class calling the non-static method.

Read this explanation on what is the difference between non-static methods and static methods.

“(array) <X> not initialized”

You’ll get the “(array) <X> not initialized” message when an array has been declared but not initialized. Arrays are fixed in length so each array needs to be initialized with the desired length.

The following code is acceptable:

AClass[] array = {object1, object2}       As is:       AClass[] array = new AClass[2];…       array[0] = object1;array[1] = object2;But not:       AClass[] array;…       array = {object1, object2};

Read this discussion of how to initialize arrays in Java software. (@StackOverflow)

Runtime Exceptions

“ArrayIndexOutOfBoundsException”

This is a runtime error message that occurs when the code attempts to access an array index that is not within the values. The following code would trigger this exception:

String[] name = {“tom”, “dick”, “harry”};       for(int i = 0; i<=sprers.eu; i++) {       sprers.eu(name[i] +‘\n’);}       Here’s another example (@DukeU):int[] list = new int[5];list[5] = 33;       // illegal index, maximum index is 4

Array indexes start at zero and end at one less than the length of the array. Often it is fixed by using “<” instead of “<=” when defining the limits of the array index.

Check out this example on how an index triggered the “ArrayIndexOutOfBoundsException” Java software error message. (@StackOverflow)

  “StringIndexOutOfBoundsException”

This is an issue that occurs when the code attempts to access a part of the string that is not within the bounds of the string. Usually, this happens when the code tries to create a substring of a string that is not of the same length as the parameter. Here’s an example (@javacodegeeks):

public class StringCharAtExample {public static void main(String[] args) {       String str = “Java Code Geeks!”;System.out.println(“Length: “ + sprers.eu());//The following statement throws an exception, because       //the request index is sprers.eu ch = sprers.eu(50);}}

Like array indexes, string indexes start at zero. When indexing a string, the last character is at one less than the length of the string. The “StringIndexOutOfBoundsException” Java software error message usually means the index is trying to access characters that aren’t there.

Here’s an example that illustrates how the “StringIndexOutOfBoundsException” can occur and be fixed. (@StackOverflow)

“NullPointerException”

A “NullPointerException” will occur when the program tries to use an object reference that does not have a value assigned to it (@geeksforgeeks).

// A Java program to demonstrate that invoking a method// on null causes NullPointerExceptionimport sprers.eu*;class GFG{public static void main (String[] args)   {// Initializing String variable with null valueString ptr = null;// Checking if sprers.eu null or works sprers.eu{// This line of code throws NullPointerException           // because ptr is nullif (sprers.eu(“gfg”))               System.out.print(“Same”);           elseSystem.out.print(“Not Same”);}catch(NullPointerException e)       {           System.out.print(“NullPointerException Caught”);}   }}

The Java program often raises an exception when:

  • A statement references an object with a null value.
  • Trying to access a class that is defined but isn’t assigned a reference.

Here’s a discussion of when developers encounter the “NullPointerException” error and how to handle it. (@StackOverflow)

“NoClassDefFoundError”

The “NoClassDefFoundError” will occur when the interpreter cannot find the file containing a class with the main method. Here’s an example from DZone (@DZone):

If you compile this program:

class A{// some code}public class B{public static void main(String[] args)   {       A a = new A();}}

Two .class files are generated: sprers.eu and sprers.eu Removing the sprers.eu file and running the sprers.eu file, will  get you the “NoClassDefFoundError”:

Exception in thread “main” sprers.eusDefFoundError: A       at sprers.eu(sprers.eu)       Caused by: sprers.euotFoundException: A       at sprers.euass(sprers.eu)       at sprers.euass(sprers.eu)       at sprers.euer$sprers.euass(sprers.eu)       at sprers.euass(sprers.eu)

This can happen if:

  • The file is not in the right directory.
  • The name of the class is not the same as the name of the file (without the file extension). Also, the names are case sensitive.

Read this discussion of why “NoClassDefFoundError” occurs when running Java software. (@StackOverflow)

“NoSuchMethodFoundError”

This error message will occur when the Java software tries to call a method of a class and the method no longer has a definition (@myUND):

Error: Could not find or load main class sprers.eu

Often the “NoSuchMethodFoundError” Java software error occurs when there is a typo in the declaration.

Read this tutorial to learn how to avoid the error message “NoSuchMethodFoundError”. (@javacodegeeks)

“NoSuchProviderException”

“NoSuchProviderException” occurs when a security provider is requested that is not available (@alvinalexander):

sprers.euProviderException

When trying to find why “NoSuchProviderException” occurs, check:

  •         The JRE configuration.
  •         The Java_home is set in the configuration.
  •         The Java environment being used.
  •         The security provider entry.

Read this discussion of what causes “NoSuchProviderException” when you run Java software. (@StackOverflow)

AccessControlException

“AccessControlException” indicates that requested access to system resources such as a file system or network is denied, as in this example from JBossDeveloper (@jbossdeveloper):

ERROR Could not register mbeans sprers.euty.       AccessControlException: WFSM Permission check failed (permission “(“sprers.euermission” “sprers.euContextAdmin#-       [sprers.eu4j2:type=f]” “registerMBean“)” in code source “(vfs:/C:/wildflyFinal/standalone/deployments/sprers.eu       jar )” of “null”)

Read this discussion of a workaround used to get past an “AccessControlException” error. (@github)

“ArrayStoreException”

An “ArrayStoreException” occurs

Relative error =
Percentage error = &#;

The equations above are based on the assumption that true values are known. True values are often unknown, and under these situations, standard deviation is one way to represent the error. Please refer to the Standard Deviation Calculator for further details.