janwesterkamp commented on issue #6856: URL: https://github.com/apache/camel-quarkus/issues/6856#issuecomment-2527582402
Hi @jamesnetherton, I did further integration testing with variants using the mostly integration tests from the according test suite (+1000 tests, full test run takes about 2h): Adding `camel-quarkus-platform-http` even as first Maven dependency does not change anything in any combination of extensions. Replacing the `camel-quarkus-vertx-http` with the `camel-quarkus-http` extension removes the warnings from the blog, but the tests start to fail after approximately 10 minutes. Some of the PUT tests fail because of not having the Content-Lenght header set (null instead of the response body size) and others fail because of returning HTTP Status Code 500. Setting the Content-Lenght header manually failed for other methods like POST, GET and HEAD in the past and setting that manually did not succeed - so I deactivated this check on these methods already and calclate the value from the response body only for now. However, for PUT it works with `camel-quarkus-vertx-http` out of the box, but with `camel-quarkus-http` it fails too. May be this is a separate issue... I have more concerns about the internal server errors (HTTP Status Code 500) - this forces me to stay with `camel-quarkus-vertx-http` and a bloaded log for now. So it looks like the log messages came from the use of `camel-quarkus-vertx-http`, but the issue is more complex... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
