Uploaded image for project: 'Realm Core'
  1. Realm Core
  2. RCORE-469

Infinite reconnect in case of DNS resolution failure

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintableJSON

      It looks like the Sync Client goes into an infinite reconnect loop if there is DNS resolution failure. We need to figure out if this is a problem in the Sync Client or in Object Store. Either way, the behaviour is undesirable. As a minimum, there should be exponential backoff applied.

      2020-04-29 15:36:51.641 29277-29319/io.realm.test D/REALM_SYNC: Connection[2]: Connecting to endpoint '75.2.26.70:443' (1/2)
2020-04-29 15:36:51.912 29277-29319/io.realm.test I/REALM_SYNC: Connection[2]: Connected to endpoint '75.2.26.70:443' (from '192.168.232.2:37910')
2020-04-29 15:36:52.054 29277-29319/io.realm.test E/REALM_SYNC: Connection[2]: SSL handshake failed: Connection reset by peer
2020-04-29 15:36:52.054 29277-29319/io.realm.test I/REALM_SYNC: Connection[2]: Connection closed due to error
2020-04-29 15:36:52.054 29277-29319/io.realm.test I/REALM_JAVA: Session Error[wss://realm-dev.mongodb.com/]: CONNECTION_RESET_BY_PEER(realm.basic_system:104): Connection reset by peer
2020-04-29 15:36:52.054 29277-29319/io.realm.test D/REALM_SYNC: Connection[2]: Allowing reconnection in 453 milliseconds
2020-04-29 15:36:52.509 29277-29319/io.realm.test D/REALM_SYNC: Connection[2]: Resolving 'realm-dev.mongodb.com:443'
2020-04-29 15:36:52.510 1614-29405/? E/ResolverController: No valid NAT64 prefix (113, <unspecified>/0)
// This just repeats as fast as possible

            Assignee:
            jonathan.reams@mongodb.com Jonathan Reams
            Reporter:
            christian.melchior@mongodb.com Christian Melchior (Inactive)
            Archiver:
            marc.greenfield@mongodb.com Marc Greenfield

              Created:
              Updated:
              Resolved:
              Archived: