errors not writing to hcidbdump

[Jennifer Johnson]

Had an interesting thing happen here. I am wondering if anyone else has had this occur.

On version 5.2.1

We have an inbound thread that sends messages to two outbound threads. Each route has it’s own tcl and Xlates. It happened one night that there were problems with the tcl on one thread and approximately 200 messages failed. Those messages were written to the error database. The odd thing is that those same messages failed to write to the second thread nor did they write to the error database as having failed in route to the second thread. Any ideas?

Topic

[David Caragay]

Jennifer,

Can you post a sample of the error from the database?  You may have received an error in the routing/translation of the message.  Cloverleaf must successfully process the inbound message through all routing/translations otherwise it will not send any outbound message.   Even though each route has it’s own tcls and xlates, they must all be successful before the different outbound messages are released from the “partial queue” in the translation process.  It is an “all or nothing” concept.  If this was the case, you would only see one message in the error database.

[Bill Bertera]

That’s correct. It saves the messages to the DB at the last state it was successful. In this case that was pre-xlate, it did not succeed make it to the post-xlate of BOTH destinations, so it was written to the EDB as pre-xlate.

[Author]

Replies