-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Reusing active connection #2114
Comments
we would prefer you follow the process exactly as described: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue I don't consider this a priority just yet as no one else has reported this, and this is possibly a non-issue for internal / pre-prod tests. tagging as |
How to pull request? |
closing this as |
Just dumping thoughts here as it might be related to something I was looking into. Have a team getting some socket timeouts in a huge pipeline (inconsistently and based on timing <5ms probably on handshake or even the client side) and I was wondering about this Http Client configuration. Reading through the previous Apache lib they used to have a multi thread connection mgr. I think the newer version (currently in use) must have something of that nature and some tweaks in the current client might be needed. For now consider me just as an observer of this thread although I might play around that area of the code based on my availability. Regardless it's probably too sensitive to try to put into 1.3.0 if intention is to release in the next couple weeks. https://stackoverflow.com/questions/35939602/apache-httpclient-and-httpconnection-in-a-multithreaded-applicatio |
@ptrthomas A new connection is now opeened and closed for each request. After some testing, I still received timeout issues. |
my feature
my karate-config
fucntion fn() { karate.configure('readTimeout', 30000);}
and my karate.log
The logs show that a tls handhsake is performed for each request. Have also debugged it with wireshark and can confirm it.
The log also show tht socket timeout is set to 0 after a request is handled
Once a connection is established, requests should reuse the same session, this implicates handshake is not repeated
Stack overflow question https://stackoverflow.com/questions/73568779/connnections-handling/73569628#73569628
The text was updated successfully, but these errors were encountered: