"Pending acquire queue has reached its maximum size.." error in the RSocket server responding to a RSocket cli

admin管理员组

文章数量:1201571

I am trying to understand the next error thrown by a Spring boot application(above all the first 4 lines) that is using RSocket protocol to respond to another application acting as a RSocket client. I understand tecnically the part that says "Pending acquire queue has reached its maximum size of 32; nested exception is " but what I dont understand is seeing this error in the "responder" app of a "request/response" RSocket connection and not in the "requester" part. As you can see this error says "at io.rsocket.core.RSocketResponder.handleFrame(RSocketResponder.java:258) ~[rsocket-core-1.1.3.jar!/:na]**" in the fourth line.

Is this error telling that:

1.when the responder app is trying to get a RSocket connection from the pool to respond to the RSocketClient, there is no one because all of them are already busy?. It this the cause, it makes no sense to me because the pool of connections is in the application that makes the RSocket requests.

2.Or is telling that the responder app cannot process the incoming RSocket request?. If its, it makes not sense to me either because that error is already telling that the Rsocket request has been sent OK to the responder app, right?

2025-01-21 13:02:38.007 ERROR [conac-springboot-app2,9c00ef46a999eb80,edaff5a7a0e3e8d3] 1 --- [or-http-epoll-1] reactor.core.publisher.Operators         : Operator called default onErrorDropped

io.rsocket.exceptions.ApplicationErrorException: Pending acquire queue has reached its maximum size of 32; nested exception is reactorty.internal.shaded.reactor.pool.PoolAcquirePendingLimitException: Pending acquire queue has reached its maximum size of 32
    at io.rsocket.exceptions.Exceptions.from(Exceptions.java:76) ~[rsocket-core-1.1.3.jar!/:na]
    at io.rsocket.core.RSocketResponder.handleFrame(RSocketResponder.java:258) ~[rsocket-core-1.1.3.jar!/:na]**
    at reactor.core.publisher.LambdaSubscriber.onNext(LambdaSubscriber.java:160) ~[reactor-core-3.4.34.jar!/:3.4.34]
    at io.rsocket.core.ClientServerInputMultiplexer$InternalDuplexConnection.onNext(ClientServerInputMultiplexer.java:248) ~[rsocket-core-1.1.3.jar!/:na]
    at io.rsocket.core.ClientServerInputMultiplexer.onNext(ClientServerInputMultiplexer.java:129) ~[rsocket-core-1.1.3.jar!/:na]
    at io.rsocket.core.ClientServerInputMultiplexer.onNext(ClientServerInputMultiplexer.java:48) ~[rsocket-core-1.1.3.jar!/:na]
    at io.rsocket.core.SetupHandlingDuplexConnection.onNext(SetupHandlingDuplexConnection.java:119) ~[rsocket-core-1.1.3.jar!/:na]
    at io.rsocket.core.SetupHandlingDuplexConnection.onNext(SetupHandlingDuplexConnection.java:19) ~[rsocket-core-1.1.3.jar!/:na]
    at com.dynatrace.agent.introspection.reactor3.TracingReactorSubscriber.lambda$onNext$0(TracingReactorSubscriber.java:36) ~[na:na]
    at com.dynatrace.agent.introspection.reactor3.TracingReactorSubscriber.withActivePath(TracingReactorSubscriber.java:62) ~[na:na]
    at com.dynatrace.agent.introspection.reactor3.TracingReactorSubscriber.onNext(TracingReactorSubscriber.java:36) ~[na:na]
    at reactor.core.publisher.FluxPeek$PeekSubscriber.onNext(FluxPeek.java:200) ~[reactor-core-3.4.34.jar!/:3.4.34]
    at com.dynatrace.agent.introspection.reactor3.TracingReactorSubscriber.lambda$onNext$0(TracingReactorSubscriber.java:36) ~[na:na]
    at com.dynatrace.agent.introspection.reactor3.TracingReactorSubscriber.withActivePath(TracingReactorSubscriber.java:62) ~[na:na]
    at com.dynatrace.agent.introspection.reactor3.TracingReactorSubscriber.onNext(TracingReactorSubscriber.java:36) ~[na:na]
    at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:122) ~[reactor-core-3.4.34.jar!/:3.4.34]
    at com.dynatrace.agent.introspection.reactor3.TracingReactorSubscriber.lambda$onNext$0(TracingReactorSubscriber.java:36) ~[na:na]
    at com.dynatrace.agent.introspection.reactor3.TracingReactorSubscriber.withActivePath(TracingReactorSubscriber.java:62) ~[na:na]
    at com.dynatrace.agent.introspection.reactor3.TracingReactorSubscriber.onNext(TracingReactorSubscriber.java:36) ~[na:na]
    at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:122) ~[reactor-core-3.4.34.jar!/:3.4.34]
    at reactorty.channel.FluxReceive.drainReceiver(FluxReceive.java:294) ~[reactor-netty-core-1.0.39.jar!/:1.0.39]
    at reactorty.channel.FluxReceive.onInboundNext(FluxReceive.java:403) ~[reactor-netty-core-1.0.39.jar!/:1.0.39]
    at reactorty.channel.ChannelOperations.onInboundNext(ChannelOperations.java:419) ~[reactor-netty-core-1.0.39.jar!/:1.0.39]
    at reactorty.channel.ChannelOperationsHandler.channelRead(ChannelOperationsHandler.java:114) ~[reactor-netty-core-1.0.39.jar!/:1.0.39]
    at ioty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) ~[netty-transport-4.1.101.Final.jar!/:4.1.101.Final]
    at ioty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) ~[netty-transport-4.1.101.Final.jar!/:4.1.101.Final]
    at ioty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) ~[netty-transport-4.1.101.Final.jar!/:4.1.101.Final]
    at ioty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346) ~[netty-codec-4.1.101.Final.jar!/:4.1.101.Final]
    at ioty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318) ~[netty-codec-4.1.101.Final.jar!/:4.1.101.Final]
    at ioty.channel.AbstractChannelHandlerContext.i

本文标签：