| Martin,
This is a known problem. We've experienced it at a number of sites.
I don't believe that the problem has been fixed, but there is a
work-around that we've used that seems to resolve the problem. There
is a logical DECEDI$AFS_QUE_REFRESH which defines how often the search
list is updated in CACHE (my technical explanation may be incorrect,
but this is the "laymens" description!). If you reduce this (I believe
the default is 6 hours) cache will be updated more often and the search
list will hopefully contain all documents. Mark Thompson can certainly
provide you with a better technical explanation and let you know if
this has been fixed or what the outlook is. One note....my
understanding is that lowering this can have a negative impact on
performance, particularly in high-volume shops.
Hope this helps.
Paul Gonyea
Electronic Commerce Practice Group
Dallas TX
|
| This won't be fixed until V3.2.
The problem is caused by a change in the caching algorithm to cope with
high-volume sites. The AFS used to clear its cache and reload every
time it failed to find a requested document. Now it merely does an
incremental update and only flushes the cache when the refresh timer
expires. The problem is that some documents can miss this incremental
update, because they take a longer time to translate.
The problem is very common if you run multiple translators, since the
documents can easily get to AVAILABLE out of sequence.
|