apache / apache/incubator-seata
应用war部署在weblogic,关闭应用后,日志中发现seata仍然有线程在不断请求。
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
具体步骤如下
1,springboot应用打包war后,部署在weblogic上。
2,从weblogic中停止删除应用。

3,查看日志,日志中仍然不断在尝试seata register,有线程并没有关闭。
日志如下:
2021-03-24 10:56:30.447 ERROR 4353 --- [eoutChecker_1_1] i.s.c.r.netty.NettyClientChannelManager : no available service 'default' found, please make sure registry config correct
2021-03-24 10:56:30.594 ERROR 4353 --- [eoutChecker_2_1] i.s.c.r.netty.NettyClientChannelManager : no available service 'default' found, please make sure registry config correct
2021-03-24 10:56:40.447 ERROR 4353 --- [eoutChecker_1_1] i.s.c.r.netty.NettyClientChannelManager : no available service 'default' found, please make sure registry config correct
2021-03-24 10:56:40.595 ERROR 4353 --- [eoutChecker_2_1] i.s.c.r.netty.NettyClientChannelManager : no available service 'default' found, please make sure registry config correct
2021-03-24 10:56:50.448 ERROR 4353 --- [eoutChecker_1_1] i.s.c.r.netty.NettyClientChannelManager : no available service 'default' found, please make sure registry config correct
2021-03-24 10:56:50.594 ERROR 4353 --- [eoutChecker_2_1] i.s.c.r.netty.NettyClientChannelManager : no available service 'default' found, please make sure registry config correct
2021-03-24 10:57:00.449 ERROR 4353 --- [eoutChecker_1_1] i.s.c.r.netty.NettyClientChannelManager : no available service 'default' found, please make sure registry config correct
2021-03-24 10:57:00.595 ERROR 4353 --- [eoutChecker_2_1] i.s.c.r.netty.NettyClientChannelManager : no available service 'default' found, please make sure registry config correct
。。。。。。。。。。。。。。。。。。。。。。
一直在尝试
Contributor guide
Research direction
Reproduce the reported WAR deployment on WebLogic, stop and remove the application, and inspect the Seata registration logs. Focus on the eoutChecker threads and repeated "no available service 'default' found" messages. Done means application shutdown stops the Seata registration attempts and no longer emits these recurring errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100