Message Deletion; Critical Errors; Common Causes Of Errors - IBM BJ0NJML - Service And Asset Management Integration Manual

Common Causes of Errors

Message Deletion

Critical Errors

Common Causes of Errors
Error Type
Sequence error
Data error
124
You can choose to delete a message from a queue. After you delete a message, the
system cannot reprocess it.
When the system deletes the message, the record is deleted from the
MAXINTERRORMSG and MAXINTERROR tables.
The application refreshes the result set and omits the deleted message listing on
the main tab of the Message Reprocessing application.
Critical errors are transaction processing exceptions that the integration
framework error correction process cannot retry. Transaction processing
exceptions can occur when incorrect data, such as a special character, is present in
the XML file. When the integration framework identifies a critical error, ER and IR
sections in the corresponding error file are not present.
To correct the critical error, remove the incorrect data from the error XML. You
can see incorrect data that is associated with a critical error in the main tab of the
Message Reprocessing application.
Errors that occur when a message is processed from an outbound queue are
related to the problematic delivery of a message to the endpoint that is specified
for the external system. Typical problems are disruptions of the communication
link between the system and the external application, or database table space, or
file space issues in the external application. To resolve an outbound error, you
typically do not need to modify the XML message.
Errors that occur when a message is processed from an inbound queue are
typically related to a business rule validation in an object or in the inbound
processing of the enterprise service.
The following table describes the most common message errors that you can
encounter. Perform the suggested actions to correct your message errors.
Correcting an error in the XML file might create a mismatch in data between the
sending and receiving systems.
Description
Caused by sequencing problems between
messages. The system stops message
processing when one record is referencing
another record that is in a pending state.
Occurs because the data or record does not
exist in the system database, and is not part of
the inbound messages in the queue.
Actions
No action required. The system
resolves the error.
Add the missing data to the
system database.
Integration Guide