MID Server log is showing AMB channel connection is not successful with an Illegal character error.Issue The MID Server log shows AMB channel Connection is not successful with an Illegal character error. The following error message can be seen in the agent logs: 03/05/20 13:39:07 (877) ECCQueueMonitor.40 WARNING *** WARNING *** Reconnecting AMB channel..03/05/20 13:39:07 (877) ECCQueueMonitor.40 Initializing AMB client...03/05/20 13:39:07 (877) AMBClientProvider Connecting AMB client to instance...03/05/20 13:39:07 (877) AMBClientProvider SEVERE *** ERROR *** AMBClient exception when instantiating a AMBClient. Connection is not successfulcom.snc.glide.amb.AMBClient$ProxyBuilderException: java.net.URISyntaxException: Illegal character in hostname at index 15: http://host_name:8080at com.snc.glide.amb.AMBClient$Builder.buildProxyURI(AMBClient.java:314)at com.snc.glide.amb.AMBClient$Builder.setProxy(AMBClient.java:305)at com.service_now.mid.Instance.getAMBClient(Instance.java:777)at com.service_now.mid.amb.AMBClientProvider.connect(AMBClientProvider.java:116)at com.service_now.mid.amb.AMBClientProvider.executeInLock(AMBClientProvider.java:191)at com.service_now.mid.amb.AMBClientProvider.lambda$initialize$0(AMBClientProvider.java:54)at java.lang.Thread.run(Thread.java:748)Caused by: java.net.URISyntaxException: Illegal character in hostname at index 15: http://host_name:8080 //index 15 is the underscoreat java.net.URI$Parser.fail(URI.java:2848)ReleaseAfter upgrades to OrlandoCauseThe most probable cause for this issue is because of using underscore "_" in the proxy hostname and this is considered illegal since Orlando release.ResolutionThe solution to the issue would be either of the following: Enter the IP address of the proxy server in config.xml, as opposed to hostname if you have "_" as part of the hostname.Reconfigure your Proxy Server to remove the underscore "_" from the hostname.Related LinksRFC822 defines this as an illegal character. The recommended solution would be to correct the hostname to a legal one.