Skip Headers

# EIS Exceptions (17007 – 17025), 90000, 91000

Previous

Next

`EISException` is a run-time exception that is raised when invoking EIS interactions. For more information on EIS interactions, see "Enterprise Information System (EIS) Interactions".

Format

    EXCEPTION [TOPLINK – error code]: Exception name
    EXCEPTION DESCRIPTION: Message

JMS Processing Exception

    EXCEPTION [TOPLINK – 17010]: oracle.toplink.eis.EISException
    EXCEPTION DESCRIPTION: Output record contains an unsupported message type.

17007: PROP_NOT_SET
  Cause: The specified property is not set.
  Action: Verify your interaction and ensure that the specified property is set (see "Configuring Custom EIS Interactions for Basic Persistence Operations" or "Creating an EIS Interaction for a Named Query").

17008: INVALID_PROP
  Cause: Invalid property encountered.
  Action: Verify your interaction and remove the specified property (see "Configuring Custom EIS Interactions for Basic Persistence Operations" or "Creating an EIS Interaction for a Named Query").

17009: PROPS_NOT_SET
  Cause: The specified properties are not set.
  Action: Verify your interaction and ensure that the specified properties are set (see "Configuring Custom EIS Interactions for Basic Persistence Operations" or "Creating an EIS Interaction for a Named Query").

17010: OUTPUT_UNSUPPORTED_MSG_TYPE
  Cause: The output record contains an unsupported message type.
  Action: Verify your interaction and ensure that you specify a supported message type. Ensure that the required connector JAR file is on your classpath (see "EIS Projects").

17011: NO_CONN_FACTORY
  Cause: The connection factory is not specified.
  Action: Verify your interaction and ensure that you specify a connection factory (see "Configuring EIS Connection Specification Options at the Project Level" or "Configuring EIS Connection Specification Options at the Session Level").

17012: INVALID_INTERACTION_SPEC_TYPE
  Cause: `InteractionSpec` is not a `CciJMSInteractionSpec`.
  Action: Verify your interaction and ensure that you specify a valid interaction specification type (CciJMSInteractionSpec). Ensure that the required connector JAR file is on your classpath (see "EIS Projects").

17013: INVALID_RECORD_TYPE
  Cause: `Record` is not a `CciJMSRecord`.
  Action: Verify your interaction and ensure that you specify a valid record type (CciJMSRecord). Ensure that the required connector JAR file is on your classpath (see "EIS Projects").

17014: UNKNOWN_INTERACTION_SPEC_TYPE
  Cause: Unknown interaction specification type.
  Action: Verify your interaction and ensure that you specify a valid interaction specification type. Ensure that the required connector JAR file is on your classpath (see "EIS Projects").

17015: INVALID_INPUT
  Cause: Invalid input: input must contain a single text element.
  Action: Verify your interaction and ensure that you specify valid input–a single text element (see "Configuring Custom EIS Interactions for Basic Persistence Operations" or "Creating an EIS Interaction for a Named Query").

17016: TIMEOUT
  Cause: A time-out occurred–no message was received.
  Action: Verify your interaction and the EIS on which you invoked it.

17017: INPUT_UNSUPPORTED_MSG_TYPE
  Cause: Input record contains an unsupported message type.
  Action: Verify your interaction and ensure that you specify a valid message type. Ensure that the required connector JAR file is on your classpath (see "EIS Projects").

17018: INVALID_METHOD_INVOCATION
  Cause: TopLink cannot invoke `begin` method on a nontransacted session.
  Action: To be determined.

17019: TX_SESSION_TEST_ERROR
  Cause: Problem testing for transacted session.
  Action: To be determined.

17020: INVALID_AQ_INTERACTION_SPEC_TYPE
  Cause: `InteractionSpec` is not an `AQInteractionSpec`.
  Action: Verify your interaction and ensure that you specify a valid Oracle AQ interaction specification type (AQInteractionSpec). Ensure that the required connector JAR file is on your classpath (see "EIS Projects").

17021: INVALID_AQ_RECORD_TYPE
  Cause: `Record` is not an `AQRecord`.
  Action: Verify your interaction and ensure that you specify a valid Oracle AQ record type (AQRecord). Ensure that the required connector JAR file is on your classpath (see "EIS Projects").

17022: INVALID_AQ_INPUT
  Cause: Invalid input: input must contain a single raw element.
  Action: Verify your Oracle AQ interaction and ensure that you specify valid input–a single raw element (see "Configuring Custom EIS Interactions for Basic Persistence Operations" or "Creating an EIS Interaction for a Named Query").

17023: INVALID_FACTORY_ATTRIBUTES
  Cause: An exception occurred setting `MQQueueConnectionFactory` attributes.
  Action: Verify your interaction and ensure that you specify an appropriate IBM `MQSeries` connection factory (see "Configuring EIS Connection Specification Options at the Project Level" or "Configuring EIS Connection Specification Options at the Session Level").

17024: COULD_NOT_DELETE_FILE
  Cause: TopLink cannot delete the specified file.
  Action: To be determined.

17025: GROUPING_ELEMENT_REQUIRED
  Cause: No grouping element is specified: this mapping requires a foreign key grouping element, as mulitple foreign keys exist.
  Action: Verify your EIS mappings (see Understanding EIS Mappings.

90000: RESOURCE_EXCEPTION
  Cause: Unknown resource.
  Action: See the generated exception for the root cause.

91000: EIS_EXCEPTION
  Cause: General EIS-related failure.
  Action: See the generated exception for the root cause.