Skip to content

No easy way to configure the underlying HTTP client #2319

Description

@geoand

After spending much time trying to figure out why my GraphQL calls were getting slower and slower, I finally figured out that the Vert.x HTTP Client cache was to blame (this same thing often comes up with the Quarkus REST Client as well).
Given that I knew what setting I had to update, I then proceeded to write:

        var builder =
                (VertxDynamicGraphQLClientBuilder) DynamicGraphQLClientBuilder.newBuilder().url("http://whatever.com");
        this.client =
                (VertxDynamicGraphQLClient) builder.options(new WebClientOptions().setMaxPoolSize(50)).build();

This is not really user friendly :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions