|
hi everybody, i've a little program that that takes the chain of the options using the method reqContractDetailsEx (ActiveX). It worked fine till yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6 seconds of before yesterday. In this way the program is dramaticaly slow. Anyone experienced the same?
thanks
Enrico
|
My app, whenever it launches, requests contract details for a certain saved
set of contracts (not a chain). Some of them are obsolete and I have not
cleaned them up and for these I get the error 200 "No security definition
...". I am using the app for other things so did not pay attention to all
the details, but what shows up on my log are the error 200's and they are
now coming much slower than before. It appeared earlier that when launching
my app it took several minutes for it to finish all the error 200's and I
did not look into it further. It appeared at one point that a historical
data requests did not get a result back until the last contract details
request finished, but I am not sure about that.
So it did make me wonder whether IB started throttling contract details
requests but I have not looked into it since things I need are working for
me at the moment.
-Kurt
toggle quoted message
Show quoted text
On 7/11/13 1:07 AM, "dairen62" <no_reply@...> wrote: hi everybody, i've a little program that that takes the chain of the options
using the method reqContractDetailsEx (ActiveX). It worked fine till
yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6
seconds of before yesterday. In this way the program is dramaticaly slow.
Anyone experienced the same?
thanks
Enrico
|
Is this still a problem? I just ran a program at 8:25 EST on 11 JUL, and everything appears normal on Globex (E6).
[rwk]
--- dairen62 <no_reply@...> wrote:
toggle quoted message
Show quoted text
hi everybody, i've a little program that that takes the chain of the options using the method reqContractDetailsEx (ActiveX). It worked fine till yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6 seconds of before yesterday. In this way the program is dramaticaly slow. Anyone experienced the same?
|
Yes, when i try to take the options chain every call to reContractDetailsEx (with strike set to zero) lasts 1 minute instead the normal 6 seconds. I also notice that the demo program of the API (client3.exe) crash when you use "reqContractData". Can you try if you have the same problem?
thanks
toggle quoted message
Show quoted text
--- In TWSAPI@..., "rwk2095" <r@...> wrote:
Is this still a problem? I just ran a program at 8:25 EST on 11 JUL, and everything appears normal on Globex (E6).
[rwk]
--- dairen62 <no_reply@> wrote:
hi everybody, i've a little program that that takes the chain of the options using the method reqContractDetailsEx (ActiveX). It worked fine till yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6 seconds of before yesterday. In this way the program is dramaticaly slow. Anyone experienced the same?
|
I ran an app to retrieve the option chain for one expiry (201309 for CL), and it seems to work okay with edemo.
I tried client3.exe, and I get error 200: no contract, but it does not crash. This again was with edemo. The sample program is so hard to use, it may not be possible to get futures options info with it.
[rwk]
--- dairen62 <no_reply@...> wrote:
toggle quoted message
Show quoted text
Yes, when i try to take the options chain every call to reContractDetailsEx (with strike set to zero) lasts 1 minute instead the normal 6 seconds. I also notice that the demo program of the API (client3.exe) crash when you use "reqContractData". Can you try if you have the same problem?
thanks
--- In TWSAPI@..., "rwk2095" <r@...> wrote:
Is this still a problem? I just ran a program at 8:25 EST on 11 JUL, and everything appears normal on Globex (E6).
[rwk]
--- dairen62 <no_reply@> wrote:
hi everybody, i've a little program that that takes the chain of the options using the method reqContractDetailsEx (ActiveX). It worked fine till yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6 seconds of before yesterday. In this way the program is dramaticaly slow. Anyone experienced the same?
|
Hi, i experience same issues!
the first request answers quickly then a second after 1 minute
then nothing... :-(
I updated TWS and API to use latest stuff but even worse
with the <>clients.exe crash (previous API clients versions don't crash).
I'm going to log the issue to IB.
Regards
CH
toggle quoted message
Show quoted text
--- In TWSAPI@..., dairen62 <no_reply@...> wrote:
Yes, when i try to take the options chain every call to reContractDetailsEx (with strike set to zero) lasts 1 minute instead the normal 6 seconds. I also notice that the demo program of the API (client3.exe) crash when you use "reqContractData". Can you try if you have the same problem?
thanks
--- In TWSAPI@..., "rwk2095" <r@...> wrote:
Is this still a problem? I just ran a program at 8:25 EST on 11 JUL, and everything appears normal on Globex (E6).
[rwk]
--- dairen62 <no_reply@> wrote:
hi everybody, i've a little program that that takes the chain of the options using the method reqContractDetailsEx (ActiveX). It worked fine till yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6 seconds of before yesterday. In this way the program is dramaticaly slow. Anyone experienced the same?
|
just got an answer from IB API support. 1 minute issue should be solved in near future(when???) Unfortunately IB imposes limitations on the amount of contracts
that can be returned when invoking the reqContractDetails( ) method.
In this particular case it would be best to include additional
contract parameters which will narrow your scope.
Example if you include m_expiration and m_right then you can
determine all the available strikes for that particular expiration.
Alternatively if you include m_strike and m_right you can determine
all the available expirations.
But please note there are currently an issue that development is
working on with respect to Option Contracts. It seems even though
you include the m_expiry there still is a 1 minute buffer for
additional requests. Once this has been resolved I will provide
you a follow-up comment on this ticket with additional details, --- In TWSAPI@..., clove2hitch <no_reply@...> wrote:
Hi, i experience same issues!
the first request answers quickly then a second after 1 minute
then nothing... :-(
I updated TWS and API to use latest stuff but even worse
with the <>clients.exe crash (previous API clients versions don't crash).
I'm going to log the issue to IB.
Regards
CH
--- In TWSAPI@..., dairen62 <no_reply@> wrote:
Yes, when i try to take the options chain every call to reContractDetailsEx (with strike set to zero) lasts 1 minute instead the normal 6 seconds. I also notice that the demo program of the API (client3.exe) crash when you use "reqContractData". Can you try if you have the same problem?
thanks
--- In TWSAPI@..., "rwk2095" <r@...> wrote:
Is this still a problem? I just ran a program at 8:25 EST on 11 JUL, and everything appears normal on Globex (E6).
[rwk]
--- dairen62 <no_reply@> wrote:
hi everybody, i've a little program that that takes the chain of the options using the method reqContractDetailsEx (ActiveX). It worked fine till yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6 seconds of before yesterday. In this way the program is dramaticaly slow. Anyone experienced the same?
|
i received exactly the same answer... hope for a quick solution :)
toggle quoted message
Show quoted text
--- In TWSAPI@..., clove2hitch <no_reply@...> wrote:
just got an answer from IB API support.
1 minute issue should be solved in near future(when???)
Unfortunately IB imposes limitations on the amount of contracts
that can be returned when invoking the reqContractDetails( ) method.
In this particular case it would be best to include additional
contract parameters which will narrow your scope.
Example if you include m_expiration and m_right then you can
determine all the available strikes for that particular expiration.
Alternatively if you include m_strike and m_right you can determine
all the available expirations.
But please note there are currently an issue that development is
working on with respect to Option Contracts. It seems even though
you include the m_expiry there still is a 1 minute buffer for
additional requests. Once this has been resolved I will provide
you a follow-up comment on this ticket with additional details,
--- In TWSAPI@..., clove2hitch <no_reply@> wrote:
Hi, i experience same issues!
the first request answers quickly then a second after 1 minute
then nothing... :-(
I updated TWS and API to use latest stuff but even worse
with the <>clients.exe crash (previous API clients versions don't crash).
I'm going to log the issue to IB.
Regards
CH
--- In TWSAPI@..., dairen62 <no_reply@> wrote:
Yes, when i try to take the options chain every call to reContractDetailsEx (with strike set to zero) lasts 1 minute instead the normal 6 seconds. I also notice that the demo program of the API (client3.exe) crash when you use "reqContractData". Can you try if you have the same problem?
thanks
--- In TWSAPI@..., "rwk2095" <r@...> wrote:
Is this still a problem? I just ran a program at 8:25 EST on 11 JUL, and everything appears normal on Globex (E6).
[rwk]
--- dairen62 <no_reply@> wrote:
hi everybody, i've a little program that that takes the chain of the options using the method reqContractDetailsEx (ActiveX). It worked fine till yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6 seconds of before yesterday. In this way the program is dramaticaly slow. Anyone experienced the same?
|
Good news... the problem will be fixed on 7/18. We just need to include the full expiration in the format of YYYYMMDD when invoking the reqContractDeta ils( ) method.
toggle quoted message
Show quoted text
--- In TWSAPI@..., dairen62 <no_reply@...> wrote:
i received exactly the same answer... hope for a quick solution :)
--- In TWSAPI@..., clove2hitch <no_reply@> wrote:
just got an answer from IB API support.
1 minute issue should be solved in near future(when???)
Unfortunately IB imposes limitations on the amount of contracts
that can be returned when invoking the reqContractDetails( ) method.
In this particular case it would be best to include additional
contract parameters which will narrow your scope.
Example if you include m_expiration and m_right then you can
determine all the available strikes for that particular expiration.
Alternatively if you include m_strike and m_right you can determine
all the available expirations.
But please note there are currently an issue that development is
working on with respect to Option Contracts. It seems even though
you include the m_expiry there still is a 1 minute buffer for
additional requests. Once this has been resolved I will provide
you a follow-up comment on this ticket with additional details,
--- In TWSAPI@..., clove2hitch <no_reply@> wrote:
Hi, i experience same issues!
the first request answers quickly then a second after 1 minute
then nothing... :-(
I updated TWS and API to use latest stuff but even worse
with the <>clients.exe crash (previous API clients versions don't crash).
I'm going to log the issue to IB.
Regards
CH
--- In TWSAPI@..., dairen62 <no_reply@> wrote:
Yes, when i try to take the options chain every call to reContractDetailsEx (with strike set to zero) lasts 1 minute instead the normal 6 seconds. I also notice that the demo program of the API (client3.exe) crash when you use "reqContractData". Can you try if you have the same problem?
thanks
--- In TWSAPI@..., "rwk2095" <r@...> wrote:
Is this still a problem? I just ran a program at 8:25 EST on 11 JUL, and everything appears normal on Globex (E6).
[rwk]
--- dairen62 <no_reply@> wrote:
hi everybody, i've a little program that that takes the chain of the options using the method reqContractDetailsEx (ActiveX). It worked fine till yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6 seconds of before yesterday. In this way the program is dramaticaly slow. Anyone experienced the same?
|
This has indeed been fixed for live and paper trading accounts, but not for edemo
toggle quoted message
Show quoted text
--- In TWSAPI@..., dairen62 <no_reply@...> wrote:
Good news... the problem will be fixed on 7/18. We just need to include the full expiration in the format of YYYYMMDD when invoking the reqContractDeta ils( ) method.
--- In TWSAPI@..., dairen62 <no_reply@> wrote:
i received exactly the same answer... hope for a quick solution :)
--- In TWSAPI@..., clove2hitch <no_reply@> wrote:
just got an answer from IB API support.
1 minute issue should be solved in near future(when???)
Unfortunately IB imposes limitations on the amount of contracts
that can be returned when invoking the reqContractDetails( ) method.
In this particular case it would be best to include additional
contract parameters which will narrow your scope.
Example if you include m_expiration and m_right then you can
determine all the available strikes for that particular expiration.
Alternatively if you include m_strike and m_right you can determine
all the available expirations.
But please note there are currently an issue that development is
working on with respect to Option Contracts. It seems even though
you include the m_expiry there still is a 1 minute buffer for
additional requests. Once this has been resolved I will provide
you a follow-up comment on this ticket with additional details,
--- In TWSAPI@..., clove2hitch <no_reply@> wrote:
Hi, i experience same issues!
the first request answers quickly then a second after 1 minute
then nothing... :-(
I updated TWS and API to use latest stuff but even worse
with the <>clients.exe crash (previous API clients versions don't crash).
I'm going to log the issue to IB.
Regards
CH
--- In TWSAPI@..., dairen62 <no_reply@> wrote:
Yes, when i try to take the options chain every call to reContractDetailsEx (with strike set to zero) lasts 1 minute instead the normal 6 seconds. I also notice that the demo program of the API (client3.exe) crash when you use "reqContractData". Can you try if you have the same problem?
thanks
--- In TWSAPI@..., "rwk2095" <r@...> wrote:
Is this still a problem? I just ran a program at 8:25 EST on 11 JUL, and everything appears normal on Globex (E6).
[rwk]
--- dairen62 <no_reply@> wrote:
hi everybody, i've a little program that that takes the chain of the options using the method reqContractDetailsEx (ActiveX). It worked fine till yesterday: every call to reqContractDetailsEx lasts 1 minute versus the 6 seconds of before yesterday. In this way the program is dramaticaly slow. Anyone experienced the same?
|
It is 7/18, and I just noticed the recently slow contract details behavior
seems to have reverted back to what it was previously.
-Kurt
toggle quoted message
Show quoted text
On 7/15/13 6:31 AM, "dairen62" <no_reply@...> wrote: Good news... the problem will be fixed on 7/18. We just need to include the
full expiration in the format of YYYYMMDD when invoking the reqContractDeta
ils( ) method.
--- In TWSAPI@..., dairen62 <no_reply@...> wrote:
i received exactly the same answer... hope for a quick solution :)
--- In TWSAPI@..., clove2hitch <no_reply@> wrote:
just got an answer from IB API support.
1 minute issue should be solved in near future(when???)
Unfortunately IB imposes limitations on the amount of contracts
that can be returned when invoking the reqContractDetails( ) method.
In this particular case it would be best to include additional
contract parameters which will narrow your scope.
Example if you include m_expiration and m_right then you can
determine all the available strikes for that particular expiration.
Alternatively if you include m_strike and m_right you can determine
all the available expirations.
But please note there are currently an issue that development is
working on with respect to Option Contracts. It seems even though
you include the m_expiry there still is a 1 minute buffer for
additional requests. Once this has been resolved I will provide
you a follow-up comment on this ticket with additional details,
--- In TWSAPI@..., clove2hitch <no_reply@> wrote:
Hi, i experience same issues!
the first request answers quickly then a second after 1 minute
then nothing... :-(
I updated TWS and API to use latest stuff but even worse
with the <>clients.exe crash (previous API clients versions don't crash).
I'm going to log the issue to IB.
Regards
CH
--- In TWSAPI@..., dairen62 <no_reply@> wrote:
Yes, when i try to take the options chain every call to
reContractDetailsEx (with strike set to zero) lasts 1 minute instead the
normal 6 seconds. I also notice that the demo program of the API
(client3.exe) crash when you use "reqContractData". Can you try if you
have the same problem?
thanks
--- In TWSAPI@..., "rwk2095" <r@...> wrote:
Is this still a problem? I just ran a program at 8:25 EST on 11 JUL, and
everything appears normal on Globex (E6).
[rwk]
--- dairen62 <no_reply@> wrote:
hi everybody, i've a little program that that takes the chain of the
options using the method reqContractDetailsEx (ActiveX). It worked fine
till yesterday: every call to reqContractDetailsEx lasts 1 minute versus
the 6 seconds of before yesterday. In this way the program is
dramaticaly slow. Anyone experienced the same?
------------------------------------
Yahoo! Groups Links
|
