使用eureka启动报错

seata-server-0.5.1连接没有任何问题，在Eureka的管理界面也能看到。但是使用springcloud-jpa-seata里面的各个微服务连接的时候就报错了。
2019-05-09 16:58:40.370 ERROR 18244 --- [imeoutChecker_1] i.s.c.r.netty.AbstractRpcRemotingClient : Failed to get available servers: {}not found service provider for : io.seata.discovery.registry.RegistryProvider[Eureka] and classloader : sun.misc.Launcher$AppClassLoader@18b4aac2

Start by reproducing the failure with seata-server-0.5.1 and the services in springcloud-jpa-seata, then inspect the Eureka registration and the RegistryProvider[Eureka] lookup mentioned in the log. Compare the service-discovery configuration with what appears in the Eureka management interface; done means the microservices connect without the “not found service provider” error.

Written by the indexing model from the issue text.