Xlate Error Behavior

This topic has 1 reply, 2 voices, and was last updated 17 years, 5 months ago by Ryan Spires.

Creator

Topic
July 3, 2007 at 4:05 pm #49383
Carter Harrison
Participant
I’m still new to the Cloverleaf engine, so excuse me if this is a silly question. If I have a message that comes into the Cloverleaf and it fails during the xlate stage, I understand that the failed message gets copied into the error database. At this point, does the inbound thread stop allowing messages through until that error is cleared? In other words, is the interface going to stop working if a bad/improperly formatted messages makes its way into the xlate? Thanks in advance.
Creator

Topic

Viewing 0 reply threads

Author

Replies
- July 3, 2007 at 4:34 pm #61732
  Ryan Spires
  Participant
  In general, –unless special coding is in place, the engine will move the “bad message” to the errordb and will continue processing as messages are received inbound… As you can see, this could build up a significant number of errors in the error db if the source system has changed something to modify the message beyond the coding or configurations ability to handle it or coding and/or configuration has been changed within the engine itself which has caused the error. The hope is the error isolated to a single message or type of message that can be identified and resolved.
Author

Replies

Viewing 0 reply threads