Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 21 APR 1998 05:44:47PM Mina Lee wrote:

I am using AREV 2.12, AREV NLM and Novell InternetWare Client.

I keep getting phantom GFE errors on VERBS. My tech support department saids I am running the latest and greatest InternetWare.

Does anyone have any ideas as to how I can fix this????

Thanks for any help given.


At 22 APR 1998 11:33AM Jeff Warvel wrote:

This is not an answer, but maybe my desire to co-miserate.

(and hopefully some helpful information)

We see the same type of thing (using Arev 2.12, NLM 1.2), but not always as a GFE. Usually we get an error that a certain record

does not exist in the VERBS (typically a frequently used program)

when the record *does* exist. Sometimes a restart will continue

our Arev application without a problem. Other times, we must reboot.

In most cases this happens to our workstations connected via T1

lines. Lines that are occasionally problematic. We typically

see these types of Revelation file access errors surrounding

a network "event" (problem with a T1 line, a bad repeater, etc.).

Most of the other workstations in our network, that are connected

directly to our local ethernet backbone rarely see these types of

errors.

We have not tried "tweaking" any of the timeout parameters for the

NLM or on the client side, but that would be my next step.

So once again, the answer seems to be hardware. For us anyway.

Jeff Warvel

jeff@regen.rg.iupui.edu


At 25 APR 1998 11:10AM Aaron Kaplan wrote:

99.99% of phantom GFEs occur because of some form of caching, and 99.99% of these are workstation based caching. It's not enough to just check for the latest and greatest of something, things need to bet set up propertly. Duh. So, chgeck through the client set up and look for workstation cache issues. Write behind and optimistic locking are prime suspects. Basically, in a heavy transaction based environment (like ARev) all caching should be done on the server, none on the workstation. You don't want to write a record, have it stored in workstation memory and not have it written for 20 or 30 minutes or so.

As for the other .01% of phantom errors, they are from the ghost in the machine.

apk@sprezzatura.com

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/fb20ec21c670becd852565ed00777513.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1