Jump to content
  • 0

[DEMO] Streaming API : Allowed session count reached (code 7)

Question

Hi everyone !

For a week or two, I can observe a little problem on DEMO with streaming API. When I restart my Application, it closes wisely the API, unregistering everything and closing connection. After that the application restarts, and bam, error 7 "allowed session count reached". On saturday, waiting 60 seconds between stop and start was enough to successfully reconnect to the streaming API, but today (monday, stopped at 17h17 GMT+2), it took 20 minutes to have a successfull restart. 

I think it is server side problem : the session seems to exists... maybe it takes time for the server to successfully close it. I used this API for more than a year and it is the first time I have so much trouble with the streaming API....

Anyone else having similar behaviour on streaming API ?

Thanks !

NLP

Share this post


Link to post

8 answers to this question

Recommended Posts

  • 0
Guest Guest007

Hello Nicols,

I am getting the same error. I didn't get that error 3 weeks ago.

Any update on your side ?

Share this post


Link to post
  • 0

No update 😐

The only things I tried is to wait and try to restart few minutes later...

Actually, it is like a confirmation of the latency when you disconnect / reconnect...

My solution is to ... wait after disconnecting... and sometimes... it takes some time 😫

Have a good day !

NLP

Share this post


Link to post
  • 0

Had similar issues and had to stop my developemnt until I figure out what is wrong.

All began when I started doing automated testing of my software and the session will be opened and closed many times, I will reach the session limit after 5 tests or so.

It may be possible to stop closing the session, I think reconnecting will give you the old session and the problem is solved. Otherwise, a bit risky moving to live account if the issue is server side.

Has this been fixed yet?

Share this post


Link to post
  • 0

No fix => I had the problem yesterday...

Maybe... you can reconnect to the old session but in this case the REST API will connect with different auth infos...
The major problem to me is that it is not always the same amount of time for delay. Sometimes 20 minutes waiting is not enough, sometimes you can reconnect after 45 seconds...

The best solution to me is to have a REST command to force the closing of the streaming API (Note : unsubscribing to everything and closing listeners do NOT solve the problem). With an explicit REST command (with the correct CST- token) => problem solved. 

... maybe I'am wrong totally on the source of the error, I don't know ...

This problem arrived late july, and I had never seen it for a year or more before that !!!

Share this post


Link to post
  • 0

You are only allowed 10 sessions on the streaming API if I remember rightly. Check you are not going over that. 

 

How are you managing your connections in your code? Do they go down cleanly? 

Edited by TheGuru12

Share this post


Link to post
  • 0

No, I have a mail from the IG team => we are limited to one session at a time !
I tested and it is true, when my program is connected to streamAPI, I can't use the stream companion from IGlabs.
I joined a capture of the answer of the mail from IG team.

So I have :

- Only 1 software running at a time (only one session of streaming API used)
- the software is fully closed before relauching another one  with a minute before the disconnection and a new connection).
- before disconnecting from the stream API, I unsubscribe to everything (epics, account etc)
- I also disconnect from the REST API, after the stream API
- I respect all limitations given by IG on IGlabs site
- I don't use the streamAPI companion (only one time to confirm the 1 session limitation)
- I connect the REST API before reconnecting the streamAPI and I use the token of the new connection (I don't reuse the old one, of the connection which has been cut).
- I never experienced those problem before end july 2019, and the connection / disconnection system was not change for months before that

Considering all of that, I tried to explain the problem with a server side timeout. I think it is the simplier explanation, but not sure of it (of course). Maybe if some can get in touch with the dev team, we will have more clues on this problem...

NLP

contacts - Dossiers locaux - Mozilla Thunderbird.jpg

Share this post


Link to post
  • 0

I agree that this looks like a server side issue on the IG. I started seeing this behaviour at the end of August.

My java code is unsubscribing and disconnecting from lightstreamer and from my log-files this is successful.

I have put a retry around the lightstreamer openConnection method and wait for 30 secs.

The issue is easily reproducible and I can see successful connections after a couple of attempts with the modified code.

I suggest that IG fixes this rather than assuming users are breaching session limits. In my case I am definitely running one Java jar file that connects on a single thread for the api key I am using.

 

 

Share this post


Link to post
  • 0

Hi !

I did the same thing => a retry loop of connection if a failure is detected (40sec). It connects successfully after few attemps everytime.

I agree about the fix : it is on IG side, to detect a closed session faster or to provide a REST function that force the shutdown of a user session (in order to reconnect after few seconds).

Share this post


Link to post

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
You are posting as a guest. If you have an account, please sign in.
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×