We have our xMatters web services fronted, we have specified the single URL as both the primary and secondary servers in IAConfig.xml. In production the URL is a load balanced URL, so the risk is decreased however in our development and test environments, there is only one AlarmPoint webserver.
If there is any issue with connecting to the URL, the intergration agent tries using the secondary (which is the same as the primary) except for production the odds are it cannot send a heartbeat there either. At which point the integration agent completely hangs. It no longer even queues events coming from HP Service Manager. Once we resolve the issue, get-status does seem to eventually show PRIMARY ACCEPTED, however the logs stop, and it still doesn't accept events from HP Service Manager. To get things working right, we have to restart the integration agent.
Why does the integration agent lock up when it cannot get a successful heartbeat and why doesn't it retry on its own without having to restart?