MID server logging java.net.UnknownHostException

Manuel38
Kilo Contributor

hello all, seeing this error in the wrapper.log file on the MID server we have, to connect to one SNOW instance

2018/12/12 06:44:11 | [AMBClientProvider] WARN com.snc.glide.amb.AMBClient - Encountered exception during disconnect(): null
2018/12/12 06:44:11 | [AMBClientProvider] WARN org.eclipse.jetty.client.HttpExchange - CONNECTION FAILED Exchange@feb7636=POST//cscqa.service-now.com:443/api/now/amb/session/finish#CONNECTING(11ms)->EXCEPTED(0ms)
2018/12/12 06:44:11 | java.net.UnknownHostException

SNOW instance is scqa.service-now.com and is resolving fine. 

root@ustlssnmidprd01 logs]# nslookup cscqa.service-now.com
Server: 10.156.255.10
Address: 10.156.255.10#53

Non-authoritative answer:
Name: cscqa.service-now.com
Address: 149.96.50.183

[root@ustlssnmidprd01 logs]#

 

[root@ustlssnmidprd01 logs]# nmap -p 443 cscqa.service-now.com

Starting Nmap 6.40 ( http://nmap.org ) at 2018-12-12 07:20 CST
Nmap scan report for cscqa.service-now.com (149.96.50.183)
Host is up (0.00016s latency).
rDNS record for 149.96.50.183: vip-149-96-50-183.cust.service-now.com
PORT STATE SERVICE
443/tcp filtered https

Nmap done: 1 IP address (1 host up) scanned in 0.41 seconds
[root@ustlssnmidprd01 logs]#

We have a catalog item that is requested from SNOW and performs an API call to our environment. MID server was configured for the solution.

The call is failing sometimes and sometimes works just fine. When it fails we are seeing the error I pasted above on the MID server Wrapper log.

Do you know what could be the reason of the failure ? 

thanks

4 REPLIES 4

Deepak Ingale1
Mega Sage

Hello,

 

Exchange@feb7636=POST//cscqa.service-now.com:443/api/now/amb/session/finish#CONNECTING(11ms)->EXCEPTED(0ms)
2018/12/12 06:44:11 | java.net.UnknownHostException

SNOW instance is scqa.service-now.com and is resolving fine. 

 

POST error is listing the URL as CSCQA and you are saying it is SCQA.

Please see if this is the difference

Manuel38
Kilo Contributor

yes, was my mistake, I wrong copied it. the instance is fine, should be cscqa.service-now.com

Andy101
Kilo Explorer

I am also facing a similar issue with one of my MID Server. Did you find the solution for this?

Manuel38
Kilo Contributor

not yet Andy, we have an internal support team working on this. we reinstalled our MID server and performed few tests but didn't work. Some settings for the MID server were changed on ServiceNow instance after that, but still didn't work.