升级AWS SDK后Kinesis Consumer报NoClassDefFoundError求助

错误原因分析 #

java.lang.NoClassDefFoundError: Could not initialize class com.amazonaws.protocol.json.SdkStructuredCborFactory 本质是AWS SDK组件版本不兼容或依赖缺失：

• 升级aws-java-sdk-core到1.12.398后，amazon-kinesis-client 1.14.9默认依赖的AWS Kinesis SDK版本可能仍停留在1.11.x系列，与新版core存在兼容性冲突
• CBOR序列化相关类加载失败，说明核心协议组件的依赖链出现断裂

分步解决方案 #

1. 统一AWS SDK依赖版本 #

在POM中显式指定所有AWS相关依赖的版本，确保与aws-java-sdk-core 1.12.398完全一致：

<properties>
    <aws.sdk.version>1.12.398</aws.sdk.version>
</properties>

<dependencies>
    <!-- 已升级的核心依赖 -->
    <dependency>
        <groupId>com.amazonaws</groupId>
        <artifactId>amazon-kinesis-client</artifactId>
        <version>1.14.9</version>
    </dependency>
    <dependency>
        <groupId>com.amazonaws</groupId>
        <artifactId>amazon-kinesis-producer</artifactId>
        <version>0.15.2</version>
    </dependency>
    <dependency>
        <groupId>com.amazonaws</groupId>
        <artifactId>aws-java-sdk-core</artifactId>
        <version>${aws.sdk.version}</version>
    </dependency>
    <dependency>
        <groupId>com.amazonaws</groupId>
        <artifactId>jmespath-java</artifactId>
        <version>${aws.sdk.version}</version>
    </dependency>
    <!-- 显式引入匹配版本的Kinesis SDK，解决client依赖的旧版冲突 -->
    <dependency>
        <groupId>com.amazonaws</groupId>
        <artifactId>aws-java-sdk-kinesis</artifactId>
        <version>${aws.sdk.version}</version>
    </dependency>
</dependencies>

2. 排除冲突的旧版依赖 #

执行mvn dependency:tree检查依赖树，若发现1.11.x版本的aws-java-sdk-core或aws-java-sdk-kinesis被间接引入，在amazon-kinesis-client依赖中排除：

<dependency>
    <groupId>com.amazonaws</groupId>
    <artifactId>amazon-kinesis-client</artifactId>
    <version>1.14.9</version>
    <exclusions>
        <exclusion>
            <groupId>com.amazonaws</groupId>
            <artifactId>aws-java-sdk-kinesis</artifactId>
        </exclusion>
        <exclusion>
            <groupId>com.amazonaws</groupId>
            <artifactId>aws-java-sdk-core</artifactId>
        </exclusion>
    </exclusions>
</dependency>

3. 清理并重新构建项目 #

• 执行mvn clean install -U，强制更新依赖并清理旧构建缓存
• 检查运行时classpath，确保只有1.12.398版本的AWS SDK核心组件存在

验证 #

重启Kinesis Consumer服务，观察日志是否不再出现SdkStructuredCborFactory相关错误，Shard初始化和消费流程是否正常。

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