Hi,

just installed 7.2 verison on tomcat 8.5.3. After AES Connector configuration complete catalonia.out files started growing with many entries:

- Handling INVOKE ID 8050955 for TSProvider[#2]@5c0a3c14
- DONE handling INVOKE ID 8050955 for TSProvider[#2]@5c0a3c14
- Sent InvokeID 492734 for TSProvider[#4]@65e28319
- Received invokeID 492734 for TSProvider[#4]@65e28319
- Handling INVOKE ID 492734 for TSProvider[#4]@65e28319
- DONE handling INVOKE ID 492734 for TSProvider[#4]@65e28319
- Sent InvokeID 8050956 for TSProvider[#2]@5c0a3c14
etc

Aesconnector Trace Verbosity is set to 0

How to turn it off ?

The tsapi.pro in the Tomcat/lib should dictate this.

debugLevel=0
127.0.0.1=450
altTraceFile=tsapi_trace.txt

Any JTAPI log should've been written to the tsapi_trace.txt

Thanks for your reply. My tsapi.pro looks similar:

#Sun Nov 06 00:33:04 EST 2005

debugLevel=0
10.48.XX.XXX=450
10.48.XX.XXX=450

altTraceFile=tsapi_trace.txt

trustStoreLocation=/usr/share/tomcat/tomcat8/webapps/aesconnector/WEB-INF/lib/avayaprca.jks
trustStorePassword=password

I tried to remove truststore definition and second AES as well with no luck.

Try an absolute path for the tsapi_trace.txt file?

For example:
altTraceFile=c:/temp/tsapi_trace.txt

File location is not a problem. When I change debugLevel to something other than 0 aesconnetor starts to log to tsapi_trace.txt file but continue to log to catalina.out file.

Finally I was able to solve the problem. I'm not sure what exactly was wrong but Eclipse export runtime libraries and replace them on tomcat server did the trick.

Hello OldSeb and Others!

I do not know how you was able to find this solution but it DOES work!
I did comparison, but all the substituted files were the same. So.. it is like a miracle...

Thank you a lot for your answer.
(BTW I found another thread which did not help me https://www.devconnectprogram.com/forums/posts/list/21437.page#p151120)

Hello,

One more observation regarding aesconnector debug logs.

If you set debugLevel = 1 (6,7) then you will get logs immediately after tomcat start. Depending on the settings in tsapi.pro you can get them in catalina.out or in altTraceFile location. In my case altTraceFile must be absolute (relative path does not work)!

If you set debugLevel = 0 then you will not get logs immediately after tomcat start. But you may start to receive them for example after call has arrived and application has started processing. The reason is in ddlog4j.properties for that specific application. If you see that the line

# log4j.rootLogger=error, stdout

is uncommented then there is a big probability that it is the reason why you see all this extreme logging.

Also, check tomcat/lib/log4j.properties
If you have any then make sure that either the line is commented or set to log only warning instead of DEBUG
log4j.rootCategory=WARN, CONSOLE

But please take into account that all described above is only my experience and may not work in your case.