agentscope-ai/agentscope-java

[Bug]:1.0.11 AgentScopeJvmShutdownHook conflict with spring

Open

#1093 opened on Apr 1, 2026

View on GitHub
 (5 comments) (1 reaction) (1 assignee)Java (3,253 stars) (693 forks)user submission
buggood first issue

Description

spring工程的SIGTERM信号响应是由spring的ShutdownHook处理的，agentscope又注册了一个AgentScopeJvmShutdownHook。这两个hook之间是并行的，会造成spring容器没有完全关闭时会正常接受请求，但是agent已经关闭了，调用会报错返回Operation interrupted due to system shutting down, please retry。 按照我的理解，在spring工程中agentscope不需要这种hook，生命周期是由spring统一管理。 之前dubbo也有这种问题，提供了一个ShutdownHook和spring的ShutdownHook并发冲突。

Contributor guide

Tech stack
javaspring
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic JavaSpring framework basicsJVM shutdown hook concept
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Investigate AgentScope's registration of AgentScopeJvmShutdownHook and Spring's default shutdown hook. Understand the conflict: during SIGTERM, both hooks run in parallel, causing Spring context not fully closed while agent is already shut down. Look for similar issues in Dubbo that led to a solution. Consider making AgentScope's hook optional or compatible with Spring's lifecycle. Check if there is a Spring specific configuration to disable the custom hook.