Thanks for the feedback Sergio. I agree this aspect of client creation is pretty poor at the moment. Unfortunately the behavior of the express client (at least for this topic) just mirrors the custom mode L1 at the moment. You can tweak the maximum number of connect retries (default it is unlimited) with a tc.property (l1.max.connect.retries). Unfortunately it looks like the failure mode for that is call to System.exit()! There is also another timeout before that if you're using URL based config, I think it will timeout after 5 minutes and that doesn't seem configurable.
I'll get something in JIRA on this topic but can't give you any guidance on when/what will be done at this time. -tim > -----Original Message----- > From: tc-dev-boun...@lists.terracotta.org [mailto:tc-dev- > boun...@lists.terracotta.org] On Behalf Of Sergio Bossa > Sent: Monday, August 23, 2010 2:37 AM > To: tc-dev > Subject: [tc-dev] Timeout handling in TerracottaClient > > Hi guys, > > I noticed there's no timeout handling in TerracottaClient, for > connecting to a Terracotta master by using the express toolkit: that > is, the TerracottaClient waits indefinitely to connect to the master, > even if the master is actually unavailable. > > Are there any plans to introduce timeout (and connection failure) > handling? > I can't use the toolkit without such a feature. > > Thanks, > Cheers, > > Sergio B. > > -- > Sergio Bossa > http://www.linkedin.com/in/sergiob > _______________________________________________ > tc-dev mailing list > tc-dev@lists.terracotta.org > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
