sprintboot-dubbo-seata 不能rollback

sample启动不了需要做如下修改后才能运行，可以commit但是不能rollback
1.在SeataAutoConfig 添加 application的配置
@bean
public ApplicationConfig applicationConfig() {
ApplicationConfig applicationConfig = new ApplicationConfig();
applicationConfig.setName("dubbo-account-example");
return applicationConfig;
}
2.修改service
@service(version = "1.0.0",
timeout = 3000)
public class AccountDubboServiceImpl implements AccountDubboService
并且nacos-client的版本要用0.9.1 可以正常启动，
可以commit 但是rollback不了
错误日志：
2019-05-30 16:03:27.742 INFO [RetryRollbacking_1]io.seata.core.rpc.ChannelManager.getChannel:357 -Just got exactly the one [id: 0x5e4ec063, L:/127.0.0.1:8091 - R:/127.0.0.1:63093] for order-gts-fescar-example:127.0.0.1:63093
2019-05-30 16:03:27.814 INFO [RetryRollbacking_1]io.seata.server.coordinator.DefaultCore.doGlobalRollback:291 -Failed to rollback branch BR:2012930890/2012930887
2019-05-30 16:03:32.741 INFO [RetryRollbacking_1]io.seata.core.rpc.ChannelManager.getChannel:357 -Just got exactly the one [id: 0x5e4ec063, L:/127.0.0.1:8091 - R:/127.0.0.1:63093] for order-gts-fescar-example:127.0.0.1:63093
2019-05-30 16:03:32.809 INFO [RetryRollbacking_1]io.seata.server.coordinator.DefaultCore.doGlobalRollback:291 -Failed to rollback branch BR:2012930890/2012930887

Start by running the sprintboot-dubbo-seata sample with the reported SeataAutoConfig application configuration, AccountDubboServiceImpl service settings, and nacos-client 0.9.1. Inspect the rollback failures in DefaultCore.doGlobalRollback and ChannelManager.getChannel, then verify that a transaction can both commit and roll back successfully.

Written by the indexing model from the issue text.