AES keeps trying to connect to weblm without timeout. and grace period do not work.
Issue is identified as known issue on AES 8.1.2 and JIRA
AES-20720
has been opened for the issue.
In some cases, socket connection to client application fails as below.
<132>Jul 30 03:42:33 ctrlsaes1 TSAPI[15098]: -04:00 2020 981 1 com.avaya.aes | ERROR:WARNING:TSERVER:ClnMsg.cpp/1259 75 FwdDriverMsg[1]: Could not find invokeID 0xcda7 for message ACSUniversalFailureConfEvent from driver AVAYA#CTRLSCM#CSTA#CTRLSAES1: loginID=Okhla-Easyjet, app=TSAPI Adapter, sessionID=6871, ip=172.28.3.200. Number of missing invokeIDs for this driver: 1
<132>Jul 30 03:42:33 ctrlsaes1 TSAPI[15098]: -04:00 2020 981 1 com.avaya.aes | ERROR:WARNING:TSERVER:ClientHandler.cpp/769 10 SendMsg(): getpeername() failed for socket -1, errno=9
<132>Jul 30 04:25:21 ctrlsaes1 TSAPI[15098]: -04:00 2020 231 1 com.avaya.aes | ERROR:WARNING:TSERVER:ClientHandler.cpp/769 10 SendMsg(): getpeername()
failed for socket 28, errno=9
Also, connections to the devices has resource busy errors as they tend to use different sessions for connectivity causing issues.
This also causing the number of messages to increase and reach threshold level and causing the CTI link to bounce
<132>Jul 30 03:42:33 ctrlsaes1 TSAPI[15098]: -04:00 2020 981 1 com.avaya.aes | ERROR:WARNING:TSERVER:ClnMsg.cpp/1259 75 FwdDriverMsg[1]: Could not find invokeID 0xcda7 for message ACSUniversalFailureConfEvent from driver AVAYA#CTRLSCM#CSTA#CTRLSAES1: loginID=Okhla-Easyjet, app=TSAPI Adapter, sessionID=6871, ip=172.28.3.200. Number of missing invokeIDs for this driver: 1
<132>Jul 30 03:42:33 ctrlsaes1 TSAPI[15098]: -04:00 2020 981 1 com.avaya.aes | ERROR:WARNING:TSERVER:ClientHandler.cpp/769 10 SendMsg(): getpeername() failed for socket -1, errno=9
<132>Jul 30 04:25:21 ctrlsaes1 TSAPI[15098]: -04:00 2020 231 1 com.avaya.aes | ERROR:WARNING:TSERVER:ClientHandler.cpp/769 10 SendMsg(): getpeername()
failed for socket 28, errno=9
