×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
i tried commitment control but it has no effect on sending and receiving
messages to a dataqueue. puting back the message to the queue is no
solution because when an unexpected error occurs commitment-control would
be the safer way.
If you are not using more than one instance of a job listening on the data
queue, it may be reasonable to resend the entry to the queue. If the
error, for example, was the unability to lock another record of another
file, it's reasonable to reuse the entry, and let ROLLBACK to undo
everything else. A retry may succeed some time later. But if you have
several listening jobs to the same queue, you may get into an infinite loop
problem.
In general, if you weren't successful in the first try, it may probably be
safer to discard your entry and let the original sender to resend it,
having had an error message from your program.
I imagine you are dealing with a transaction messaging kind of
application. Just like credit card authorization systems, they simply
report a rejected authorization and have the end user resend the message.
Javier Sanchez
midrange.com
