EIS Exceptions (17007 – 17025)
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
Example 13-18 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 must be set.
-
-
17008: INVALID_PROP
-
Cause: Invalid property encountered.
-
-
17009: PROPS_NOT_SET
-
Cause: The specified properties must be set.
-
-
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: No connection factory has been specified.
-
-
17012: INVALID_INTERACTION_SPEC_TYPE
-
Cause: InteractionSspec must be a CciJMSInteractionSpec.
-
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").
-
17013: INVALID_RECORD_TYPE
-
Cause: Record must be a CciJMSRecord.
-
Action: Verify your interaction and ensure that you specify a valid record type. 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: Input must contain a single text element.
-
-
17016: TIMEOUT
-
Cause: A time-out occurred–no message was received.
-
Action: Verify your interaction and the EIS you invoked it on.
-
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: Cannot invoke begin
method on a non-transacted 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 must be an AQInteractionSpec.
-
Action: Verify your interaction and ensure that you specify a valid Oracle AQ interaction specification type. Ensure that the required connector JAR file is on your classpath (see
"EIS Projects").
-
17021: INVALID_AQ_RECORD_TYPE
-
Cause: Record must be an AQRecord.
-
Action: Verify your interaction and ensure that you specify a valid Oracle AQ record type. Ensure that the required connector JAR file is on your classpath (see
"EIS Projects").
-
17022: INVALID_AQ_INPUT
-
Cause: Input must contain a single raw element.
-
-
17023: INVALID_FACTORY_ATTRIBUTES
-
Cause: An exception occurred setting MQQueueConnectionFactory attributes.
-
-
17024: COULD_NOT_DELETE_FILE
-
Cause: Could not delete the specified file.
-
Action: To be determined.
-
17025: GROUPING_ELEMENT_REQUIRED
-
Cause: This mapping requires a foreign key grouping element, as mulitple foreign keys exist.
-