MID Server - AMBClient exception when instantiating a AMBClient error observed after Upgrade.Issue MID Server - Unresolved issues post upgrade - AMBClient exception when instantiating a AMBClient. Connection is not successful error CauseThis issue might occur after the Upgrade. Mid Server will be Up and running but AMB client exception error will observed in the Mid Server Issues.Resolution1. Restarting the MID Server is one way to force it to attempt to reconnect the AMB Channel. That may be all that needs doing if the cause was a temporary network issue that is now resolved.2. If you simply cannot get the AMB Channel working, you can turn it off, and the pre-Helsinki behavior will be used. With this MID Server Parameter set, the poll time will be 5s by default, and no attempt will be made to create an AMB connection.3. mid.disable_amb=true4. If the AMB channel is intermittent, and does work most of the time, then instead of turning it off, you can set the poll time to 5s so that if the AMB channel is down then it will poll every 5 seconds, instead of the default 40s.5. You can reduce that to 5 seconds by setting the MID Server Parameter: mid.poll.time=5 6. Check if there is underscore "_" in the hostname of the proxy as having "_" in the hostname is not an industry standard. 7. If the Proxy Hostname is a URL, We don't have to give http/https in the Proxy hostname.