Application Enablement Services (AES ) : AES Is Terminating the Application Connections.

Doc ID    SOLN212128
Version:    2.0
Status:    Published
Published date:    28 Mar 2014
Created Date:    12 Oct 2012
Author:   
d4
 

Details

Application Enablement Services (AES ) system is on Release 4.2.4 patch 2.

AES is Terminating the Application connections.

Problem Clarification

AES  has terminated the application connection when there are too many messages coming on it. In other words we could say that there may be too many request pending in the AES which caused it to drop the connection with the TSAPI applications.

Cause

Its a software issue and AES needs to be upgraded :

we see that there were critical errors regarding the query inconsistency

10:13:34 ERROR:CRITICAL:TSAPI:TSERVER:ClientHandler.cpp/680 95 SendToClient: Application Global PABX Monitor (conn 20 IP 172.XX.XX.XX) is not processing messages from its queue. Send to app failed 5 times with send=0, wait=12c, retry=5. This connection will be dropped.

10:13:34 ERROR:WARNING:TSAPI:TSERVER:DriverService.cpp/1607 7 LDRV[1]: Cannot receive message from Driver ID 1, Driver Name AVAYA#ISLASICILIA#CSTA#TRANSCISICILIA. The client connection for the message may have been closed.

10:13:34 ERROR:WARNING:TSAPI:TSERVER:DriverService.cpp/1607 7 LDRV[1]: Cannot receive message from Driver ID 1, Driver Name AVAYA#ISLASICILIA#CSTA#TRANSCISICILIA. The client connection for the message may have been closed.


10:13:34 ERROR:CRITICAL:TSAPI:TSERVER:DriverService.cpp/1518 72 TDI Receive from Driver: Semaphore/queue inconsistency for driver ID 1; driver registration state is 3
10:13:34 ERROR:WARNING:TSAPI:TSERVER:DriverService.cpp/1616 7 LDRV[1]: Cannot receive messages from Driver ID 1 Driver Name AVAYA#ISLASICILIA#CSTA#TRANSCISICILIA, rc = ffffffff
 

Solution

In the above snippet you can see the Semaphore/queue inconsistency error messages.

Prior to AE Services 5.2.3, if a TSAPI application was terminated while it had many outstanding requests, the TSAPI Service would log a critical error describing a semaphore/queue inconsistency. For AE Services 5.2.3, the likelihood of these errors being logged is significantly reduced. Hence the recommendation is to upgrade to the AES release 5.2.3.
 


Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy