-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
CXF-8629: AsyncHTTPConduit (hc5) should support chunked request / response. Add test cases with auto-redirect #2202
base: main
Are you sure you want to change the base?
Conversation
a1226e1
to
031cc4e
Compare
camel-spring-boot-examples-8.10.0.zip |
@jyinpci the issue seems clear now, the logging comes from the server AND the client since you have configured the logging feature in the bus (which is this particular case is the same for server and the client). |
Hi @reta, Thanks for looking into this again. I am afraid it was not double-logging by the server and the client. Yes, both server and client logged the response. But the server logged the response once (indicated by "Outbound Message" label), and the client logged the response twice (indicated by "Inbound Message" label). In fact, because of the null body, it caused Camel to fail afterwards. Please note this was done using Camel without synchronous=true on the endpoint - I am under the impression that with the async support in CXF http client, we do not have to use synchronous=true with Camel. Here is the log generated by the test project I submitted: 2024-12-23T19:39:49.341-05:00 INFO 8592 --- [ - timer://test] o.a.c.interceptor.LoggingOutInterceptor : Outbound MessageID: 1
|
Hi @jyinpci , I think you are very right, and I believe I could reproduce the issue successfully now - the key is to use |
dc196aa
to
0c5bd02
Compare
…ponse. Add test cases with auto-redirect
0c5bd02
to
bd5f016
Compare
AsyncHTTPConduit (hc5) should support chunked request / response. Add test cases with auto-redirect