title: Startup of spring-data-gemfire without locator running yet
body: <p>We have a big web application in Java which uses Gemfire and spring-data-gemfire. We run gemfire in a client server configuration.</p>
  
  <p>We have the following problem: During startup, in the bean wiring phase, spring-data-gemfire wants to connect to the locator of gemfire. However, the locator may not be up yet. The application will then throw a <code>com.gemstone.gemfire.cache.NoSubscriptionServersAvailableException: Primary discovery failed</code> exception. </p>
  
  <p>This causes a slow and fragile startup procedure of our services, which is inconvenient, especially during our automated tests.</p>
  
  <p>Is there any good solution to have the client wait and periodically poll until the locator is running?</p>