Scott,
Yes, that's just what I suspect. At present the upgrade is just on the DEV machine. We have a facilities Mgt crowd that does all that.
I think things seem to be working OK except for this connection thing.
There were no errors in the LICPGM log for the upgrade and all the TCP displays have an expected match with those on the PROD machine, including the routing displays.
So it seems like there's a DNS or proxy or firewall problem for facilities Mgt to sort out.
I know now that it has nothing to do HTTPAPI since a simple non-ssl socket that always works hangs as well (although I thought that would work coz it connects to a listener on the same box)
Peter
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Wednesday, 20 September 2017 9:34 AM
To: Midrange Systems Technical Discussion
Subject: [IE] Re: HTTPAPI failing at V7R3
Peter,
This error means that HTTPAPI sent a connect request without any errors, but didn't get a reply.
It almost always (90% of the time) means that a firewall is blocking access. Occasionally (8-9% of the time) it means there's a mistake in routing.
-SK
On 9/18/2017 7:16 PM, Peter Connell wrote:
Just upgraded to V7R3 and all requests via HTTPAPI are timing out with
-
http_url_get(): entered
http_persist_open(): entered
http_long_ParseURL(): entered
DNS resolver retrans: 2
DNS resolver retry : 2
DNS resolver options: x'00000136'
DNS default domain: corp.bayadv
DNS server found: 10.9.64.104
DNS server found: 10.90.100.20
DNS server found: 10.1.77.4
Nagle's algorithm (TCP_NODELAY) disabled.
SetError() #7: Timeout occurred while trying to connect to server!
Any clues please?
Regards, Peter
############################################################## This
correspondence is for the named person's use only. It may contain
confidential or legally privileged information, or both. No
confidentiality or privilege is waived or lost by any mistransmission.
If you receive this correspondence in error, please immediately delete
it from your system and notify the sender. You must not disclose, copy
or rely on any part of this correspondence if you are not the intended
recipient. Any views expressed in this message are those of the
individual sender, except where the sender expressly, and with
authority, states them to be the views of Equifax. If you need
assistance, please contact Equifax :- Australia
www.equifax.com.au/contact New Zealand www.equifax.co.nz/contact
##############################################################
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
############################################################## This correspondence is for the named person's use only. It may contain confidential or legally privileged information, or both. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this correspondence in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or rely on any part of this correspondence if you are not the intended recipient. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views of Equifax. If you need assistance, please contact Equifax :- Australia www.equifax.com.au/contact New Zealand www.equifax.co.nz/contact ##############################################################
midrange.com
