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
  • General Statistics

    • Total Topics
    • Total Posts
    • Total Members
    • Most Online
      10/06/21 10:53

    Newest Member
    Joined 06/10/22 07:56
  • Posts

    • Shell is warning that its natural gas trading and refining divisions are under stress and will negatively affect the company's third quarter release on 27 October.    Jeremy Naylor | Writer, London | Publication date: Thursday 06 October 2022 Shell shares drop, steering FTSE 100 down There's been a hefty decline in Shell shares at the open today in the London markets. The London-listed FTSE 100 oil giant has seen its stock down almost 4% as a result of a profit warning that's come through today. The group warned that its third quarter (Q3) profits will be weakened by a sharp drop in refining margins and significantly weaker earnings from its natural gas trading unit. Shell share price chart Let's take a look at the share price chart because we have what is overall still a continuation of this up move here. Shell obviously benefits from a large amount of exposure to the energy sector, a sector which is showing enormous price gains. So we have seen this uplifting show along with the rest of the oil sector. But you can see if we look in here, this is a drop we've seen in today's session, with the stock, as I said, down almost 4% on the trading day today. And this stock is so big, it is also steering the FTSE into losses in the earlier part of the session today. Indicative refining margins have dropped to $15 a barrel in the quarter, compared with $28 a barrel in the previous three months. You can see a really big hit to the bottom line here from the refining numbers. We'll get some more details on October the 27th when the company comes through with earnings. You'll remember as well yesterday the Shell chief executive calling on the government to tax oil and gas companies more in order to protect the poorest people in society from soaring energy costs. That's not really anything to do with today's trade. That was yesterday. I mean in fact we saw Shell yesterday close at levels we've not seen since the 10th of June. And in fact, if you look at the continuation of this upward move here, if we get a break of the highs we saw back on the 9th of June, we're then trading at levels not seen in a couple of years or so. So, Shell on the way down in today's trade, the up move is in the long-term and is still in place, but the company warned about the outlook for earnings and also considering this idea that the CEO wanted oil companies to have more of a tax burden which could ultimately end up with a further indication of potential losses ahead.
    • Thank you for the explanation and quick reply 👍
    • Hi @Amur3001 We are sorry to hear that you are not satisfied with your opening or closing prices. Slippage occurs when a market moves suddenly during the few seconds between when an order was placed, and when it was executed by a broker or on an exchange. This most generally happens in fast moving, highly volatile markets which are susceptible to quick and unexpected turns in a specific trend. The price difference can be either positive or negative depending on the direction of the price movement, if you are going long or short, and whether you are opening or closing a position. You can minimize your exposure to slippage by trading during a market’s most active hours and by going for highly liquid markets, preferably those with low volatility. You can also use Use guaranteed stops and limits on your trades to help mitigate the effects of slippage. Here's a link which clearly defines Slippage and how to avoid it Thanks, OfentseIG  
  • Create New...