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
}
        return typedClients;
    }
    /**
     * Check if the client list is all available
     *
     * @param referenceCountExchangeClients
     * @return true-available，false-unavailable
     */
    private boolean checkClientCanUse(List<ReferenceCountExchangeClient> referenceCountExchangeClients) {
        if (CollectionUtils.isEmpty(referenceCountExchangeClients)) {
            return false;
        }
        for (ReferenceCountExchangeClient referenceCountExchangeClient : referenceCountExchangeClients) {
            // 
            if (referenceCountExchangeClient == null || referenceCountExchangeClient.getCount() <= 0 || referenceCountExchangeClient.isClosed()) {
                return false;
            }
        }
        return true;
    }
    /**
     * Increase the reference Count if we create new invoker shares same connection, the connection will be closed without any reference.
     *
     * @param referenceCountExchangeClients
     */
    private void batchClientRefIncr(List<ReferenceCountExchangeClient> referenceCountExchangeClients) {
        if (CollectionUtils.isEmpty(referenceCountExchangeClients)) {
            return;
        }