@@ -14,10 +14,11 @@
 package zipkin.server;
 
 import org.springframework.boot.autoconfigure.SpringBootApplication;
+import org.springframework.boot.autoconfigure.elasticsearch.jest.JestAutoConfiguration;
 import org.springframework.boot.builder.SpringApplicationBuilder;
 import zipkin.server.brave.BootstrapTrace;
 
-@SpringBootApplication
+@SpringBootApplication(exclude = JestAutoConfiguration.class)
 @EnableZipkinServer
 public class ZipkinServer {
 
/**
 * Copyright 2015-2016 The OpenZipkin Authors
 *
 * Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 * in compliance with the License. You may obtain a copy of the License at
 *
 * http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software distributed under the License
 * is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express
 * or implied. See the License for the specific language governing permissions and limitations under
 * the License.
 */
package zipkin.server;

import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.boot.builder.SpringApplicationBuilder;
import zipkin.server.brave.BootstrapTrace;

@SpringBootApplication
@EnableZipkinServer
public class ZipkinServer {

  public static void main(String[] args) {
    new SpringApplicationBuilder(ZipkinServer.class)
        .listeners(new RegisterZipkinHealthIndicators(), BootstrapTrace.INSTANCE::record)
        .properties("spring.config.name=zipkin-server").run(args);
  }
}

I'm sorry about this, but it was the only way I could find to prevent Spring from (eagerly) spinning up an unused JestClient in the application context (with pursuant confusing log messages about its initialization). I suppose we could have found a way to use that configuration, but it doesn't quite meet our needs - there's no hook for adding the signing interceptor, for example. I'd also suggest that makes more sense to have the HttpClient own its own connectivity rather than having it injected, similarly to how the NativeClient handles things.