|
Exception Summary |
| DuplicateMessageRegistrationException |
Exception used by sequence implementation to notify RM runtime infrastructure of
a detected attempt to register a duplicate message number on a given sequence. |
| DuplicateSequenceException |
Inicates that the sequence with given sequence identifier already exists in a given environment. |
| InvalidAcknowledgementException |
An example of when this fault is generated is when a message is Received by
the RM Source containing a SequenceAcknowledgement covering messages that have
not been sent. |
| MessageNumberRolloverException |
If the condition listed below is reached, the RM Destination MUST generate this fault. |
| OutOfOrderMessageException |
Exception used by sequence implementation to reject out of order
message number for a given sequence when InOrder QoS is configured. |
| SequenceClosedException |
This fault is generated by an RM Destination to indicate that the specified Sequence
has been closed. |
| SequenceTerminatedException |
The Endpoint that generates this fault SHOULD make every reasonable effort to
notify the corresponding Endpoint of this decision. |
| UnknownSequenceException |
Inicates that the sequence with given sequence identifier is not available. |