The problem was caused by the usage of libraries quarkus-resteasy-reactive and quarkus-rest-client-reactive. After replacing these libraries with non-reactive versions, the endpoint correctly responded, as I wish.