[Bug]:Blocking SendMessage returns stale task state when the agent ends in an interrupted state (INPUT_REQUIRED / AUTH_REQUIRED)
Mantenedores costumam responder em até 1 dia
@VISHNU0906 já está trabalhando nisso.
Desde 9/11/2026.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 45/100
- Tipo de issue
- Bug
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Stack de tecnologia
- java
- Domínio
- backend-api-design
Direção de pesquisa
Start with DefaultRequestHandler.onMessageSend, EventQueue.MainQueue.enqueueItemInternal, and MainEventBusProcessor; the report also gives a self-contained reproducer, InputRequiredStaleRepro.java. Trace when queued events are persisted and when the blocking response reads TaskStore, then reproduce with a delayed save and an INPUT_REQUIRED final event. Done means the blocking response returns the persisted interrupted state even when persistence lags.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
What happened?
[Bug]: Blocking SendMessage returns stale task state when the agent ends in an interrupted state (INPUT_REQUIRED / AUTH_REQUIRED)
Version: org.a2aproject.sdk:*:1.5.0.Final (also present in main as of 2026-11-09)
Environment: macOS / OpenJDK 17.0.20.1, plain Java (no CDI), InMemoryTaskStore wrapped with a
fixed per-save delay, InMemoryQueueManager, MainEventBusProcessor, handler built via
DefaultRequestHandler.builder()
Affects: non-streaming SendMessage with returnImmediately omitted or false, when the last
event is INPUT_REQUIRED or AUTH_REQUIRED
Summary
For a blocking SendMessage, the returned Task is read from TaskStore
(DefaultRequestHandler.onMessageSend, Step 5, taskStore.get(taskId)), but the blocking path only
waits for the consumer future. If the agent's last event has not been persisted by
MainEventBusProcessor when Step 5 runs, the caller receives a stale state (SUBMITTED / WORKING)
even though the task is already INPUT_REQUIRED in the store a moment later.
Terminal states are protected by the awaitingFinalEvent machinery; interrupted states are not,
because TaskState.INPUT_REQUIRED.isFinal() == false and isInterrupted() == true.
This is the interrupted-state analogue of #1247 (fixed for terminal events by #1227).
Why it happens
EventQueue.MainQueue.enqueueItemInternalonly callsChildQueue.expectFinalEvent()when
isFinalEvent(event)is true.isFinalEventacceptsTaskState.isFinal()andA2AError—
INPUT_REQUIRED/AUTH_REQUIREDare excluded.- The blocking path (
DefaultRequestHandler.onMessageSend) closes the caller'sChildQueue
(Step 2) and waits for consumption (Step 3). WithisAwaitingFinalEvent() == false, the
consumer exits as soon as the queue is closed and empty
(ChildQueue.dequeueEventItem). - Step 5 then reads
TaskStore. Events still inMainQueue— acquired on the semaphore in
enqueueItemInternal, released only after persist + distribute — are invisible at this point. MainEventBusProcessoris asynchronous and persists before distributing, so the event is
durable shortly afterwards; the caller already returned.
The consumer's dequeueEventItem(QUEUE_WAIT_MILLISECONDS = 500) gives an accidental grace window:
with a fast store the event lands before the poll times out, which is why this is invisible in
simple examples and only shows up when persistence lags (slow DB, many events, write backlog)
beyond ~500 ms after the agent returns.
Reproduction
Self-contained single file, attached as InputRequiredStaleRepro.java. Only
a2a-java-sdk-server-common + a2a-java-sdk-spec 1.5.0.Final are required.
# pom: the two artifacts above at 1.5.0.Final
mvn -q dependency:build-classpath -Dmdep.outputFile=cp.txt
# interrupted last event, 600ms per persist -> stale
java -DsaveDelay=600 -Dcalls=3 -cp "$(cat cp.txt)" InputRequiredStaleRepro.java blocking
# same store, terminal last event -> correct
java -DsaveDelay=600 -Dcalls=3 -cp "$(cat cp.txt)" InputRequiredStaleRepro.java terminal
Observed:
mode=blocking expected=TASK_STATE_INPUT_REQUIRED saveDelay=600ms artifacts=0 calls=3
call#1 returned=TASK_STATE_SUBMITTED eventual=TASK_STATE_INPUT_REQUIRED STALE
call#2 returned=TASK_STATE_SUBMITTED eventual=TASK_STATE_INPUT_REQUIRED STALE
call#3 returned=TASK_STATE_SUBMITTED eventual=TASK_STATE_INPUT_REQUIRED STALE
=> 0/3 returned the expected state
mode=terminal expected=TASK_STATE_COMPLETED saveDelay=600ms artifacts=0 calls=3
call#1 returned=TASK_STATE_COMPLETED eventual=TASK_STATE_COMPLETED OK
call#2 returned=TASK_STATE_COMPLETED eventual=TASK_STATE_COMPLETED OK
call#3 returned=TASK_STATE_COMPLETED eventual=TASK_STATE_COMPLETED OK
=> 3/3 returned the expected state
A less artificial shape reproduces too — 50 ms per save with 12 artifact events before
requiresInput() (≈650 ms of persistence lag for the tail):
java -DsaveDelay=50 -Dartifacts=12 -Dcalls=3 -cp "$(cat cp.txt)" InputRequiredStaleRepro.java blocking
# => 0/3, e.g. returned=TASK_STATE_WORKING / SUBMITTED, eventual=INPUT_REQUIRED
GetTask immediately afterwards returns INPUT_REQUIRED — the state is not lost, only the blocking
response is wrong.
Suggested fix
The blocking path should guarantee the same invariant the terminal path gets from
awaitingFinalEvent: no event enqueued by the agent may still be in flight in MainQueue when
Step 5 reads TaskStore.
Option A (general): expose the existing in-flight count and wait for it to reach zero before Step 2,
e.g. QueueManager.awaitDrained(taskId, timeout) implemented on MainQueue
(size() == getQueueSize() - semaphore.availablePermits()), signalled from
releaseSemaphore() — which runs in MainEventBusProcessor's finally block, after persist and
distribute. A callback-based wake-up would miss the last event, so the signal has to be on the
release path.
Option B (narrower): extend the awaitingFinalEvent accounting to
state.isFinal() || state.isInterrupted(). This fixes the status-event case, but an artifact tail
(the last event being an artifact) would still race, so Option A is preferable.
Workaround for applications
Wrap the AgentExecutor so that execute() does not return until the task's queue is drained
(poll QueueManager.get(taskId).size() with a bounded timeout), or use
returnImmediately=true plus client-side GetTask polling.
Related
- #1247 — blocking
SendMessagedrops in-flight final events (fixed in 1.5.0 by #1227) - #1249 — builder blocking timeouts aligned with documented defaults
- #990 — API/hook to close streams after INPUT_REQUIRED / AUTH_REQUIRED
Relevant log output
Code of Conduct
- I agree to follow this project's Code of Conduct
- Linguagem predominante
- Java
- Estrelas
- 514
- Forks
- 200
- Merge médio
- 1d 2h
- PRs com merge (30d)
- 53
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de a2aproject/a2a-java
-
Document 1.x is the actively supported stream, and not 0.3.xTalvez já em andamento @Linux2010 assumiu há 2 dias. Aberta
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 62/100
a2aproject/a2a-java#1321 ·
Mantenedores costumam responder em até 1 dia
-
HTTP+JSON CancelTask returns 409 Conflict instead of 400 Bad Request for TaskNotCancelableErrorTalvez livre de novo @ravismash assumiu há 9 dias e não há nenhum pull request aberto. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
a2aproject/a2a-java#1298 · 5 comentários ·
Mantenedores costumam responder em até 1 dia
-
fix: handle blank push notification config id consistently across transportsTalvez já em andamento @prachisinghal-1 assumiu há 24 dias. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
a2aproject/a2a-java#1012 · 2 comentários · 1 responsável ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
a2aproject/a2a-java#464 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Create a sample that demonstrates how to use a shared contextId across multiple tasksTalvez livre de novo @tanish111 assumiu há 390 dias e não há nenhum pull request aberto. Abertasample
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
a2aproject/a2a-java#375 · 5 comentários · 1 responsável ·
Mantenedores costumam responder em até 1 dia
Todas as issues de a2aproject/a2a-java
Issues semelhantes
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
apache/skywalking#14239 ·
Mantenedores costumam responder em até 1 dia
-
account bug exercise lecture modeling programming
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 64/100
Mantenedores costumam responder em até 1 dia
-
Re-executed query with IN condition on an index column returns deleted rows (stale IndexCursor)Talvez já em andamento @dbusche assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
h2database/h2database#4580 ·
Mantenedores costumam responder em até 1 dia
-
vips-drift
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
Stirling-Tools/JPDFium#300 ·
Mantenedores costumam responder em até 1 dia
-
hermes-queue
Dificuldade 1/5 1-3 horas Facilidade para iniciantes 85/100
chrisalunlloyd2-sudo/mindpalace#403 ·
Mantenedores costumam responder em até 1 dia