apache/dubbo

[Bug] Directory of type RegistryDirectory already destroyed for service

Open

#15,798 创建于 2025年11月25日

在 GitHub 查看
 (5 评论) (0 反应) (1 负责人)Java (41,524 star) (26,453 fork)batch import
help wanted

描述

Pre-check

  • I am sure that all the content I provide is in English.

Search before asking

  • I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

openjdk: 1.8 dubbo: 3.2.0

Steps to reproduce this issue

Because Dubbo for Spring Boot starts to destroy itself immediately after receiving the ContextClosedEvent, while the Spring Boot scheduled task (ThreadPoolTaskScheduler) is destroyed later during the DisposableBean.destroy() phase, the destruction order becomes inconsistent.

As a result, Dubbo is destroyed before the scheduled tasks are stopped. If those tasks continue to invoke Dubbo remote services during this period, they will throw the following error:

org.apache.dubbo.rpc.RpcException: Directory of type RegistryDirectory already destroyed for service

What you expected to happen

Support graceful shutdown

Anything else

No response

Are you willing to submit a pull request to fix on your own?

  • Yes I am willing to submit a pull request on my own!

Code of Conduct

贡献者指南

技术栈
javaspring
领域
backend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaDubbo frameworkSpring Boot lifecycleApache Dubbo internals
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
The issue identifies a race condition where Dubbo destroys itself on ContextClosedEvent before scheduled tasks stop, causing RpcException. Investigate the shutdown hook order in dubbo spring boot integration. Look at RegistryDirectory's destroy logic and the Spring context lifecycle to ensure Dubbo shuts down after ThreadPoolTaskScheduler. The assignee's comments may provide additional context.