ByteBuf LEAK when PoolAcquirePendingLimitException is thrown about reactor-netty HOT 9 OPEN

@violetagg Thanks for the reply. I'll try to update the code as suggested by you.

from reactor-netty.

@Akshay-Sundarraj You should always defer the creation of the buffers. Something like this:

    static Mono<String> execute(HttpClient httpClient, String uri) {
        return Mono.defer(() -> {
            return Mono.defer(() -> {
                return httpClient.request(HttpMethod.POST)
                        .uri(uri)
                        .send((httpClientRequest, nettyOutbound) -> {
                            return nettyOutbound.send(Mono.create(sink -> {
                                ByteBuf buffer = ByteBufAllocator.DEFAULT.directBuffer();
                                buffer.writeBytes("Hello World".getBytes(StandardCharsets.UTF_8));
                                sink.success(buffer);
                            }));
                        }).responseSingle(((response, byteBufMono) -> {
                            return byteBufMono.asString();
                        }));
            }).doFinally(signalType -> {
            });
        });
    }

from reactor-netty.

@violetagg Thanks for the suggestion. The thing is I need to fill the buffer with some binary values based on some binary protocol somewhere else and filling the buffer(serialising some objects) may throw errors. Basically buffer is created and filled in some other part. Is there any way I can handle this?

from reactor-netty.

@Akshay-Sundarraj I cannot help with creating the reactive pipeline as I do not know your project.

from reactor-netty.

@violetagg My question is reactor netty release buffer in some cases and does not release is some other cases. How can I know in what scenarios it doesn't relases?

from reactor-netty.

@Akshay-Sundarraj If we receive the buffer we will definitely release it, however here the HttpClient doesn't start sending at all as it cannot obtain a connection from the pool. That said the buffer consumption is lazy, we will not obtain the buffer as a first step. As a first step we need a connection that will be used for sending the request. Because of that you have to create the buffer only if there is a subscriber that will consume it, while now you create the buffer always regardless whether there is a subscriber or not.

from reactor-netty.