Issue Review: cloudflare/workers-sdk#8221

Summary

Using queue method in Miniflare with https: true produces a TLS disconnection error message in workerd logs, though functionality is unaffected.

Findings

• Created: 2025-02-22
• Updated: 2025-10-30
• Version: miniflare ^3.20250214.0 (workerd 1.20250214.0) -> 4.20260120.0 (workerd 1.20260120.0)
• Component: miniflare / workerd
• Labels: bug, miniflare
• Comments: 0

Key Evidence

• Issue reproduced with miniflare@3.20250214.0 (original reported version):

  workerd/server/server.c++:4032: error: Uncaught exception: kj/compat/tls.c++:416: disconnected: peer disconnected without gracefully ending TLS session
  

• Issue also reproduced with miniflare@3.20250310.2 (workerd 1.20250310.0)
• Issue NOT reproduced with miniflare@3.20250408.0 (workerd 1.20250408.0) and later
• Issue NOT reproduced with miniflare@4.20260120.0 (current version)

Root Cause & Fix

The error was cosmetic log spam (the queue functionality worked correctly). The fix was merged in:

• workerd PR #3816: "Dont log DISCONNECTED application errors" (merged 2025-03-27)
• Fixes workerd issue #3761: Durable Objects + Hibernation log spam

The fix prevents logging of DISCONNECTED application errors that are not actual failures.

Recommendation

Status: CLOSE

Reasoning: The issue has been fixed in workerd 1.20250408.0 and later. The error was cosmetic log spam that did not affect functionality (as the reporter noted). The fix was shipped in miniflare 3.20250408.0 (April 2025) and is included in all current versions.

Action: Close the issue with a comment explaining the fix.

Suggested Comment

This issue has been fixed. The error message was cosmetic log spam that was addressed in workerd PR #3816 (merged March 27, 2025), which prevents logging of DISCONNECTED application errors.

The fix is included in miniflare versions 3.20250408.0 and later (including all miniflare 4.x versions). Upgrading to the latest miniflare version will resolve this issue.

As you noted in the original report, the queue functionality was working correctly - this was just unwanted log output. Closing this issue as resolved.