We have an application using EMC XML servers to do screen pops and call control and we're getting outstandingRequestLimitExceeded errors with CSTAMakeCall. Below is a sample of the request and error in the TSAPI logs on one of the AES servers. What does the oustanding request limit exceeded mean? If theres a limit around number of concurrent requests it can process do you know what that limit is? Is the limit at the CM level or AES level because we have 11 AES boxes.

CSTA Log:
06/02/2017 10:23:49.444:TSAPI:Thread 0x977d0b90: TSERVER Src: CLNT
06/02/2017 10:23:49.444:TSAPI:Thread 0x977d0b90: Login: "emcxmluser1" App Name: "AXMLServer" SessionID: 40 Transport ID: 172.23.73.25
06/02/2017 10:23:49.444:TSAPI:Thread 0x977d0b90: InvokeID: 100017960
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: Driver: AVAYA#SWLINK11#CSTA-S#EMC-AES-1
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: Message:
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: value CSTAMakeCall ::=
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: {
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: callingDevice "55504",
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: calledDevice "917087616308"
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: }
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90:
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: Private Data:
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: value ATTMakeCall ::=
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: {
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: destRoute "",
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: priorityCalling FALSE,
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: userInfo
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: {
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: type uuiIa5Ascii,
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: data ''H
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: }
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90: }
06/02/2017 10:23:49.445:TSAPI:Thread 0x977d0b90:
06/02/2017 10:23:49.530:TSAPI:Thread 0x9b3d6b90: TSERVER Src: DRVR
06/02/2017 10:23:49.530:TSAPI:Thread 0x9b3d6b90: Login: "emcxmluser1" App Name: "AXMLServer" SessionID: 40 Transport ID: 172.23.73.25
06/02/2017 10:23:49.531:TSAPI:Thread 0x9b3d6b90: InvokeID: 100017960
06/02/2017 10:23:49.531:TSAPI:Thread 0x9b3d6b90: Driver: AVAYA#SWLINK11#CSTA-S#EMC-AES-1
06/02/2017 10:23:49.531:TSAPI:Thread 0x9b3d6b90: Message:
06/02/2017 10:23:49.531:TSAPI:Thread 0x9b3d6b90: value UniversalFailureConfEvent ::=
06/02/2017 10:23:49.531:TSAPI:Thread 0x9b3d6b90: {
06/02/2017 10:23:49.531:TSAPI:Thread 0x9b3d6b90: error outstandingRequestLimitExceeded
06/02/2017 10:23:49.531:TSAPI:Thread 0x9b3d6b90: }


G3trace:
06/02/2017 10:23:49.454:TSAPI:swlink11: Received CSTA Msg (CSTAREQUEST)(3) (CSTA_MAKE_CALL)(23)
06/02/2017 10:23:49.454:TSAPI:swlink11: msgoff(76)msglen(128)privoff(24)privlen(52)
06/02/2017 10:23:49.454:TSAPI:swlink11: invokeID(20503)monXref(0)sessionID(40)clsOfServ(0)
06/02/2017 10:23:49.454:TSAPI:swlink11: callingDevice(55504)
06/02/2017 10:23:49.454:TSAPI:swlink11: calledDevice(917087616308)
06/02/2017 10:23:49.454:TSAPI:swlink11: eventType(ATT_MAKE_CALL)(110)
06/02/2017 10:23:49.454:TSAPI:swlink11: priorityCalling(F)
06/02/2017 10:23:49.454:TSAPI:swlink11: destRoute()
06/02/2017 10:23:49.454:TSAPI:swlink11: userInfotype(UUI_IA5_ASCII)(4)
06/02/2017 10:23:49.454:TSAPI:swlink11: .length(0)
06/02/2017 10:23:49.456:TSAPI:swlink11: Sent ASAI Message A3PDCInfo
06/02/2017 10:23:49.456:TSAPI:swlink11: cap,prim,sao_id C_3PDC_REQ,C_REQUEST,42182968
06/02/2017 10:23:49.456:TSAPI:swlink11: extension 55504
06/02/2017 10:23:49.456:TSAPI:swlink11: domain_type 3

06/02/2017 10:23:49.528:TSAPI:LinkThread01: Received ASAI Message A3PDCNak
06/02/2017 10:23:49.528:TSAPI:LinkThread01: cap,prim,sao_id C_3PDC_CONF,C_NEG_ACK,42182968
06/02/2017 10:23:49.528:TSAPI:LinkThread01: cause_value CS3/63
06/02/2017 10:23:49.529:TSAPI:LinkThread01: Sent CSTA Msg (CSTACONFIRMATION)(5) (CSTA_UNIVERSAL_FAILURE_CONF)(53)
06/02/2017 10:23:49.529:TSAPI:LinkThread01: msgoff(24)msglen(4)privoff(0)privlen(0)
06/02/2017 10:23:49.529:TSAPI:LinkThread01: invokeID(20503)monXref(2989)sessionID(40)clsOfServ(0)
06/02/2017 10:23:49.529:TSAPI:LinkThread01: error(OUTSTANDING_REQUEST_LIMIT_EXCEEDED)(44)

OUTSTANDING_REQUEST_LIMIT_EXCEEDED is a fairly obscure error and, as you can see, it doesn't provide a clear description of the problem.

In your case, Communication Manager is sending the error when AE Services tries to take "Domain Control" of 55504. AE Services must do this in order to perform one of several operations, such as Monitor Device or Make Call.

There is a limit to the number of applications that can take "Domain Control" of a station. I think the limit may have been increased recently but, for most releases of Communication Manager, the limit is 4. TSAPI, DMCC & JTAPI applications on a single AE Services can share a single DC but CVLAN & DLG applications or any application on another AE Services cannot. So, my theory is that 55504 is already being used by applications on some of your other AE Services.

Martin

So if this application makes a CSTAMakeCall request on a AES thats not monitoring the device, how long does it hold onto the Domain Control? Is there a way in the CM to find out which AES servers have domain control of a device?

I am not sure how long the DC is held though I would expect it to be held for the duration of the call.

I do not know of any way to tell what AE Services already have control of a station.

Martin