graphql-spring-boot icon indicating copy to clipboard operation
graphql-spring-boot copied to clipboard

Query returning the result of previously timed out query

Open paulohenriqu opened this issue 1 year ago • 0 comments

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

paulohenriqu avatar May 06 '23 00:05 paulohenriqu