nats-io / gnatsd / 3163

90%

master: 91%

Pull #920

travis-ci

Gateways: Fix race for request reply

This addresses the following race:
- client connection creates a subscription on a reply subject
- client connection sends a request
- server sends the subscription to inbound gateway
- server sends the message to outbound gateway (those may be
  different)
- receiving server sends to sub interested in request subject
- app sends reply
- its server then check for interest on the reply's subject

In interestOnly mode, there is a possibility that this server
has not received the interest on the reply subject yet and would
then drop the reply.

This PR detects above scenario and will prefix the reply subject
to identify the origin cluster if it is detected that a matching
subscription was created less than a second ago.
Once the destination has this prefix, the destination cluster
will always send back that message to origin cluster even if
there is no registered interest.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>

174 of 174 new or added lines in 4 files covered. (100.0%)

13342 of 14594 relevant lines covered (91.42%)

99657.81 hits per line