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 DEFAULT_DIRECTORY = "dubbo";
    String PROTOCOL_KEY = "protocol";
    String DEFAULT_PROTOCOL = "dubbo";
    String DEFAULT_THREAD_NAME = "Dubbo";
    int DEFAULT_CORE_THREADS = 0;
    int DEFAULT_THREADS = 200;
    String EXECUTOR_SERVICE_COMPONENT_KEY = ExecutorService.class.getName();
    String THREADPOOL_KEY = "threadpool";
    String THREAD_NAME_KEY = "threadname";
    String CORE_THREADS_KEY = "corethreads";
    String THREADS_KEY = "threads";
    String QUEUES_KEY = "queues";
    String ALIVE_KEY = "alive";
    String DEFAULT_THREADPOOL = "limited";
    String DEFAULT_CLIENT_THREADPOOL = "cached";
    String IO_THREADS_KEY = "iothreads";
    String KEEP_ALIVE_KEY = "keep.alive";
    int DEFAULT_QUEUES = 0;
    int DEFAULT_ALIVE = 60 * 1000;
    String TIMEOUT_KEY = "timeout";
    int DEFAULT_TIMEOUT = 1000;
    String SESSION_KEY = "session";
    
    
    String TIMEOUT_ATTACHMENT_KEY = "_TO";
    String TIMEOUT_ATTACHMENT_KEY_LOWER = "_to";
    String TIME_COUNTDOWN_KEY = "timeout-countdown";
    String ENABLE_TIMEOUT_COUNTDOWN_KEY = "enable-timeout-countdown";
    String REMOVE_VALUE_PREFIX = "-";
    String PROPERTIES_CHAR_SEPARATOR = "-";