Feedback:

Discovery process is unable to recover

3 votes
Vote 0 votes Vote Vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service

    You'll receive a confirmation email with a link to create a password (optional).

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    ahinsonahinson shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service

      You'll receive a confirmation email with a link to create a password (optional).

      Signed in as (Sign out)
      Submitting...
      • ahinsonahinson commented  ·   ·  Flag as inappropriate

        .net data provider, ads dlls, v 10.1

        If our application is disconnected from the server, due to service restart or is disconnected using Architect it is unable to rediscover the server unless we create an ads.ini with RETRY_ADS_CONNECTS=1.

        It's obvious to me that the discovery process is using it's cached state since this is a ADS_REMOTE connection.

        Why is there not a default RETRY_ATTEMPTS to be used in conjunction with the cached connection state?

      Knowledge Base and Helpdesk