Re: [I] [Bug] Using http connector in common protocol，data cant be saved in the topic (eventmesh)

["qqeasonchen (via GitHub)" <gi...@apache.org>]

qqeasonchen commented on issue #5232:
URL: https://github.com/apache/eventmesh/issues/5232#issuecomment-5519452643

   **Resolution.** Closing via #5328.
   
   **Root cause.** The stack trace targets the *old* `openconnect` HTTP connector (`CommonProtocol.setHandler` in `org.apache.eventmesh.openconnect.*`), which set a CloudEvent extension attribute named `recordUniqueId` — CloudEvents requires lowercase alphanumeric extension names, so serialization threw `CloudEventRWException: Invalid extensions name` and the event was never persisted. That framework was removed by the uni-architecture redesign; the class no longer exists on `develop`.
   
   **What landed for the failure class.** The rewritten HTTP source connector no longer adds non-conforming extension attributes (events are built with spec-compliant ids/types only), and #5328 hardened the replacement `ConnectorRuntime` so that even a serialization failure on one event is isolated: the bad event is logged + skipped + counted, and the rest of the batch still publishes — instead of the whole worker thread dying as in this report. Regression coverage for that path is in `ConnectorRuntimeTest` (4 new tests).
   
   If you can still reproduce this on `develop` after #5328, please reopen with the payload and the new stack trace. Thanks for the report!
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@eventmesh.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: issues-help@eventmesh.apache.org