Author Message
ShackyPoh
Joined: Jan 13, 2014
Messages: 23
Offline
Hi,

I encountered an issue with running aesconnector, the connector was unable to retrieve the configurations from ddconfig.

The same configurations used for aesconnector 07.20.09.04 works well with no issues. Would like to seek advice on how to resolve this issue. Both tsapi.pro are the same as well.

aesconnrector log

13/06/2022 19:58:50:454 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.init: AES Connector Version is 08.11.08.01
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
13/06/2022 19:58:50:470 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)

massimo__croci
Joined: Jan 31, 2020
Messages: 518
Offline
Hi. Please

- set debugLevel=7 in your "tsapi.pro" ;

- take a look at the "tsapi_trace.txt" for the start up attempt. The exact error message should be visible;

- Set debugLevel back to 0 in your "tsapi.pro" when done.

"tsapi_trace.txt" usually resides in your Tomcat root dir.

The connector does not get informed as to the cause of the failure (aesconnrector log), it just gets back a generic failure.
ShackyPoh
Joined: Jan 13, 2014
Messages: 23
Offline
Hi massimo,

I have tried turning on debug level 7 in tsapi.pro but i do not see any tsapi_tract.txt in the root folder when tomcat service is started.
massimo__croci
Joined: Jan 31, 2020
Messages: 518
Offline
Hi.

In the "tsapi.pro" file, the 'altTraceFile' needs to be configured in order to collect the tsapi tracing associated with the client libraries such as JTAPI and CTIConnector. There isn't any default location or name for the trace file, so you have to specify the absolute path (full path).

Please, double-check on the "tsapi.pro" file if a valid path was configured.
In case of no configuration, remeber to use the forward slash in the path name for all operating systems.
Example:
altTraceFile=C:/temp/tsapi_trace.txt

For more information on JTAPI tracing reference the JTAPI programmer's guide (https://download.avaya.com/css/public/documents/100068966)
Go to:   
Mobile view