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 SHARE_CONNECTIONS_KEY = "shareconnections";
    /**
     * By default, a consumer JVM instance and a provider JVM instance share a long TCP connection (except when connections are set),
     * which can set the number of long TCP connections shared to avoid the bottleneck of sharing a single long TCP connection.
     */
    String DEFAULT_SHARE_CONNECTIONS = "1";
    String DECODE_IN_IO_THREAD_KEY = "decode.in.io";
    boolean DEFAULT_DECODE_IN_IO_THREAD = false;
    /**
     * callback inst id
     */
    String CALLBACK_SERVICE_KEY = "callback.service.instid";
    String CALLBACK_SERVICE_PROXY_KEY = "callback.service.proxy";
    String IS_CALLBACK_SERVICE = "is_callback_service";
    /**
     * Invokers in channel's callback
     */
    String CHANNEL_CALLBACK_KEY = "channel.callback.invokers.key";
    /**
     * when this warning rises from invocation, program probably have a bug.
     */
    String LAZY_REQUEST_WITH_WARNING_KEY = "lazyclient_request_with_warning";
    boolean DEFAULT_LAZY_REQUEST_WITH_WARNING = false;
    String OPTIMIZER_KEY = "optimizer";
    String ON_CONNECT_KEY = "onconnect";
    String ON_DISCONNECT_KEY = "ondisconnect";
    String ASYNC_METHOD_INFO = "async-method-info";
}