9997766
9997766
As the topic. It seems that there is no example showing how to serialize List . Springboot's default serialization mechanism is jackson, which serializes List ,The resulted json string cannot...
Our project uses Dubbo as a microservice framework. Does Fury currently support Dubbo? If we want to integrate Fury ourselves, how should we make Dubbo to support fury?
Before asking a question, please first consider: - Searching [existing discussions](https://github.com/clickvisual/clickvisual/discussions/) - Searching [existing issues](https://github.com/clickvisual/clickvisual/issues/) - Searching Google ------- 提问之前,建议先在 ClickVisual 社区寻找答案。 - 查看 [存在的 discussions](https://github.com/clickvisual/clickvisual/discussions/) - 查看 [存在的 issues](https://github.com/clickvisual/clickvisual/issues/)...
### 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 Linux ### EventMesh version 1.10.0 ### What happened 我这应用系统集成1.10的sdk,对接eventmesh服务端,用grpc协议接收消息,rocketmq是双机集群,发现有时能收到消息有时收不到, eventmesh 服务端总是报如下错误,...
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues. ### Question 我用docker运行eventmesh 服务端,用rocketmq作为存储,用sdk中的http作为subsciber消费消息时,eventmesh.out的日志报如下错误,我猜测是因为不同的类加载器,导致的EventMeshConsumeConcurrentlyContext 和ConsumeConcurrentlyContext 不认,应该把plugin下的rocket-storage的包,拷贝到apps下能解决问题, 是否能重新打镜像包,放到库上? tenerConcurrently.java:63) - handleMessage fail java.lang.ClassCastException: org.apache.rocketmq.client.consumer.listener.ConsumeConcurrentlyContext...
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues. ### Question 我想搭建一个evenemesh集群,用nginx作为负载均衡,应用系统集成eventmesh-sdk,访问nginx,连到eventmesh。这个是是否能做到,推荐的部署结构是什么? 我希望evenemesh每个节点是无状态的,不管应用系统通过nginx连到哪个节点上,都能流畅的使用http tcp grpc 消费消息。重启应用服务,或者重启eventmesh 不会造成消息丢失。 我试了用rabbitmq作为存储,是不能达到这个效果的,因为rabbitmq-client.properties中,只能配一个队列。如果集群中任何一个eventmesh消费了消息,其他的eventmesh是无法接收该消息了,自然也无法返回给应用系统。比如应用通过nginx连到eventmesh节点1上,节点1消费了消息,节点2的evenmesh就无法收到该消 , 就无法推给连节点2上的应用系统。 上面的效果是否能做到?使用哪种部署结构能搞定?