UPOC protocol in 5.8.4

This topic has 2 replies, 2 voices, and was last updated 12 years, 3 months ago by David Barr.

Creator

Topic
June 21, 2012 at 12:02 am #53156

David Barr
Participant

I’m trying to implement error handling in an outbound UPOC protocol thread in 5.8.4 on Linux. The documentation says the following:

~~Quote:~~

When you use KILL, the message will be sent to the Send Fail TPS. If you do not have any code in Send Fail TPS or it returns a CONTINUE, then the message will be re-queued (State 11) at the top of the queue for re-delivery. If you do not want to retry, then use ERROR inside the Send Fail proc.”

Now I think the “KILL” in this documentation should be “ERROR” because returning a “KILL” will crash the process with an invalid disposition error. However if I return an ERROR disposition my Send Fail TPS is not being called. The message is resent every 10 seconds, and I want the message to go straight to the error database without retrying.
Creator

Topic

Viewing 1 reply thread

Author

Replies
- June 21, 2012 at 9:14 am #76741
  
  Aurelien Garros
  Participant
  
  Hi David,
  
  Our experience is that the UPOC protocol (in Write mode) is not very “stable”. I advice that you call your proc in OB TPS, in this case you could use KILL, ERROR, CONTINUE,… (with this solution, the message will not be send to the Send fail proc)
  
  Aurelien
- June 21, 2012 at 4:12 pm #76742
  
  David Barr
  Participant
  
  Thanks for the reply. I just had another idea that works. I can generate a TCL error in my write TPS proc and that causes the message to go to the error database.
Author

Replies

Viewing 1 reply thread

The forum ‘Cloverleaf’ is closed to new topics and replies.