添加spring-cloud-sleuth至类路径时触发‘上下文初始化’错误

Hey there, let's work through this startup issue you're hitting after adding Spring Cloud Sleuth to your project. From what you shared, you're using Spring Boot 1.5.9.RELEASE with Spring Cloud Dalston.SR5, and adding spring-cloud-starter-sleuth triggers a context initialization error when launching your app. Here are the most likely fixes to resolve this:

1. Verify Dependency Management Order #

Spring Cloud's BOM relies on Spring Boot's dependency versions, so the order of your BOM imports matters a lot. Make sure you first import the Spring Boot BOM before the Spring Cloud BOM in your dependencyManagement block. Your corrected build config should look like this:

dependencyManagement {
    imports {
        // First import Spring Boot's BOM to set base compatible versions
        mavenBom "org.springframework.boot:spring-boot-dependencies:${springBootVersion}"
        // Then import Spring Cloud's BOM to align its components with Boot
        mavenBom "org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}"
    }
}

dependencies {
    compile 'org.springframework.cloud:spring-cloud-starter-sleuth'
    // Your other project dependencies...
}

This ensures all Spring Cloud components (including Sleuth) pull in versions that play nicely with your Spring Boot release.

2. Identify & Fix Dependency Conflicts #

If adjusting the BOM order doesn't fix things, you're probably dealing with a hidden dependency conflict. Use your build tool to inspect the dependency tree:

• For Gradle: Run ./gradlew dependencyInsight --dependency org.springframework.cloud:spring-cloud-sleuth-core to check Sleuth's transitive dependencies and spot version mismatches.
• For Maven: Run mvn dependency:tree -Dverbose -Dincludes=org.springframework.cloud to trace conflicting modules.

Once you find a conflicting dependency (like a mismatched Spring Core or logging library), exclude it from the Sleuth starter like this:

compile('org.springframework.cloud:spring-cloud-starter-sleuth') {
    exclude group: 'com.example.conflicting-group', module: 'conflicting-module'
}

3. Simplify Configuration to Isolate the Issue #

Temporarily comment out all Sleuth-related properties in your application.properties or application.yml file. If the app starts successfully without these configs, gradually reintroduce each setting to pinpoint which one is causing the failure. Common culprits include invalid sampling rates or misconfigured trace ID formats.

4. Validate Critical Dependencies Aren't Excluded #

While spring-cloud-starter-sleuth should pull in all necessary transitive dependencies for basic tracing, double-check that you haven't accidentally excluded critical modules (like Spring Context or Spring AOP) elsewhere in your build config.

If you still hit issues, sharing the full stack trace of the context initialization error would help narrow things down further, but the steps above should resolve most common causes with your specific Spring Boot/Spring Cloud version combo.

内容的提问来源于stack exchange，提问作者patb23