-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read Timeout with Graphql extension #11076
Comments
/cc @phillip-kruger, @jmartisk |
Hi @Neisuz - Do you have a small project that recreate this issue so that I can have a look ? |
Yeah I guess we will need to see the code, from the stack trace I'm not sure how GraphQL is involved, this looks like a normal REST call, but for some reason it times out on reading the body (?). Also it seems that you're using Undertow, I'd suggest trying to switch to Vert.x for the web layer. I'm not completely sure if the GraphQL extension can run with Undertow. |
This causes the issue:
|
@stuartwdouglas might be able to help here then. |
any update? |
You probably need to change quarkus.http.read-timeout, which defaults to 60s. If graphql is expecting to be able to read from the client until the client sends it something then you will likely want something a lot larger. Something that is weird is that the resteasy stack trace does not seem to line up with the sources. |
Nope, it does not work. The issue still exists and if a project contains this dependency, it does not allow REST to do "POST, UPDATE..."(as an example) with Graphql.
|
@phillip-kruger, hello, i added some code to your project where you can see what the reason of this issue. |
@stuartwdouglas - this is a very weird scenario - What is being read it a REST service (not GraphQL) - and that is where the timeout occur. You don't even need any GraphQL code, but if you add GraphQL and undertow to a JAX-RS project that use InputStream as parameter on a POST, it hangs. As soon as you remove either of the GraphQL or undertow extension, it works. I am not sure what is happening. |
It would be the combination of the RequireBodyHandlerBuildItem + Undertow. Undertow must not handle requests that have been through the body handler correctly. |
Actually there was already a bug about this (#5959) and it should be fixed, so I am not 100% sure what is happening. |
anything new? |
Is this still an issue? |
Closing for lack of feedback |
Describe the bug
i've got the simple project where i use Rest approach.
When i add quarkus-smallrye-graphql extension and execute the request via Rest approach where i have to deserialize the body i got this ->
probably where it stucks ->
Expected behavior
(Describe the expected behavior clearly and concisely.)
Graphql extension shoudn't affect the behavior of the Rest
Actual behavior
up.
Configuration
1.5.2.Final or 1.6.1.Final - the same behavior.
Java 11
The text was updated successfully, but these errors were encountered: