Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
CURLOPT_CONNECTTIMEOUT Question
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Bob Sorrells via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 19 Aug 2025 19:07:55 +0000
I support a CURL back-end REST API running on OpenVMS 8.4 with release 7.66.0. All binaries are linked statically with CURL, so issues with shared data spaces should not be an issue. My predecessor wrote a small local C module that calls the libcurl functions. Everything seems to be in order there.
Thinking that it should improve performance, I wrote my code to be sure to reuse an existing handle whenever possible and NOT call curl_slist_free_all() or curl_easy_cleanup() unless something changed that would demand a new handle (URL change, etc.).
I ran a single test thread in which I called CURL 858,976 times against the same URL, with different JSON bodies. On 242 of those calls, I received a CONNECTION TIMEOUT message from CURL after 245 seconds. My code calls curl_easy_setop(curl, CURLOPT_CONNECTTIMEOUT, 7) after establishing each handle.
What could be causing CURL to take 245 seconds to time out, instead of 7 seconds?
Bob Sorrells
Software Engineer/Software Developer
AT&T Entertainment Group (AEG), DirecTV Account
(314) 212-7692 (office)
[cid:image001.png_at_01DC1112.6E482E60]
Read the latest on Amdocs.com<https://amdocsmanagementlimited.newsweaver.com/amdocspeople.MondayMailIndia/15x4r4aj5964g7a4qwciyg/external?a=6&p=8747637&t=2729683> and follow us on LinkedIn<https://amdocsmanagementlimited.newsweaver.com/amdocspeople.MondayMailIndia/13j0vh05v474g7a4qwciyg/external?a=6&p=8747637&t=2729683>, Twitter<https://amdocsmanagementlimited.newsweaver.com/amdocspeople.MondayMailIndia/dovocagaef44g7a4qwciyg/external?a=6&p=8747637&t=2729683>, and Facebook<https://amdocsmanagementlimited.newsweaver.com/amdocspeople.MondayMailIndia/16d5zytzbby4g7a4qwciyg/external?a=6&p=8747637&t=2729683>
This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service>
Received on 2025-08-19
Date: Tue, 19 Aug 2025 19:07:55 +0000
I support a CURL back-end REST API running on OpenVMS 8.4 with release 7.66.0. All binaries are linked statically with CURL, so issues with shared data spaces should not be an issue. My predecessor wrote a small local C module that calls the libcurl functions. Everything seems to be in order there.
Thinking that it should improve performance, I wrote my code to be sure to reuse an existing handle whenever possible and NOT call curl_slist_free_all() or curl_easy_cleanup() unless something changed that would demand a new handle (URL change, etc.).
I ran a single test thread in which I called CURL 858,976 times against the same URL, with different JSON bodies. On 242 of those calls, I received a CONNECTION TIMEOUT message from CURL after 245 seconds. My code calls curl_easy_setop(curl, CURLOPT_CONNECTTIMEOUT, 7) after establishing each handle.
What could be causing CURL to take 245 seconds to time out, instead of 7 seconds?
Bob Sorrells
Software Engineer/Software Developer
AT&T Entertainment Group (AEG), DirecTV Account
(314) 212-7692 (office)
[cid:image001.png_at_01DC1112.6E482E60]
Read the latest on Amdocs.com<https://amdocsmanagementlimited.newsweaver.com/amdocspeople.MondayMailIndia/15x4r4aj5964g7a4qwciyg/external?a=6&p=8747637&t=2729683> and follow us on LinkedIn<https://amdocsmanagementlimited.newsweaver.com/amdocspeople.MondayMailIndia/13j0vh05v474g7a4qwciyg/external?a=6&p=8747637&t=2729683>, Twitter<https://amdocsmanagementlimited.newsweaver.com/amdocspeople.MondayMailIndia/dovocagaef44g7a4qwciyg/external?a=6&p=8747637&t=2729683>, and Facebook<https://amdocsmanagementlimited.newsweaver.com/amdocspeople.MondayMailIndia/16d5zytzbby4g7a4qwciyg/external?a=6&p=8747637&t=2729683>
This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at https://www.amdocs.com/about/email-terms-of-service <https://www.amdocs.com/about/email-terms-of-service>
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
(image/png attachment: image001.png)