The bridge component of the adapter can encounter three types of errors:
In any case, the errors are logged. Depending on the configuration of the bridge, the bridge component of the adapter uses the FRONT ARENA application alert mechanism and can additionally send SMTP mail to indicate that there is a problem.
In cases of recoverable communication problems, the bridge tries to recover. If recovering fails or if a non-recoverable error occurred, the bridge component of the adapter terminated.
Due to the asynchronous communication between the bridge component and other components in the adapter, a bridge termination will not be noticed directly, except that asynchronous service requests will time out. This can also happen for other reasons, however.
If the bridge is configured to send out an SMTP mail in case of an error, this mail can be received, and follow-on processing can be initiated, by an E-Mail adapter.
The adapter distinguishes three types of errors:
In the first case, where the conversion of a FRONT ARENA event notification to a business object fails, the message being processed is forwarded to the adapter's ErrorQueue if a valid queue is specified in the adapter's application configuration property. Otherwise, the event message is simply discarded.
Besides a corrupted event message, a missing entry for the <object>_<verb> entry in the static conversion meta-object of the adapter can be responsible for this failure.
If the error was detected by the data handler, details about the failure can be found in the adapter's log file.
In the case where the communication between the adapter and either the bridge component of the adapter or the server-side connector agent fails, the adapter creates a log file entry. The event message being processed remains in the adapter's InProgressQueue.
In the third case, where a service request cannot be converted to a FRONT ARENA message, a log file entry is created and the erroneous service request is discarded. A negative response is sent to the originating collaboration.
Events that no collaboration has subscribed to are stored in the UnsubscribedQueue, if this queue is defined in the adapter configuration. Otherwise, they are simply discarded.