Jump to content
  • 0

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



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 !


Link to comment

8 answers to this question

Recommended Posts

  • 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 !


Link to comment
  • 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?

Link to comment
  • 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 !!!

Link to comment
  • 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...


contacts - Dossiers locaux - Mozilla Thunderbird.jpg

Link to comment
  • 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.



Link to comment
  • 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).

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • Sainsburys full year earnings and Unilever’s first quarter trading update both say the same thing, UK consumers are in for higher prices. The war in Ukraine, supply chain issues and the effects of ongoing Covid all to blame.      
    • US Dollar (DXY) Daily Price and Analysis US Q1 GDP may stall the greenback’s advance. A 20-year high nears for the US dollar. The multi-month US dollar rally continues with the greenback printing a fresh high today ahead of the first look at US Q1 GDP at 12.30 GMT. The US dollar basket (DXY) has been boosted by renewed weakness in the Euro and the Japanese Yen, as investors move from lower-yielding to higher-yielding currencies, while safe-haven flows continue to benefit the greenback. The US growth release later in the session is expected to show a sharp slowdown from the robust Q4 figure of 6.9%. The markets are currently pricing in growth of just 1% for the first three months of this year, with the slowdown mainly due to a reduction in inventory accrual over the quarter. This release is unlikely to move the greenback, unless there is a large miss or beat, as the Fed believe that 2022 US growth will be robust enough to let them tighten monetary policy sharply without damaging the economy. The latest US Core PCE data – the Fed’s preferred inflation reading – is released on Friday and this may have more effect on the US dollar than today’s GDP data. For all market moving economic data and events, see the DailyFX Calendar. The ongoing US dollar rally has been aided by weakness across a range of G7 currencies including the Euro, the Japanese Yen, and the British Pound. The Euro continues to battle with lowly growth expectations, exacerbated by energy concerns, the British Pound is mired by weak economic data, while the Japanese Yen is in freefall as the BoJ continues with its ultra-loose monetary policy.   The US dollar continues to press higher and looks set to break above 103.96, the March 2020 high. Above here the US dollar would be back at levels last seen nearly two decades ago. The March resistance will likely hold in the short-term, especially with month-end portfolio rebalancing at the end of the week, but US dollar strength is set to continue in the months ahead. USDOLLAR (DXY) WEEKLY PRICE CHART – APRIL 28, 2022 {{THE_FUNDAMENTALS_OF_BREAKOUT_TRADING}} What is your view on the US Dollar – bullish or bearish?   Apr 28, 2022 | DailyFX Nick Cawley, Strategist
    • While Tesla has nothing directly to do with Elon Musk buying Twitter - TSLA stock closed down 12% on news that Musk may have to sell stock and use other holdings to stand against the loan to finalise the purchase of the social media giant.        
  • Create New...