Skip to main content

[Migrated content. Thread originally posted on 15 January 2003]

I have a customer storing Vision 3 files on a Samba server (HP-UX).

They are having a problem where an OPEN I-O of a file (running through a Windows client) hangs occasionally (at least once a day).

It as puzzling for a while trying to determine whether the hang was occurring, but I ran a program on their system through a Citrix connection with the debugger and I happened to catch it. The debugger hits an OPEN I-O statement and it locks up.

In the Samba config file, they have "oplocks = false" set. We've previously found that the default of oplocks = true causes corruption in the files. But I can't see why an OPEN I-O would hang. If I start another instance of the runtime, it can do an OPEN I-O of the same file, even while the other instance is sitting there locked up.

NOTE: AcuServer is not an option. I'm sure it would help, but we use only perhaps 3 Vision files - the rest of the data is stored in a database. So the costs for AcuServer could not be justified.

[Migrated content. Thread originally posted on 15 January 2003]

I have a customer storing Vision 3 files on a Samba server (HP-UX).

They are having a problem where an OPEN I-O of a file (running through a Windows client) hangs occasionally (at least once a day).

It as puzzling for a while trying to determine whether the hang was occurring, but I ran a program on their system through a Citrix connection with the debugger and I happened to catch it. The debugger hits an OPEN I-O statement and it locks up.

In the Samba config file, they have "oplocks = false" set. We've previously found that the default of oplocks = true causes corruption in the files. But I can't see why an OPEN I-O would hang. If I start another instance of the runtime, it can do an OPEN I-O of the same file, even while the other instance is sitting there locked up.

NOTE: AcuServer is not an option. I'm sure it would help, but we use only perhaps 3 Vision files - the rest of the data is stored in a database. So the costs for AcuServer could not be justified.
There are two things I might consider:
1. Upgrading to a newer version of the runtime.
2. Moving to vision 4 format.

I had a similar problem that only appeared when I had two runtime environemnts operating on the same computer at the same time. Read and open statements would variously fail and/or exhibit strange behavior. Updating the runtime fixed the problem.

Merlin
Terms & ConditionsAccessibility statement