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.
|