ADDP disconnect problem

[Jeff]

Dear Genesys Professionals,

I am not new to Genesys and I have been posting on this site for about two years, focusing mainly on operational side. This time around, I need your help with getting a handle on addp. I have added addp to my TConnection control to make sure tserver and my application is always connected.

Here is the code of how I did it:

    Call TConnection.ConfigureAddp(10, 20, addpTraceFull)
    Call TConnection.EnableAddp(True)

I do this before creating a connection and once connection is established I can confirm continuous addp-pings at 10 second intervals like this

-AP[11]-<-524 @22:14:03.0150
-Ap[11]->-524
-AP[12]-<-524 @22:14:13.0150
-Ap[12]->-524
-AP[13]-<-524 @22:14:23.0150
-Ap[13]->-524
-AP[14]-<-524 @22:14:33.0150
-Ap[14]->-524
-AP[15]-<-524 @22:14:43.0150
-Ap[15]->-524
-AP[16]-<-524 @22:14:53.0150
-Ap[16]->-524
-AP[17]-<-524 @22:15:03.0150
-Ap[17]->-524
-AP[18]-<-524 @22:15:13.0150
-Ap[18]->-524

But then, I get this:

22:18:54.687 Trc 04524 Client PandaExpress disconnected on 524, id=001c:0003
(addp-dispose) fd=524

I thought it was strange because non of other Genesys applications have disconnected plus there was no network outage or anything.
What is worse, I can trace all the addps before that (my client is 524):

IPMX_TServer.20061002_182545_078.log (23242):-AP[1]-<-524 @22:10:58.6400
IPMX_TServer.20061002_182545_078.log (23244):-AP[2]-<-524 @22:11:08.6400
IPMX_TServer.20061002_182545_078.log (23246):-AP[3]-<-524 @22:11:18.6400
IPMX_TServer.20061002_182545_078.log (23248):-AP[4]-<-524 @22:11:28.6400
IPMX_TServer.20061002_182545_078.log (23250):-AP[5]-<-524 @22:11:38.6400
IPMX_TServer.20061002_182545_078.log (23252):-AP[6]-<-524 @22:11:48.6400
IPMX_TServer.20061002_182545_078.log (23254):-AP[7]-<-524 @22:11:58.6710
IPMX_TServer.20061002_182545_078.log (23688):-AP[1]->-524 @22:12:18.6710
IPMX_TServer.20061002_182545_078.log (23847):-AP[8]-<-524 @22:12:36.7500
IPMX_TServer.20061002_182545_078.log (23905):-AP[9]-<-524 @22:12:52.1560
IPMX_TServer.20061002_182545_078.log (24094):-AP[2]->-524 @22:13:12.1560
IPMX_TServer.20061002_182545_078.log (24465):-AP[3]->-524 @22:13:32.1560
IPMX_TServer.20061002_182545_078.log (24624):-AP[10]-<-524 @22:13:51.4840
IPMX_TServer.20061002_182545_078.log (24682):-AP[11]-<-524 @22:14:03.0150
IPMX_TServer.20061002_182545_078.log (24684):-AP[12]-<-524 @22:14:13.0150
IPMX_TServer.20061002_182545_078.log (24686):-AP[13]-<-524 @22:14:23.0150
IPMX_TServer.20061002_182545_078.log (24688):-AP[14]-<-524 @22:14:33.0150
IPMX_TServer.20061002_182545_078.log (24690):-AP[15]-<-524 @22:14:43.0150
IPMX_TServer.20061002_182545_078.log (24692):-AP[16]-<-524 @22:14:53.0150
IPMX_TServer.20061002_182545_078.log (24694):-AP[17]-<-524 @22:15:03.0150
IPMX_TServer.20061002_182545_078.log (24696):-AP[18]-<-524 @22:15:13.0150
IPMX_TServer.20061002_182545_078.log (24698):-AP[19]-<-524 @22:15:23.0150
IPMX_TServer.20061002_182545_078.log (24700):-AP[20]-<-524 @22:15:33.0150
IPMX_TServer.20061002_182545_078.log (24702):-AP[21]-<-524 @22:15:43.0150
IPMX_TServer.20061002_182545_078.log (24704):-AP[22]-<-524 @22:15:53.0150
IPMX_TServer.20061002_182545_078.log (24706):-AP[23]-<-524 @22:16:03.0150
IPMX_TServer.20061002_182545_078.log (24708):-AP[24]-<-524 @22:16:13.0150
IPMX_TServer.20061002_182545_078.log (24710):-AP[25]-<-524 @22:16:23.0150
IPMX_TServer.20061002_182545_078.log (24712):-AP[26]-<-524 @22:16:33.0150
IPMX_TServer.20061002_182545_078.log (24714):-AP[27]-<-524 @22:16:43.0150
IPMX_TServer.20061002_182545_078.log (24716):-AP[28]-<-524 @22:16:53.0150
IPMX_TServer.20061002_182545_078.log (24718):-AP[29]-<-524 @22:17:03.0150
IPMX_TServer.20061002_182545_078.log (24720):-AP[30]-<-524 @22:17:13.0150
IPMX_TServer.20061002_182545_078.log (24722):-AP[31]-<-524 @22:17:23.0150
IPMX_TServer.20061002_182545_078.log (24724):-AP[32]-<-524 @22:17:33.1090
IPMX_TServer.20061002_182545_078.log (24726):-AP[33]-<-524 @22:17:43.1090
IPMX_TServer.20061002_182545_078.log (24728):-AP[34]-<-524 @22:17:53.1090
IPMX_TServer.20061002_182545_078.log (24730):-AP[35]-<-524 @22:18:03.1090
IPMX_TServer.20061002_182545_078.log (24924):-AP[4]->-524 @22:18:23.1090
IPMX_TServer.20061002_182545_078.log (25323):-AP[5]->-524 @22:18:43.1090
IPMX_TServer.20061002_182545_078.log (25324):-AP[36]-<-524 @22:18:44.6870
IPMX_TServer.20061002_182545_078.log (25482):-AP[1]-<-524 @22:22:04.6560
IPMX_TServer.20061002_182545_078.log (25484):-AP[2]-<-524 @22:22:14.6560
IPMX_TServer.20061002_182545_078.log (25486):-AP[3]-<-524 @22:22:24.6560
IPMX_TServer.20061002_182545_078.log (25488):-AP[4]-<-524 @22:22:34.6560
IPMX_TServer.20061002_182545_078.log (25490):-AP[5]-<-524 @22:22:44.6560
IPMX_TServer.20061002_182545_078.log (25492):-AP[6]-<-524 @22:22:54.6560

What is the problem because I do not think it is network.
                                                                                                                      - Jeff

[victor]

I checked the log you have provided, and here is the problem:

IPMX_TServer.20061002_182545_078.log (24730):-AP[35]-<-524 @22:18:03.1090
IPMX_TServer.20061002_182545_078.log (24924):-AP[4]->-524 @22:18:23.1090
IPMX_TServer.20061002_182545_078.log (25323):-AP[5]->-524 @22:18:43.1090
[color=Red]IPMX_TServer.20061002_182545_078.log (25324):-AP[36]-<-524 @22:18:44.6870
IPMX_TServer.20061002_182545_078.log (25482):-AP[1]-<-524 @22:22:04.6560[/color]
IPMX_TServer.20061002_182545_078.log (25484):-AP[2]-<-524 @22:22:14.6560


It seems like your 10 second ping was interrupted for 41 seconds.
There is a 41 second gap between AP[35] and AP[36]. According to you, it should be 10 seconds, so this is why your application got disconnected.

I am guessing that you probably disconnected your cable, or if you are debugging you program, probably paused the program causing the disconnect.