• New Feature
  • Status: Open
  • 3 Minor
  • Resolution:
  • DSO:L1
  • interfaces
  • Reporter: psebby
  • October 15, 2007
  • 0
  • Watchers: 0
  • December 16, 2011


The property com.tc.l1.max.connect.retries controls how many times an L1 client tries to connect to the L2 *after* the client has its configuration data, but there is currently no way to limit how many times the L1 tries to get its configuration data when using the “production” configuration-model where the client configuration must be loaded from the server – the client keeps retrying for 5 minutes and then exits.

It would be nice if com.tc.l1.max.connect.retries or some other property could be used to control the number of retries when getting configuration data.


Tim Eck 2007-10-15

just my $0.02 on for the implementor – if we’re going to allow the number of config fetch retries to be configurable, might as well make the delay time configurable too so that the total “hang” time in the event of unavailable remote config source can be deterministic. Either that or just make the total time configurable and leave the delay time hard coded.

Fiona OShea 2008-03-06

not possible in pacheco timeframe

Fiona OShea 2008-03-14

We are working on a config changes and this request will be considered as part of those changes