Accumulated Delay

[giuseppe.corti]

Hi ManKeer,

If you are expecting only one client session, there are two strange things that can be inferred from this request list:

1) It seems that there are two streams of parallel requests separated by about 200 milliseconds.
Look for example at the first two, both of them with LS_cause=new.ap, that means that both are triggered by an explicit call of the connect method of the API.

2) Then new attempts are noted every 4 seconds. This means that the client library fails to establish the session within the defined timeout, precisely 4 seconds, and then proceeds with a new attempt.
Understanding why it fails is difficult with just this log excerpt, but it may be that the client is not receiving at all the create_request reply or the next attempt to bind is unsuccessful.
Are you targeting a single instance of Lightstreamer server or a cluster of two or more instances? Because in the latter case maybe there are addressing problems, i.e. two requests from the same client end up at two different instances.

Regards,
Giuseppe

[ManKeer]

why do I receive this message " Unexpected update for item xxxx" ?