I have the following environment setup:

Experience Portal 7.02
WAS:

Linux OS.
dedicated server
12 GB RAM
tomcat 7
JAVA 7.0.79 (oracle)
OD libraries 7.01.0804
AESCONNECTOR from the same version.

we're not allowed to use http, only https. for about one and a half years we have observed issues with the aesconnector, as we can see in the logs that it receives the information but when the application requests it, the response is "no call info available" even when it is known that the info was already received. This happens mostly in the hours of high traffic.

About three weeks ago, we setup another tomcat instance using http, it has been working flawlessly and little to none issues are observed even in high traffic hours.

the problem is that the use of http was approved as a contingency not as a permanent measure, we need a way to ensure that the aesconnector performs using secure protocols.

the server has been tuned with all parameters and recomendations for OD and it's memory consumption is way below the XMX parameter.

Essentially, the https request, which the app is making, is to the same app server which hosts the aesconnector. You need to have the ssl certificate in a keystore that is managed in the runtimeconfig app. I need to see both the app trace.log and aesconnector trace.log to see where exactly it's failing.

the WAS is indeed using a self signed certificate which is registered in the runtimeconfig App.

attached please find documentation of the issues found and a large aesconnector log

I see a sequence of log statements like this for extension 17098. First there a call on 17098 and aesconnector return the call info. Then the call ends. Then some how you app is trying to query for call info again (not sure why) and result in the error.

28/11/2016 17:37:14:130 DEBUG - CallInfo.doGetCallInfo: Got call info for extension 17098
28/11/2016 17:37:20:049 DEBUG - Ending call on extension 17098
28/11/2016 17:41:14:640 ERROR - CallInfo.doGetCallInfoInitialCall: No call info available for extension 17098