[Bug] Cannot subscribe message send by EventMeshHttpProducer via EventMeshTCPClient

[chenzejun]

Search before asking

• I had searched in the issues and found no similar issues.

Environment

Mac

EventMesh version

master

What happened

I dont know it ia a feature or bug？Is EventMesh transport layer protocol independent？
An exception occured in https://github.com/apache/eventmesh/blob/c3d6548eb389a47e7f3f0eb60cca1b716b7ef7cc/eventmesh-runtime/src/main/java/org/apache/eventmesh/runtime/core/protocol/tcp/client/session/push/SessionPusher.java#L111C1-L112C1
error message：

class org.apache.eventmesh.common.protocol.http.HttpCommand cannot be cast to class org.apache.eventmesh.common.protocol.tcp.Package (org.apache.eventmesh.common.protocol.http.HttpCommand and org.apache.eventmesh.common.protocol.tcp.Package are in unnamed module of loader 'app')

How to reproduce

1. start event mesh
2. start a EventMeshTCPClient and subscribe topic test-topic
3. send a cloud event by EventMeshHttpProducer to topic test-topic

Debug logs

class org.apache.eventmesh.common.protocol.http.HttpCommand cannot be cast to class org.apache.eventmesh.common.protocol.tcp.Package (org.apache.eventmesh.common.protocol.http.HttpCommand and org.apache.eventmesh.common.protocol.tcp.Package are in unnamed module of loader 'app')

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct *

[anusha975]

Hi! I’d like to work on this bug. Could someone clarify the expected behavior?

[xwm1992]

The desired outcome is to send messages using the HTTP protocol and receive messages using the TCP protocol. The example below demonstrates sending messages using an HTTP demo and receiving messages using a TCP demo.

Hi! I’d like to work on this bug. Could someone clarify the expected behavior?

[github-actions]

It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature.

If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue.