Skip to content
This repository was archived by the owner on Dec 19, 2023. It is now read-only.

Query returning the result of previously timed out query #940

Open
@paulohenriqu

Description

@paulohenriqu

Describe the bug
When a query times out, if there's a following query right away it will not even go to the resolver and just return the value of the previously timed out query, even if they are two completely different queries with different schemas.

To Reproduce
Steps to reproduce the behavior:

  1. Make you resolver take longer than the configured time out, if you are using the default it will be 30s
  2. Issue a query to the server
  3. Right after the query times out issue another query
  4. Your first query will get the Execution canceled because timeout of 30000 millis was reached response
  5. Your second query will have the response payload from the first timed out query

Expected behavior
Both queries should have the Execution canceled because timeout of 30000 millis was reached response

UPDATE: it only happens when graphql.servlet.async.enabled is true

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions