Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Bug]: Unresolved Async Callback Keeps Execution Idly Running

オープン
  • 何か問題がありますか？
#734 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@zhongkechen がすでに取り組んでいます。

2026年9月25日 から。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
aws, java
領域
backend, cloud, testing-qa

調査の方向性

Start by tracing DurableFuture.anyOf(...), waitForCallbackAsync(...), and ExecutionManager.validateRunningThreads() using the two-callback reproduction. Add regression coverage showing that completing one callback does not leave the execution idly running, and that the losing branch cannot block teardown or the execution suspends until it resolves.

索引モデルが issue の本文から書いたものです。

説明

bug pkg:sdk

Expected Behavior

DurableFuture.anyOf(cb1, cb2)with async callbacks should not block the overall execution from completing when the first callback settles, but the second does not. See reproduction example below.

Once one callback succeeds or fails, the other unresolved callback should not keep the Lambda invocation alive or gate the final workflow result. The execution should either complete or suspend itself until all callbacks resolve.

Actual Behavior

After one callback settles, but the other still pending, the Durable Execution is blocked from completing and continuously re-invokes itself until all branches settle.

In the callback repro, cb1 is completed, but the execution keeps re-invoking and timing out while teardown waits for the unresolved cb2 branch:

Waiting for operation to complete before shutting down: d4735e3a265e16eee03f59718b9b5d03019c07d8b6c51f90da3a666eec13ab35

d4735e3a... is the losing branch operation ID. The workflow eventually succeeds only when the losing callback times out. If the losing branch has no timeout, the hang can be unbounded.

This is distinct from #707's original suspension bug.

Steps to Reproduce

  1. Deploy a durable handler that creates two unresolved callbacks and returns DurableFuture.anyOf(cb1, cb2).
  2. Complete only cb1.
  3. Observe that the execution does not complete promptly or suspend. It runs idly until invocation times out, re-invokes after some time, times out again, and repeats.
  4. Check Lambda logs and execution history.

Example repro shape:

var f1 = context.waitForCallbackAsync("cb1", String.class, callbackSubmitter, config);
var f2 = context.waitForCallbackAsync("cb2", String.class, callbackSubmitter, config);
return String.valueOf(DurableFuture.anyOf(f1, f2));
Screenshot

Note the repeated invocation timeouts/failures after the first callback resolves:
Image

Still Need to Confirm
  • Still need to confirm if the issue is unrelated to DurableFuture.anyOf()
  • It could be the case that any pending async callback in the background will prevent the execution from completing or suspending

Java Version

21

Is this a regression?

No

Additional Context

Local triage identified two distinct defects in the anyOf path:

  • Defect A: anyOf skipped the durable wait/deregister path and never suspended. This is tracked by #707 and addressed by PR #730.
  • Defect B: anyOf does not cancel or abandon the losing branch, so teardown waits for it in ExecutionManager.validateRunningThreads().

The fix should add regression coverage that asserts:

  1. A Durable Execution is not kept idly running when there is an unresolved async callback in the background
  2. The losing branch is cancelled, deregistered, or otherwise prevented from blocking teardown. Either that or the Durable Function is suspending until the callback resolves.
主要言語
Java
スター
28
フォーク
13
平均マージ
2日 3時間
マージ済み PR（30日）
44

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

aws/aws-durable-execution-sdk-java のほかの issue

aws/aws-durable-execution-sdk-java の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。