You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
on servlet async mode, uncatched exception throwed from graphql.kickstart.servlet.HttpRequestInvokerImpl.invoke() will "hang" the main thread, till servlet timeout.
To Reproduce
construct a bad data input to let graphql validation failed. in other words, construct any uncatched exception throwed from graphql.kickstart.servlet.HttpRequestInvokerImpl.invoke()
we will see the error printed on console immediately
client get the data till servlet timeout. and the error msg is about timeout not the exception we made.
Expected behavior
client get the precise exception information immediately.
oliemansm
changed the title
uncatched exception throwed from graphql.kickstart.servlet.HttpRequestInvokerImpl.invoke() will "hang" the main thread
Uncaught exception thrown by HttpRequestInvokerImpl.invoke() causes main thread to "hang"
Jan 23, 2022
Describe the bug
on servlet async mode, uncatched exception throwed from
graphql.kickstart.servlet.HttpRequestInvokerImpl.invoke()
will "hang" the main thread, till servlet timeout.To Reproduce
graphql.kickstart.servlet.HttpRequestInvokerImpl.invoke()
Expected behavior
client get the precise exception information immediately.
Screenshots



Version:
Additional context
maybe some code like this
The text was updated successfully, but these errors were encountered: