mp911de on 0.8.x
Add synchronization to Indefini… (compare)
mp911de on master
Polishing Update documentation… (compare)
ttddyy on 0.8.x
Avoid NPE when publisher operat… Update CHANGELOG (compare)
ttddyy on master
Avoid NPE when publisher operat… Update CHANGELOG (cherry picke… (compare)
I played in the context of r2dbc/r2dbc-postgresql#222 with tracking the demand
AtomicLong demand = new AtomicLong(); Mono<Void> receive = connection.inbound().receive() .doOnNext(ignore -> demand.decrementAndGet()) .doOnRequest(demand::addAndGet)
and printed the
demand in the previously available
256and after ~ 258 issued commands that use
createStatement(…).execute().flatMap(result).next(), the demand went to
NettyInboundkept incrementing one-by one.
windowWhileuses its prefetch value of
256by default (https://github.com/reactor/reactor-core/blob/master/reactor-core/src/main/java/reactor/core/publisher/Flux.java#L9414). Also,
FluxWindowPredicateuses some sort of request capping.
0.8.0(from the release) that uses
request(Long.MAX_VALUE), we can either rewrite
delayUntilto something else or handle that case in the subscriber.
256 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
request(n)is intercepted by a subscriber of
WindowPredicateMainrequests a batch from upstream which is
doOnNext(fluxOfMessages): Current demand: 255 doOnNext(fluxOfMessages): Current demand: 256 … after ~ 300 queries doOnNext(fluxOfMessages): Current demand: 552 doOnNext(fluxOfMessages): Current demand: 553 doOnNext(fluxOfMessages): Current demand: 554 doOnNext(fluxOfMessages): Current demand: 555 doOnNext(fluxOfMessages): Current demand: 556 doOnNext(fluxOfMessages): Current demand: 557
sink, we need to register with it that we get its demand/cancellation signal.
Subscriber.onNext(…)) and count that value against the accumulated demand.
Hi everyone, I am experiencing a problem that I encountered now is that the program closed the connection before the response data back.
Error: "Failed to obtain R2DBC Connection; nested exception is io.r2dbc.mssql.client.ReactorNettyClient$MssqlConnectionException", ...... [WARN ] 2020-01-26 18:18:41 [reactor-tcp-epoll-3] FluxReceive.warn : [id: 0x93a0e581, L:/10.244.0.35:48462 ! R:sqlsvrdev01.database.windows.net/ip:1433] An exception has been observed post termination reactor.core.Exceptions$BubblingException: io.r2dbc.mssql.client.ReactorNettyClient$MssqlConnectionClosedException: Connection closed ...... [ERROR] 2020-01-26 18:18:41 [reactor-tcp-epoll-3] ChannelOperationsHandler.error : [id: 0x93a0e581, L:/10.244.0.35:48462 ! R:sqlsvrdev01.database.windows.net/ip:1433] Error was received while reading the incoming data. The connection will be closed. ...... application.yml spring: r2dbc: username: sa password: zynWgTxxxx url: r2dbc:pool:mssql://qlsvrdev01.database.windows.net:1433/dev01 pool: max-idle-time: 15 initial-size: 10 max-size: 100 validation-query: select 1 enabled: true sql-script-encoding: UTF-8 ENV Spring Boot 2.2.2.RELEASE io.r2dbc:r2dbc-mssql:0.8.0.RELEASE io.r2dbc:r2dbc-pool:0.8.0.RELEASE io.r2dbc:r2dbc-spi:0.8.0.RELEASE
The problem as mentioned, can you suggest a solution?
Thank you so much.