[large-payload-test] Large Payload Test FAILED - Run 21757940580

[github-actions]

Test Results

Run ID: 21757940580
Status: ❌ FAIL
Timestamp: 2026-02-06T16:36:00Z

Test Results

1. ✅ Read test secret from control file
2. ✅ Establish proxy connection to MCP Gateway
3. ✅ Send MCP initialize request
4. ✅ Send MCP initialized notification
5. ❌ Call tools/call method (backend stuck in initialization)
6. ❌ Receive gateway metadata with payloadPath (never reached)
7. ❌ Translate and access payload file path (never reached)
8. ❌ Read payload file contents (never reached)
9. ❌ Extract and verify secret (never reached)

Details

• Expected Secret: test-secret-5ef4f621-bec0-4156-825a-dce26970e091
• Found Secret: NOT TESTED - couldn't reach tool call stage
• Secret Match: N/A
• Gateway Path: N/A - test failed before payload storage
• Agent Path: N/A
• Payload Size: N/A
• Query ID: N/A

Root Cause

The MCP Gateway's backend server connection management appears to have a bug where:

1. The gateway correctly receives and acknowledges the initialize request (returns capabilities)
2. The gateway correctly receives the notifications/initialized notification (returns 202 Accepted)
3. However, subsequent tools/call requests fail with error: "method \"tools/call\" is invalid during session initialization"
4. Gateway logs show [CACHE] Reusing cached filtered server - the cached backend server instance remains stuck in initialization mode

Evidence

From gateway logs (/tmp/gh-aw/mcp-logs/stderr.log):

server:routed [CACHE] Reusing cached filtered server: backend=filesystem, session=5qXKkF4K...
server:sdk-frontend <<< SDK Response [routed:filesystem] status=202 duration=12.688085ms (empty body)
[...3 seconds later...]
server:routed [CACHE] Reusing cached filtered server: backend=filesystem, session=5qXKkF4K...
server:sdk-frontend <<< SDK Response [routed:filesystem] status=200 duration=5.79887ms (non-JSON or stream)
server:sdk-frontend     Raw response: event: message
data: {"jsonrpc":"2.0","id":101,"error":{"code":0,"message":"method \"tools/call\" is invalid during session initialization"}}

MCP Protocol Sequence Attempted

1. POST /mcp/filesystem - {"method":"initialize","id":100} → ✅ Success (capabilities returned)
2. POST /mcp/filesystem - {"method":"notifications/initialized"} → ✅ 202 Accepted
3. POST /mcp/filesystem - {"method":"tools/call","id":101} → ❌ Error "invalid during session initialization"

Possible Causes

1. Gateway session state bug: The cached backend server instance doesn't properly transition from "initializing" to "ready" state after receiving the initialized notification
2. Stateless HTTP issue: Each HTTP POST might be creating a new backend connection, but the initialization state isn't being shared
3. Notification delivery: The notifications/initialized might not be forwarded to the backend MCP server process
4. Backend MCP SDK bug: The filesystem MCP server's SDK might not handle the initialized notification correctly

Recommendation

This test cannot proceed further without fixing the gateway's session initialization handling. The large payload storage feature cannot be tested if tool calls cannot be made.

---

Run URL: https://github.com/github/gh-aw-mcpg/actions/runs/21757940580

AI generated by Large Payload Tester

[github-actions]

This issue is being closed as outdated. A newer issue has been created: #755

View newer issue

---

This action was performed automatically by the Large Payload Tester workflow.