[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
How to catch a "SetError() #6: connect(): A remote host refused an attempted connect operation" problem
Hi All,
We are using HTTPAPI to call a remote service. But for some reason, the
other party server is down. But we want to keep our application running
and have made provisions if the data from that service is not
provided. However the connect() functions "hangs" for approx 2 minutes
before the "SetError() #6: connect(): A remote host refused an
attempted connect operation" is returned. This long duration is causing
a 500 error in our web-application.
I understand that this is not a HTTPAPI problem from the archives. But
I like to get around this. Is there any way that I can test whether the
remote host is available ?
I have set a timeout of 1 sec in the post. I also tried using the
http_set_100_timeout() API prior to the post. But at no effect. We are
using HTTPAPI version 1.23
Met vriendelijke groet / Kind regards,
Rick Bovet
Development Manager
P please observe the new direct dial below
cid:image001.png@01CB5418.F5751370
ECi Software Solutions
Siriusdreef 66, 2132 WT Hoofddorp
Postbus 3005, 2130 KA Hoofddorp
Netherlands
Tel. +31 (0)23-555 49 49
Fax +31 (0)23-562 58 48
Direct dial: +31 (0)23-564 98 55
[1]rbovet@xxxxxxxxxxxxxxxx
[2]www.eci.eu & [3]www.easyorder.eu
ECi Software Solutions is a division of eCommerce Industries, Inc
[4]www.ecisolutions.com
P please consider the environment before printing this e-mail
References
1. mailto:jenaam@xxxxxxxxxxxxxxxx
2. http://www.eci.eu/
3. http://www.easyorder.eu/
4. http://www.ecisolutions.com/
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------