| John,
thanks once more for your investigation.
I wouldn't expect problems with a couple of seconds either, however, the
customer would like to know, what the limits are, and if they could be modified
at all.
If you had a chance to discuss this with AB, we would be happy.
- Thanks & regards, Tom.
|
| > If you had a chance to discuss this with AB, we would be happy.
Remembering to do this slipped my mind, so I apologize for the delay in
responding. I finally called AB and they are looking into it.
I did determine that the problem is happening in DTL_WAIT. I also did
some experimenting and the "hang" continues until the clock time
passes the original clock time. So, if you set the time back an hour,
the DTL_SERVER process will hang until an hour later. If it's only a
few seconds, then the hang will only be a few seconds.
I didn't experiment with this, but I also suspect that if the DTL_WAIT
completes for another reason (such as another request completing), you
won't experience the hang, although there is no way you could guarantee
that you had a request complete for every DTL_WAIT call.
|
| AB called back and confirmed that the DTL_WAIT call uses the absolute
time when timing out the DTL_WAIT call, so if the time is set back
during DTL_WAIT, it will hang until the clock time has proceeded back
to the original time. AB said there is no workaround to this problem.
It's the way that INTERCHANGE is designed to work.
|