CachedBodyOutputMessage usage like this will cause memory leak ?

[ihenjoy]

Question

` CachedBodyOutputMessage outputMessage = ResponseUtils.newCachedBodyOutputMessage(exchange);

    return serverRequest.bodyToMono(String.class)
            .switchIfEmpty(Mono.defer(() -> Mono.just("")))
            .flatMap(convert)
            .flatMap(body -> {
                BodyInserter<String, ReactiveHttpOutputMessage> bodyInserter = BodyInserters.fromValue(body);
                return bodyInserter.insert(outputMessage, new BodyInserterContext());
            }).then(Mono.defer(() -> {
                ServerHttpRequestDecorator decorator = new RequestDecorator(exchange, outputMessage);
                return Mono.just(exchange.mutate().request(decorator).build());
            })).onErrorResume(throwable -> ResponseUtils.release(outputMessage, throwable));`

if the filter after this , e.g check some parameter ，call response.write ,the cache body can be release ?

[ihenjoy]

in shenyu plugin filter logic, all CachedBodyOutputMessage‘s body is release errorResume and WebClientPlugin, all plugin should throw exception and up to all filter to execute all errorResume method if the plugin filter should stop excute @yu199195 ,is this rigth?