A2A Connector 1.1 Troubleshooting
To troubleshoot Anypoint Connector for A2A (A2A Connector), become familiar with the information about performing general troubleshooting, addressing specific common errors, and interpreting commonly thrown exception messages.
Error Unmarshalling String JSON Payload into Type io.a2a.spec.Task. Cause: Argument "content" is Null
Likely cause:
-
The payload maps to a task or message schema that expects a non-null text content field, but received
null.
Resolution checklist:
-
Ensure every text part includes
kind: "text"and a non-emptytextvalue. -
Avoid sending
content: nullor equivalent nullable fields in message or task parts. -
Validate outbound JSON in Studio using connector metadata types before sending.
-
Confirm your DataWeave transformation outputs JSON objects, not quoted JSON strings.
Failed to Establish SSE Connection
Likely causes:
-
Request is sent to
message/sendinstead ofmessage/stream. -
The server app doesn’t include an active
a2a:task-stream-listenerflow. -
Reverse proxy or gateway strips
text/event-streamsemantics or closes long-lived HTTP connections.
Resolution checklist:
-
Verify the method is
message/stream. -
Verify the server flow includes
a2a:task-stream-listener. -
Confirm HTTP 200 response with
Content-Type: text/event-stream. -
Check timeout and keepalive settings in intermediary proxies and load balancers.
A2A Server Config Errors Despite Correct Configuration
Likely causes:
-
Invalid
agentPathto listener route binding. -
Card file path not found at runtime.
-
Agent card JSON is malformed or missing capability metadata expected by clients.
Resolution checklist:
-
Use
${app.home}/agent-card.jsonwhen deploying to CloudHub. -
Validate card JSON syntax and required top-level fields.
-
Confirm
<a2a:connection listenerConfig="…" agentPath="…"/>references a validhttp:listener-config. -
Check app startup logs for binding or card parsing errors before runtime requests.