xiehongfeng100 opened a new issue #761:
URL: https://github.com/apache/incubator-eventmesh/issues/761


   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Environment
   
   Window
   
   ### EventMesh version
   
   master
   
   ### What happened
   
   I publish events to the EventMesh through TCP, but cannot be consumed by the 
HTTP subscriber.
   
   ### How to reproduce
   
   According to the instruction 
[QuickStart](https://eventmesh.apache.org/zh/docs/instructions/eventmesh-runtime-quickstart/):
   1. Start the EventMesh runtime by running 
**org.apache.eventmesh.runtime.boot.EventMeshStartup**.
   2. Push events through TCP by running 
**org.apache.eventmesh.tcp.demo.pub.cloudevents.AsyncPublish**.
   3. Susbcribe topic "TEST-TOPIC-TCP-ASYNC" (same with cloudevents subject 
sent in step 2) through TCP by running 
**org.apache.eventmesh.http.demo.sub.SpringBootDemoApplication**. 
   
![image](https://user-images.githubusercontent.com/3980738/153143340-b33fc56f-16d3-4874-bda5-662a3977f2f4.png)
   
   
   ### Debug logs
   
   Through debugging, I found there is a process publishing events to the HTTP 
subscriber. The problem is in **type conversion failure** (and with no logs). 
Detail is as below:
   
![image](https://user-images.githubusercontent.com/3980738/153141472-004d65dc-d8bd-4543-bc92-c7845a310c5e.png)
   
   
   And I found **HttpCommand** and **Package** has a quite different structure.
   
![image](https://user-images.githubusercontent.com/3980738/153144634-33d289fd-32ad-489b-8596-061f25bc457d.png)
   
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to