有个报错的信息， RST-600500: Failed to parse composite metadata about alibaba-rsocket-broker HOT 10 CLOSED

Composite Metadata 格式不对 RST-600500: Failed to parse composite metadata

能告知一下你是调用example的哪段代码吗？

另外我看到netty 是4.1.45的版本，那么这个rsocket server版本估计比较低啦，能否使用最新的代码重新测试一下。

from alibaba-rsocket-broker.

好的，我拉的是最新的，，borker是docker的，启动没有报错，但是我example request或者response启动时，都会报这个错误

from alibaba-rsocket-broker.

上面的报错是docker logs打印的错误信息。

from alibaba-rsocket-broker.

2020-04-28 14:48:56.223 INFO 17864 --- [ main] c.a.s.b.r.demo.RSocketResponderServer : Starting RSocketResponderServer on 2FMODBETA2IHIJ9 with PID 17864 (E:\share\share\work\idea\demo\rsocket-broker\alibaba-rsocket-broker-master\example\rsocket-responder\target\classes started by Administrator in E:\share\share\work\idea\demo\rsocket-broker\alibaba-rsocket-broker-master\example)
2020-04-28 14:48:56.225 INFO 17864 --- [ main] c.a.s.b.r.demo.RSocketResponderServer : No active profile set, falling back to default profiles: default
2020-04-28 14:48:56.755 INFO 17864 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'rsocket-com.alibaba.spring.boot.rsocket.RSocketProperties' of type [com.alibaba.spring.boot.rsocket.RSocketProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-28 14:48:56.756 INFO 17864 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.spring.boot.rsocket.RSocketAutoConfiguration' of type [com.alibaba.spring.boot.rsocket.RSocketAutoConfiguration$$EnhancerBySpringCGLIB$$5f02e82] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2020-04-28 14:48:59.783 ERROR 17864 --- [actor-tcp-nio-1] c.a.r.loadbalance.LoadBalancedRSocket : RST-400500: Failed to connect URI: tcp://192.168.150.115:9999

io.rsocket.exceptions.InvalidException: RST-600500: Failed to parse composite metadata
at io.rsocket.exceptions.Exceptions.from(Exceptions.java:70) ~[rsocket-core-1.0.0-RC6.jar:na]
at io.rsocket.RSocketRequester.handleFrame(RSocketRequester.java:478) [rsocket-core-1.0.0-RC6.jar:na]
at io.rsocket.RSocketRequester.handleIncomingFrames(RSocketRequester.java:441) [rsocket-core-1.0.0-RC6.jar:na]
at io.rsocket.RSocketRequester$$Lambda$500/1310236203.accept(Unknown Source) [rsocket-core-1.0.0-RC6.jar:na]
at reactor.core.publisher.LambdaSubscriber.onNext(LambdaSubscriber.java:160) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.MonoFlatMapMany$FlatMapManyInner.onNext(MonoFlatMapMany.java:242) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.FluxGroupBy$UnicastGroupedFlux.drainRegular(FluxGroupBy.java:554) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.FluxGroupBy$UnicastGroupedFlux.drain(FluxGroupBy.java:630) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.FluxGroupBy$UnicastGroupedFlux.subscribe(FluxGroupBy.java:696) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.Flux.subscribe(Flux.java:8264) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.MonoFlatMapMany$FlatMapManyMain.onNext(MonoFlatMapMany.java:188) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1712) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.MonoProcessor.onNext(MonoProcessor.java:317) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at io.rsocket.internal.ClientServerInputMultiplexer.lambda$new$1(ClientServerInputMultiplexer.java:116) [rsocket-core-1.0.0-RC6.jar:na]
at io.rsocket.internal.ClientServerInputMultiplexer$$Lambda$482/417929299.accept(Unknown Source) [rsocket-core-1.0.0-RC6.jar:na]
at reactor.core.publisher.LambdaSubscriber.onNext(LambdaSubscriber.java:160) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.FluxGroupBy$GroupByMain.drainLoop(FluxGroupBy.java:380) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.FluxGroupBy$GroupByMain.drain(FluxGroupBy.java:316) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.FluxGroupBy$GroupByMain.onNext(FluxGroupBy.java:201) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:114) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:114) [reactor-core-3.3.4.RELEASE.jar:3.3.4.RELEASE]
at reactor.netty.channel.FluxReceive.drainReceiver(FluxReceive.java:220) [reactor-netty-0.9.6.RELEASE.jar:0.9.6.RELEASE]
at reactor.netty.channel.FluxReceive.onInboundNext(FluxReceive.java:353) [reactor-netty-0.9.6.RELEASE.jar:0.9.6.RELEASE]
at reactor.netty.channel.ChannelOperations.onInboundNext(ChannelOperations.java:352) [reactor-netty-0.9.6.RELEASE.jar:0.9.6.RELEASE]
at reactor.netty.channel.ChannelOperationsHandler.channelRead(ChannelOperationsHandler.java:90) [reactor-netty-0.9.6.RELEASE.jar:0.9.6.RELEASE]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:321) [netty-codec-4.1.48.Final.jar:4.1.48.Final]
at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:295) [netty-codec-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) [netty-transport-4.1.48.Final.jar:4.1.48.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) [netty-common-4.1.48.Final.jar:4.1.48.Final]
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.48.Final.jar:4.1.48.Final]
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.48.Final.jar:4.1.48.Final]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_31]

2020-04-28 14:48:59.924 INFO 17864 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 15 endpoint(s) beneath base path '/actuator'
2020-04-28 14:48:59.986 INFO 17864 --- [ main] c.a.r.listen.impl.RSocketListenerImpl : RST-100001: Succeed to start RSocket Responder on tcp://0.0.0.0:42252
2020-04-28 14:49:00.139 INFO 17864 --- [ main] o.s.b.web.embedded.netty.NettyWebServer : Netty started on port(s): 8180
2020-04-28 14:49:00.141 INFO 17864 --- [ main] c.a.s.b.r.demo.RSocketResponderServer : Started RSocketResponderServer in 5.389 seconds (JVM running for 7.073)
2020-04-28 14:49:00.196 INFO 17864 --- [ main] c.a.s.b.r.r.RSocketServicesPublishHook : RST-301200: Application connected with RSocket Brokers() successfully.
2020-04-28 14:49:00.202 INFO 17864 --- [ main] c.a.s.b.r.r.RSocketServicesPublishHook : RST-301201: Services(com.alibaba.account.AccountService,com.alibaba.user.UserService,com.alibaba.user.RxUserService,com.alibaba.user.Rx3UserService) published on Brokers()!.

from alibaba-rsocket-broker.

这个是我启动RSocketResponderServer 的报错，但是通过localhost:9998查看服务是注册上了的。

2020-04-28 14:48:59.783 ERROR 17864 --- [actor-tcp-nio-1] c.a.r.loadbalance.LoadBalancedRSocket : RST-400500: Failed to connect URI: tcp://192.168.150.115:9999

貌似最终的错误在这个9999连接的问题。

from alibaba-rsocket-broker.

version: "3"
services:
  alibaba-rsocket-broker:
    image: linuxchina/alibaba-rsocket-broker
    ports:
      - "9997:9997"
      - "9998:9998"
      - "9999:9999"

用的这个启动就会有这个问题。

version: "3"
services:
  alibaba-rsocket-broker:
    image: linuxchina/alibaba-rsocket-broker:1.0.0.M1
    ports:
      - "9997:9997"
      - "9998:9998"
      - "9999:9999"

这个版本正常。

from alibaba-rsocket-broker.

这个是我启动RSocketResponderServer 的报错，但是通过localhost:9998查看服务是注册上了的。

2020-04-28 14:48:59.783 ERROR 17864 --- [actor-tcp-nio-1] c.a.r.loadbalance.LoadBalancedRSocket : RST-400500: Failed to connect URI: tcp://192.168.150.115:9999

貌似最终的错误在这个9999连接的问题。

@18758010310 好像连接不上，有什么防火墙的限制吗？ tcp://192.168.150.115:9999 有点奇怪。 如果可能的话，你可以用IntelliJ IDEA启动，然后都用127.0.0.1进行测试一下吗？

Docker镜像的问题，我抓紧更新一个版本。 那个last版本已经不是最新的啦。 三个月前的。建议使用1.0.0.M1，我会抓紧发布M2版本。

from alibaba-rsocket-broker.

version: "3"
services:
  alibaba-rsocket-broker:
    image: linuxchina/alibaba-rsocket-broker
    ports:
      - "9997:9997"
      - "9998:9998"
      - "9999:9999"

用的这个启动就会有这个问题。

version: "3"
services:
  alibaba-rsocket-broker:
    image: linuxchina/alibaba-rsocket-broker:1.0.0.M1
    ports:
      - "9997:9997"
      - "9998:9998"
      - "9999:9999"

这个版本正常。

last版本已经是三个月前的。 我会抓紧更新一个版本。

from alibaba-rsocket-broker.

好的，我等下pull个新的试试，麻烦了哈。

from alibaba-rsocket-broker.

lastest已经调整到1.0.0.M2， 目前没有发现这个问题。如果有这样的问题，麻烦再告知一下。

from alibaba-rsocket-broker.