dubbo 3.2.1-beta.1/2 provider端只要升级到该版本， C端就会无法调用了。报netty解码错误

piztneat 于 2022-12-31 发布在其他

关注(0)|答案(6)|浏览(332)

consumer报错截图：

provider报错截图：

consumer端报错详细信息

org.apache.dubbo.rpc.RpcException: Invoke remote method timeout. method: getMetadataInfo, provider: dubbo://192.168.2.104:20881/org.apache.dubbo.metadata.MetadataService?connections=1&corethreads=2&dubbo=2.0.2&group=consumerApp&port=20881&protocol=dubbo&release=3.2.0-beta.1&retries=0&side=provider&threadpool=cached&threads=100&timeout=300&version=1.0.0, cause: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-12-20 12:58:42.308, end time: 2022-12-20 12:58:42.623, client elapsed: 1 ms, server elapsed: 314 ms, timeout: 300 ms, request: Request [id=2, version=2.0.2, twoWay=true, event=false, broken=false, data=null], channel: /192.168.2.104:60271 -> /192.168.2.104:20881
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.waitForResultIfSync(AbstractInvoker.java:286) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.invoke(AbstractInvoker.java:180) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.listener.ListenerInvokerWrapper.invoke(ListenerInvokerWrapper.java:70) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at com.bestpay.drip.event.dubbo.filter.ConsumerContextFilter.invoke(ConsumerContextFilter.java:56) ~[event-1.0.3.jar:?]
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:327) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at com.bestpay.drip.ldc.dubbo.AppExFilterConsumer.invoke(AppExFilterConsumer.java:27) ~[ldc-1.0.5-SNAPSHOT.jar:?]
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CopyOfFilterChainNode.invoke(FilterChainBuilder.java:327) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CallbackRegistrationInvoker.invoke(FilterChainBuilder.java:194) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.proxy.InvocationUtil.invoke(InvocationUtil.java:55) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:75) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.metadata.MetadataServiceDubboProxy3.getMetadataInfo(MetadataServiceDubboProxy3.java) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.metadata.MetadataUtils.getRemoteMetadata(MetadataUtils.java:171) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.AbstractServiceDiscovery.getRemoteMetadata(AbstractServiceDiscovery.java:178) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.event.listener.ServiceInstancesChangedListener.lambda$doOnEvent$2(ServiceInstancesChangedListener.java:158) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at java.util.Optional.orElseGet(Optional.java:267) ~[?:1.8.0_292]
	at org.apache.dubbo.registry.client.event.listener.ServiceInstancesChangedListener.doOnEvent(ServiceInstancesChangedListener.java:158) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.event.listener.ServiceInstancesChangedListener.onEvent(ServiceInstancesChangedListener.java:112) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.ServiceDiscoveryRegistry.subscribeURLs(ServiceDiscoveryRegistry.java:316) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.ServiceDiscoveryRegistry.doSubscribe(ServiceDiscoveryRegistry.java:216) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.ServiceDiscoveryRegistry.subscribe(ServiceDiscoveryRegistry.java:184) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.ListenerRegistryWrapper.subscribe(ListenerRegistryWrapper.java:86) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.integration.DynamicDirectory.subscribe(DynamicDirectory.java:183) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.ServiceDiscoveryRegistryDirectory.subscribe(ServiceDiscoveryRegistryDirectory.java:125) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.integration.RegistryProtocol.doCreateInvoker(RegistryProtocol.java:567) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.integration.InterfaceCompatibleRegistryProtocol.getServiceDiscoveryInvoker(InterfaceCompatibleRegistryProtocol.java:65) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.migration.MigrationInvoker.refreshServiceDiscoveryInvoker(MigrationInvoker.java:436) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.migration.MigrationInvoker.migrateToApplicationFirstInvoker(MigrationInvoker.java:244) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.migration.MigrationRuleHandler.refreshInvoker(MigrationRuleHandler.java:73) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.migration.MigrationRuleHandler.doMigrate(MigrationRuleHandler.java:57) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.client.migration.MigrationRuleListener.onRefer(MigrationRuleListener.java:243) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.integration.RegistryProtocol.interceptInvoker(RegistryProtocol.java:532) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.integration.RegistryProtocol.doRefer(RegistryProtocol.java:502) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.registry.integration.RegistryProtocol.refer(RegistryProtocol.java:484) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.protocol.ProtocolListenerWrapper.refer(ProtocolListenerWrapper.java:74) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.qos.protocol.QosProtocolWrapper.refer(QosProtocolWrapper.java:80) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.cluster.filter.ProtocolFilterWrapper.refer(ProtocolFilterWrapper.java:71) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.protocol.ProtocolSerializationWrapper.refer(ProtocolSerializationWrapper.java:52) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.Protocol$Adaptive.refer(Protocol$Adaptive.java) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.config.ReferenceConfig.createInvokerForRemote(ReferenceConfig.java:608) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.config.ReferenceConfig.createProxy(ReferenceConfig.java:446) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:300) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:232) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at com.xxx.test.dubbo.DubboReferenceConfigManager.findGenericService(DubboReferenceConfigManager.java:120) ~[classes/:?]
	at com.xxx.test.dubbo.DubboMessageCallback.invokeDubbo(DubboMessageCallback.java:102) ~[classes/:?]
	at com.xxx.test.dubbo.DubboMessageCallback.lambda$onMessage$11(DubboMessageCallback.java:71) ~[classes/:?]
	at com.xxx.test.dubbo.DubboMessageCallback.callWithSentinel(DubboMessageCallback.java:189) ~[classes/:?]
	at com.xxx.test.dubbo.DubboMessageCallback.onMessage(DubboMessageCallback.java:78) ~[classes/:?]
	at com.xxx.test.consumer.PopMessageConsumer$DefaultMessageListenerConcurrently.consumeMessage(PopMessageConsumer.java:284) ~[classes/:?]
	at org.apache.rocketmq.client.impl.consumer.ConsumeMessagePopConcurrentlyService$ConsumeRequest.run(ConsumeMessagePopConcurrentlyService.java:424) ~[rocketmq-client-5.0.0.jar:5.0.0]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_292]
	at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266) ~[?:1.8.0_292]
	at java.util.concurrent.FutureTask.run(FutureTask.java) ~[?:1.8.0_292]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_292]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_292]
	at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_292]
Caused by: java.util.concurrent.ExecutionException: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-12-20 12:58:42.308, end time: 2022-12-20 12:58:42.623, client elapsed: 1 ms, server elapsed: 314 ms, timeout: 300 ms, request: Request [id=2, version=2.0.2, twoWay=true, event=false, broken=false, data=null], channel: /192.168.2.104:60271 -> /192.168.2.104:20881
	at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) ~[?:1.8.0_292]
	at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928) ~[?:1.8.0_292]
	at org.apache.dubbo.rpc.AsyncRpcResult.get(AsyncRpcResult.java:195) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.waitForResultIfSync(AbstractInvoker.java:276) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	... 54 more
Caused by: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2022-12-20 12:58:42.308, end time: 2022-12-20 12:58:42.623, client elapsed: 1 ms, server elapsed: 314 ms, timeout: 300 ms, request: Request [id=2, version=2.0.2, twoWay=true, event=false, broken=false, data=null], channel: /192.168.2.104:60271 -> /192.168.2.104:20881
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture.doReceived(DefaultFuture.java:221) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture.received(DefaultFuture.java:185) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture$TimeoutCheckTask.notifyTimeout(DefaultFuture.java:304) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.remoting.exchange.support.DefaultFuture$TimeoutCheckTask.lambda$run$0(DefaultFuture.java:291) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.common.threadpool.ThreadlessExecutor$RunnableWrapper.run(ThreadlessExecutor.java:184) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.common.threadpool.ThreadlessExecutor.waitAndDrain(ThreadlessExecutor.java:103) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.AsyncRpcResult.get(AsyncRpcResult.java:193) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.protocol.AbstractInvoker.waitForResultIfSync(AbstractInvoker.java:276) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	... 54 more
[2022-12-20 12:58:44.020][ERROR][com.xxx.test.consumer.PopMessageConsumer 301][ConsumeMessageThread_1][,][null,,,,null,null,null,,,null,null,null,null,{}]messageCallBack.onMessage error  
org.apache.dubbo.rpc.StatusRpcException: CANCELLED : Canceled by remote peer, errorCode=0
RemoteAddress:192.168.2.104:50052
	at org.apache.dubbo.rpc.TriRpcStatus.asException(TriRpcStatus.java:214) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.protocol.tri.DeadlineFuture.doReceived(DeadlineFuture.java:134) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at org.apache.dubbo.rpc.protocol.tri.DeadlineFuture.lambda$received$0(DeadlineFuture.java:91) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_292]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_292]
	at org.apache.dubbo.common.threadlocal.InternalRunnable.run(InternalRunnable.java:41) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_292]

provider端报错详细信息：

io.netty.handler.codec.DecoderException: java.io.IOException: Decode without read data.
	at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:480) ~[netty-codec-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:407) ~[netty-codec-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:374) ~[netty-codec-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:357) ~[netty-codec-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262) [netty-transport-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248) [netty-transport-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241) [netty-transport-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405) [netty-transport-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262) [netty-transport-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248) [netty-transport-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901) [netty-transport-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.channel.AbstractChannel$AbstractUnsafe$7.run(AbstractChannel.java:813) [netty-transport-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.runTask$$$capture(AbstractEventExecutor.java:174) [netty-common-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java) [netty-common-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute$$$capture(AbstractEventExecutor.java:167) [netty-common-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java) [netty-common-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) [netty-common-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500) [netty-transport-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [netty-common-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [netty-common-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [netty-common-4.1.78.Final.jar:4.1.78.Final]
	at java.lang.Thread.run(Thread.java:748) [na:1.8.0_292]
Caused by: java.io.IOException: Decode without read data.
	at org.apache.dubbo.remoting.transport.netty4.NettyCodecAdapter$InternalDecoder.decode(NettyCodecAdapter.java:92) ~[dubbo-3.2.0-beta.1.jar:3.2.0-beta.1]
	at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:510) ~[netty-codec-4.1.78.Final.jar:4.1.78.Final]
	at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:449) ~[netty-codec-4.1.78.Final.jar:4.1.78.Final]
	... 21 common frames omitted

如图。C端3.0.10或者12或者3.2.1-beta.1/2 都没问题。但是只要P端也从3.0.10或者12 升级到3.2.0beta后拉取元数据时候就报错。

来源：https://github.com/apache/dubbo/issues/11170

6条答案

按热度按时间

@mz0113 Is the triple protocol adopted?

赞(0）回复(0）举报 2022-12-31

@CrazyHZM 是triple协议

赞(0）回复(0）举报 2022-12-31

@EarthChen PTAL

赞(0）回复(0）举报 2022-12-31

plz provide a demo to reproduce it

赞(0）回复(0）举报 2022-12-31

@EarthChen

consumer端：

   //创建dubbo泛化异步引用
    public static synchronized ReferenceConfig<GenericService> createReference(TopicInfoImmutable topicInfoImmutable) {
        ReferenceConfig<GenericService> reference = new ReferenceConfig<>();
        reference.setInterface(topicInfoImmutable.getInterfaceName());
        reference.setGroup(topicInfoImmutable.getGroup());
        reference.setVersion(topicInfoImmutable.getVersion());
        reference.setRetries(1);

        reference.setGeneric(CommonConstants.GENERIC_SERIALIZATION_GSON);
        reference.setAsync(true);
        reference.setCheck(false);
        reference.setFilter("-sentinel.dubbo.consumer.filter");
        //timeout改为在调用时设置
        //reference.setTimeout((int) topicInfoImmutable.getConsumeTimeoutMills());
        return reference;
    }

//执行泛化异步调用 
genericService = createReference（topicInfoImmutable）；
CompletableFuture completableFuture = RpcContext.getContext().asyncCall(
                        () -> genericService.$invoke(info.getMethodName(), info.getArgsType(), args)
                );
                final Object invoke = completableFuture.get();

  //provider端
 
常规方式，使用@DubboService暴露一个接口
@DubboService
public class MyServiceImpl implements MyService{
   Result doXX();
}

然后C,P端就开始刷那个获取元数据失败的报错了。

赞(0）回复(0）举报 2022-12-31

@EarthChen

consumer端：

   //创建dubbo泛化异步引用
    public static synchronized ReferenceConfig<GenericService> createReference(TopicInfoImmutable topicInfoImmutable) {
        ReferenceConfig<GenericService> reference = new ReferenceConfig<>();
        reference.setInterface(topicInfoImmutable.getInterfaceName());
        reference.setGroup(topicInfoImmutable.getGroup());
        reference.setVersion(topicInfoImmutable.getVersion());
        reference.setRetries(1);

        reference.setGeneric(CommonConstants.GENERIC_SERIALIZATION_GSON);
        reference.setAsync(true);
        reference.setCheck(false);
        reference.setFilter("-sentinel.dubbo.consumer.filter");
        //timeout改为在调用时设置
        //reference.setTimeout((int) topicInfoImmutable.getConsumeTimeoutMills());
        return reference;
    }

//执行泛化异步调用 
genericService = createReference（topicInfoImmutable）；
CompletableFuture completableFuture = RpcContext.getContext().asyncCall(
                        () -> genericService.$invoke(info.getMethodName(), info.getArgsType(), args)
                );
                final Object invoke = completableFuture.get();

  //provider端
 
常规方式，使用@DubboService暴露一个接口
@DubboService
public class MyServiceImpl implements MyService{
   Result doXX();
}

然后C,P端就开始刷那个获取元数据失败的报错了。

这个我这边没法复现出来，可以提供一个demo嘛

赞(0）回复(0）举报 2022-12-31

相关问题

热门标签

Java query python Node 开发语言 request Util 数据库 Table 后端算法 Logger Message Element Parser

最新问答

xxl-job 安全组扫描到执行器端口服务存在信息泄露漏洞
回答(1) 发布于 5个月前
xxl-job 不能和nacos兼容？
回答(3) 发布于 5个月前
xxl-job 任务执行完后无法结束，日志一直转圈
回答(3) 发布于 5个月前
xxl-job-admin页面上查看调度日志样式问题
回答(1) 发布于 5个月前
xxl-job 参数512字符限制能否去掉
回答(1) 发布于 5个月前