Fill out this form to subscribe to news, tips and information about updates.

Read more
Search known errors
From date:
To date:

Follow us
Facebook    Twitter    LinkedIn

G&R » Support » Known Errors  

Known Errors

These are the known errors in our products, logged as reported with versions and platforms affected as well as corrections and work-arounds.

This list is largely historical, since it records all problems that have been reported throughout G&R history. Only the most recently reported problems still exist, unless you are using a very old copy of the product, in which case you should update the product to the most recent version.

E0926: Gproxy, redirect to server could occassionally fail

Product: Gproxy
Platform: Windows
Status: Fixed for R6.2. Fix available for R6.1
Last updated: 2003-09-30 10:35:15

Incoming connections to Gproxy are handled by child threads that
are spawned as necessary, and which do the redirection, leaving
Gproxy to handle further connections. In some cases a timing
race condition could cause the parent Gproxy to believe the
child had taken over the connection before it had done so. This
could cause the child process to terminate without redirecting
the connection to the best available server. This could
theoretically happen for any server (Ggate, Glink Java server,
Gweb server), but has only been observed with HTTP redirects to
GwebS on a low-powered Windows NT server.
(c) Copyright 1982-2018 Gallagher & Robertson AS. Webmaster: webmaster@gar.no

URL: http://www.gar.no/support/errors