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 CONFIG_ENABLE_KEY = "highest-priority";
    String CONFIG_NAMESPACE_KEY = "namespace";
    String CHECK_KEY = "check";
    String BACKLOG_KEY = "backlog";
    String HEARTBEAT_EVENT = null;
    String MOCK_HEARTBEAT_EVENT = "H";
    String READONLY_EVENT = "R";
    String REFERENCE_FILTER_KEY = "reference.filter";
    String HEADER_FILTER_KEY = "header.filter";
    String INVOCATION_INTERCEPTOR_KEY = "invocation.interceptor";
    String INVOKER_LISTENER_KEY = "invoker.listener";
    String REGISTRY_PROTOCOL_LISTENER_KEY = "registry.protocol.listener";
    String DUBBO_VERSION_KEY = "dubbo";
    String TAG_KEY = "dubbo.tag";
    /**
     * To decide whether to make connection when the client is created
     */
    String LAZY_CONNECT_KEY = "lazy";
    String STUB_EVENT_KEY = "dubbo.stub.event";
    String REFERENCE_INTERCEPTOR_KEY = "reference.interceptor";
    String SERVICE_FILTER_KEY = "service.filter";
    String EXPORTER_LISTENER_KEY = "exporter.listener";
    /**
     * After simplify the registry, should add some parameter individually for provider.
     *
     * @since 2.7.0
     */
    String EXTRA_KEYS_KEY = "extra-keys";
    String GENERIC_SERIALIZATION_NATIVE_JAVA = "nativejava";
    String GENERIC_SERIALIZATION_GSON = "gson";