dubbo：3.0.8
dubbo-serialization-kryo：1.0.0
在序列化拓展包中没有排除dubbo-common模块导致项目启动报错
<dependency>
    <groupId>org.apache.dubbo.extensions</groupId>
    <artifactId>dubbo-serialization-kryo</artifactId>
    <exclusions>
        <!-- 这里存在一个引包bug,引入的是3.0.6的dubbo-coomon包导致项目启动不起来 而我当前使用的dubbo版本是3.0.8 -->
        <exclusion>
            <groupId>org.apache.dubbo</groupId>
            <artifactId>dubbo-common</artifactId>
        </exclusion>
    </exclusions>
</dependency>

经过上面的方式排除依赖后，项目才正常启动。

还有一个疑问，我采取dubbo协议时，optimizer指定的类被加载了，但是换成tri协议却不加载请问这是什么原因？
  # 协议名称
  name: tri
  # 序列化配置
  serialization: kryo
  # 序列化对象配置实现
  optimizer: com.grain.pay.service.api.serialization.SerializationOptimizerImpl
String ROUTER_KEY = "router";
    String EXPORT_ASYNC_KEY = "export-async";
    String REFER_ASYNC_KEY = "refer-async";
    String EXPORT_BACKGROUND_KEY = "export-background";
    String REFER_BACKGROUND_KEY = "refer-background";
    String EXPORT_THREAD_NUM_KEY = "export-thread-num";
    String REFER_THREAD_NUM_KEY = "refer-thread-num";
    int DEFAULT_EXPORT_THREAD_NUM = 10;
    int DEFAULT_REFER_THREAD_NUM = 10;
    int DEFAULT_DELAY_NOTIFICATION_TIME = 5000;
    int DEFAULT_DELAY_EXECUTE_TIMES = 10;
    /**
     * Url merge processor key
     */
    String URL_MERGE_PROCESSOR_KEY = "url-merge-processor";
    /**
     * use native image to compile dubbo's identifier
     */
    String NATIVE = "native";
    String DUBBO_MONITOR_ADDRESS = "dubbo.monitor.address";
    String SERVICE_NAME_MAPPING_KEY = "service-name-mapping";
    String SCOPE_MODEL = "scopeModel";
    String SERVICE_MODEL = "serviceModel";
    /**
     * The property name for {@link NetworkInterface#getDisplayName() the name of network interface} that
     * the Dubbo application will be ignored
     *
     * @since 2.7.6
     */
    String DUBBO_NETWORK_IGNORED_INTERFACE = "dubbo.network.interface.ignored";