Technical article 107583

Connections hang when running Progress 6.x/7.x on SCO OpenServer Release 5.0.

OpenServer 5.0.0

Written · Last revised

Problem

When running Progress Version 6.x or 7.x on SCO OpenServer Release 5.0.0, connection attempts by new users fail and may result in error messages or may hang the user's process.

Cause

There is a known problem in SCO OpenServer Release 5.0.0 with the
system call setsockopt(SSC) when using the SO_REUSEADDR option.
Users running Progress in client/server mode on SCO OpenServer
Release 5.0.0 may be affected by this issue.  The problem occurs
when a non-Progress application binds to a port that is being used
by Progress.  Users already connected to the database will not be
affected, but subsequent connection attempts by new users will fail
and may result in error messages or may hang the user's process.

Note: Users running with only local clients, even if the server was started with -S <servicename>, will not be affected by this SO_REUSEADDR issue.

Solution

Apply the SCO Networking Supplement Release 1.0 for SCO
OpenServer Release 5.  This supplement corrects the behavior
of setsockopt(SSC) with the SO_REUSEADDR option.

From the Xinuos technical article database, record 107583. Reproduced with permission. The original is at www.sco.com/ta/107583, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.