Posted: Jun 16, 2014 @ 12:22 PM             Msg. 1 of 6

We request momentum bars (8) as follows:

OECAPI()->SubscribeBars_3(contract,dt.m_dt,OECAPICOM::SubscriptionType_MomentumBar,8,false);

After receiving these bars, we request the next batch:

OECAPI()->RequestBars_3(subscription->Contract,lastRecordTime.m_dt,it->second.m_DataRequestEnd.m_dt,OECAPICOM::SubscriptionType_MomentumBar,8,false);

We do this until we've received all the momentum bars the api will provide us (until OnBarsReceived receives a call back for the contract symbol with 0 bars in it).

When requesting GNGN4 momentum bars:
- At 200K bars, we get a System Error callback from oec
- "your loading limit of 36 has been reached"
- we continue receiving momentum bars, interleaved with this system error msg
- have now received 7 million momemtum bars for GNGN4
- the bars just keep trickling in

Question:
- What is this system loading limit? I can't find it in the documentation or how to use it. It does not show up as a property.
- Is this "system loading limit" on a per symbol basis?

I really just need to know as much as possible about how to access this "system loading limit'.

Also, GNGN4 is malfunctioning. It's market price today appears to oscillate between normal market price and 0.00. 7 million momentum 8 bars is alot in 10 days.

Thanks,

---

CHW
Edited by CWeber984 on Jun 16, 2014 at 14:28:11
Edited by CWeber984 on Jul 21, 2014 at 16:46:35

Posted: Jun 26, 2014 @ 11:31 AM             Msg. 2 of 6

Hello,

We have couple limitation parameters on our servers, some of them are user based and some are common parameters. Also there are request based parameters. We do not have limits by symbol basis.

You can always ask your limitation parameters at customer service

Regarding GNGN4 symbol: our uplink data provider had a temporary issue on small amount of symbols. Now it should work well.

Thanks.

---

Vitaliy Pfau

Posted: Jul 21, 2014 @ 04:44 PM             Msg. 3 of 6

Hi Vitaly,

Thanks for responding to this post. We have two users who report this issue to us when it occurs for them. One of them reported in today with the error that his loading limit has been reached.

I asked him which charts he had open. When I tested getting the history for his charts, I didn't experience the error. I asked him to reopen those charts. When he did so, he didn't experience the error again either.

This supports the idea that the uplink data provider may have had an issue with one of more of this customer's symbols (of charts he was opening).

We're still wondering exactly what this message is about. Does it mean I can request history 36 times?

Finally, and most importantly, what is the name of the limitation parameter that gives the "loading limit of 36 has been reached" error so that we can request upping the limit when we need to?

Tx,

---

CHW

Posted: Jul 21, 2014 @ 06:16 PM             Msg. 4 of 6

Hi Chris,

Here is how we restrict subscriptions\loading requests.
A user has limitations:
MaxBars, MaxTicks, MaxDoms, MaxQuotes and some other specific restrictions.

MaxBar = 5 means you can subscribe 5 charts. Also you can send MaxBar + MaxLoadRequest load requests. MaxLoadRequest is a server specific parameter and it is equal 16 for DEV server for current moment.

Example: your user has MaxBars=5 and MaxLoadRequest=16. Then you subscribed 3 charts. That moment you can send 5+16-3 = 18 simultaneous historical bar based data request. If you try to send 19 load requests you'll get "loading limit of 21 has been reached" message.

We decrement loading counter on each final loading message.

---

Vitaliy Pfau

Posted: Jul 22, 2014 @ 01:28 AM             Msg. 5 of 6

Vitaly and Chris M.,

This info is exactly what we needed.

Thanks,

---

CHW

Posted: Jul 22, 2014 @ 09:12 AM             Msg. 6 of 6

One more thing: the message "Your loading\subscription limit of N has been reached" has being sent once per 3 seconds per type limitation.

---

Vitaliy Pfau