ServerSessionNotActiveEvent. This event is sent if a message was
received by the AE Services server but the session has timed out and been
placed in the inactive state. A session enters the inactive state if the
Application Session Duration expires before a
ResetApplicationSessionTImer message is received. Upon receiving
this event, an application must first call disconnect on the application’s
ServiceProvider instance, then take the same recovery actions as for
ServerConnectionDownEvent.

MartinFlynn wrote:Hi Esmeralda,

Please take a look at the code in your callback/listener methods that receive events from AE Services. If these methods perform significant processing (e.g. make database accesses, send DMCC requests to AE Services, make file accesses etc.) then this is almost certainly the cause of your problems.

It is very important that applications exit the callback/listener methods as quickly as possible. Otherwise the SDK will not be able to process other incoming events and, eventually, AE Services outgoing buffers will overflow and it will be forced to bring down the connection.

Make sure that all listeners/callbacks take the incoming event and place it on an internal queue. You should perform the actual event processing using your own, internal, threads.

Martin

JohnBiggs wrote:1) don't you have a lab testing environment? If you do your work against production systems you will be hard pressed to isolate issues with your application
2) if you send a session disconnect, the session is gone. You can not reconnect to it.
3) you may be able to use a remote lab session to do this testing: https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/development_tools_configurations/aes_cm_remote_lab/index.gsp

<StartApplicationSessionNegResponse xmlns="http://www.ecma-international.org/standards/ecma-354/appl_session"><errorCode><applError>Terminated session can not be reconnected. Reason: Client socket closed</applError></errorCode></StartApplicationSessionNegResponse>

you can use newer versions of the SDK with older releases of AE Services at least for a test to make sure there isnt an SDK issue.

yes the sessionCleanupDelay is what I was referring to. How do you know you are initiating recovery in that 1 minute window? are you reacting to the SDK informing you that it didnt get responses to the KA messages? How do you know the recovery request made it to AE Services (you need the AES side logging).

2018-10-27 09:32:00.322 +02:00 [ERR] AES Server connection error. Error: Number of Consecutive keep alives missed: 1. Error type: Missed At Least One Keep Alive Event

2018-10-27 09:32:00.323 +02:00 [INF] Trying to reconnect to the session with ID = 3C1452555FDE19F95B0AD6AE139D635F-9100

2018-10-27 09:32:00.351 +02:00 [ERR] AES Server connection error. Error: Unable to read from socket. Socket to server has been closed.. Error type: Server Connection Down Event

2018-10-27 09:32:00.352 +02:00 [INF] Trying to reconnect to the session with ID = 3C1452555FDE19F95B0AD6AE139D635F-9100

2018-10-27 09:32:00.353 +02:00 [ERR] AES Server connection error. Error: Unable to read from socket. Socket to server has been closed.. Error type: Server Connection Down Event

2018-10-27 09:32:00.355 +02:00 [INF] Trying to reconnect to the session with ID = 3C1452555FDE19F95B0AD6AE139D635F-9100

2018-10-27 09:32:00.415 +02:00 [INF] Number Returned From Reconnectiog = 767

2018-10-27 09:32:00.417 +02:00 [ERR] AES Server connection error. Error: Unable to read from socket. Socket to server has been closed.. Error type: Server Connection Down Event

2018-10-27 09:32:00.418 +02:00 [INF] Trying to reconnect to the session with ID = 3C1452555FDE19F95B0AD6AE139D635F-9100

2018-10-27 09:32:00.509 +02:00 [INF] Number Returned From Reconnectiog = 769

private void Dmcc_OnConnectionError(object sender, ConnectionErrorArgs e)

        {

            logger.Write($"AES Server connection error. Error: {e.Message}. Error type: {e.ErrorType}", LogEventLevel.Error);

            dmcc.Reconnect(e.SessionId);

        }

public void Reconnect(string sessionId)

        {

            logger.Write($"Trying to reconnect to the session with ID = {sessionId}", LogEventLevel.Information);

            var numberReturnedFromReconnectiog = serviceProvider?.Reconnect(sessionId, null);

            logger.Write($"Number Returned From Reconnectiog = {numberReturnedFromReconnectiog}", LogEventLevel.Information);

        }