gdplogd sends subscription events after a client sends CLOSE
When a client explicitly calls the
gdp_gcl_close(...) on a
gcl with active subscriptions,
gdplogd still keeps sending new events as if the subscription was still active. The client behavior is correct in that it discards the incoming PDUs when there is no known GCL. To reproduce, run a patched
gdp-reader that explicitly calls
gdp_gcl_close(...) with a non-finished subscription. (patch attached).
See attached log-files from
gdplogd and a subscriber client that receives such events. There are two clients connected to
gdplogd during the given execution: one actively appending and the other with a subscription.
#1 Updated by Eric Allman over 6 years ago
- Status changed from New to In Progress
Are you sure that's the correct patch (
gdp-reader.patch)? It is identical to the one you gave me for Bug #110, and since
gdp-reader terminates immediately after the close it never gets a chance to read additional results. I added a five second delay which seems to be showing at least some problem, but I was wondering if you had anything more clever.