Our load balancers send an HTTP request string to EEM with an interval of 5 seconds and check whether the HTTP receive string matches the string defined by us or it returns a HTTP code which indicates an error/health problem.
The HTTP request string is: GET /spin/eiam/eiam.csp HTTP/1.1\r\nHost: ApmEem\r\nConnection: Close\r\n\r\n
The receive string defined by us is: CA Embedded Entitlements Manager
We found that there are so many CLOSE_WAIT sockets from our load balancers that it causes the EEM UI to be non-responsive i.e. the main EEM page keeps reloading after it is opened.
The root cause was found to be too frequent access of the EEM page from the load balancer.
After changing the EEM page request interval to be greater than 8 seconds and timeout to be greater than 25 seconds, the EEM page loading problem was resolved.