Author Topic: Platform SDK: ProtocolManagementService & ADDP  (Read 6438 times)

Offline jamesmurphyau

  • Full Member
  • ***
  • Posts: 123
  • Karma: 2
Platform SDK: ProtocolManagementService & ADDP
« on: June 23, 2009, 02:02:07 AM »
Hey Guys,

I'm using ADDP in my code:

[code]
tcfg.UseAddp = true;
tcfg.AddpClientTimeout = 10;
tcfg.AddpServerTimeout = 10;
tcfg.AddpTrace = "both";
[/code]

But sometimes my client gets disconnected... An example:

[code]
08:42:39.796 Std 07041 Socket 420 is not responding within 10000 milliseconds, remote socket 0
08:42:39.796 Trc 04524 Client <client> disconnected on [420], id=000410dc
@08:42:39.8120 [ISCC] Location <client>:000410dc@/0 is removed
@08:42:39.8120 [ISCC] Location object <client>:000410dc@/0/0 is removed
[/code]

Though the last message TServer sent me before this disconnect was:

[code]
08:42:39.265 Trc 04542 EventOnHook sent to [420] (000410dc <client> 10.112.128.61:2827)
[/code]

This is around 500ms before I get disconnected...

My client does receive this message:

[code]
2009-06-23 08:42:11,835 TServMon  INFO : Received event EventOnHook.
[/code]

Am I using ADDP incorrectly? What could be causing this?

Thanks

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: Platform SDK: ProtocolManagementService & ADDP
« Reply #1 on: June 24, 2009, 07:06:10 AM »
Hi skoom,

It seems time on client and server is not synchronized and that leads to some confusion during your analysis:

- T-Server sent "EventOnHook" at 08:42:39:265
- Your app received it at 08:42:11,835 what means it was received it before T-Server sent it ;)

Based on that time on client side is shifted around 27 seconds back in comparison with server time. So you should check T-Server log at the time 08:43:07 for more details.

R.

Offline jamesmurphyau

  • Full Member
  • ***
  • Posts: 123
  • Karma: 2
Re: Platform SDK: ProtocolManagementService & ADDP
« Reply #2 on: June 24, 2009, 11:52:15 PM »
Yeah the two servers aren't in sync. (I just learn to live with it, other people control that haha)

Does that affect ADDP?

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: Platform SDK: ProtocolManagementService & ADDP
« Reply #3 on: June 25, 2009, 05:23:12 PM »
[quote]Does that affect ADDP?[/quote]

No, it doesn't but it's confusing when doing log analysis

In your example

- T-Server sent ADDP ping to the application at 08:42:29.xxx
- T-Server sent "EventOnHook" at 08:42:39:265
- T-Server didn't receive response to last ADDP ping within configured timeout (10s) so disconnected the client
- Your app received "EventOnHook" at 08:42:11,835

Have your application received T-Server ping around 08:42:01.xxx? If yes - did it send reply?

R.

Offline jamesmurphyau

  • Full Member
  • ***
  • Posts: 123
  • Karma: 2
Re: Platform SDK: ProtocolManagementService & ADDP
« Reply #4 on: June 26, 2009, 01:31:41 AM »
I'm not sure - I couldn't find in the TServer logs where the server pings my client, and my code doesn't have anything it it for handling logging ping requests and replies...

How would I get more info about the ADDP ping requests/replies (in my code and in TServer)

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: Platform SDK: ProtocolManagementService & ADDP
« Reply #5 on: June 29, 2009, 07:55:54 PM »
T-Server should show ADDP messages in its log when logging level is set to debug. About your code - what SDK (Application Blocks?) are you developing with?

R.

Offline jamesmurphyau

  • Full Member
  • ***
  • Posts: 123
  • Karma: 2
Re: Platform SDK: ProtocolManagementService & ADDP
« Reply #6 on: July 19, 2009, 06:14:54 AM »
Are these ADDP messages in the logs?

-AP[1343]->-1052 @16:01:44.3900
-AP[817]-<-1052 @16:01:44.3900
-Ap[817]->-1052 @16:01:44.3900
-AP[818]-<-1052 @16:01:44.3900
-Ap[818]->-1052 @16:01:44.3900
-Ap[1343]-<-1052 @16:01:44.3900

-AP[1344]->-1052 @16:01:54.3900
-Ap[1344]-<-1052 @16:01:54.3900
16:01:54.390 Trc 04524 Client recboy disconnected on [1052], id=00003320
@16:01:54.3900 [ISCC] Location recboy:00003320@/0 is removed
@16:01:54.3900 [ISCC] Location object recboy:00003320@/0/0 is removed

This is what I got the last time my client disconnected.

For my code, yeah I'm using ProtocolManagementServices.