Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tws.eDisconnect() no worky? #51

Open
cmorgan opened this issue Dec 20, 2016 · 2 comments
Open

tws.eDisconnect() no worky? #51

cmorgan opened this issue Dec 20, 2016 · 2 comments

Comments

@cmorgan
Copy link

cmorgan commented Dec 20, 2016

Hi,
Are you aware of lack of proper disconnect for a a clientId?
By which i mean that when calling tws.eDisconnect(), and then trying to reconnect i get a client connected error.
Seems only the python process ending will do, or did i miss something?

@dbivolaru
Copy link

Try this when closing:

tws.reqOpenOrders()
tws.eDisconnect()

@cmorgan
Copy link
Author

cmorgan commented Jan 6, 2017

Hi @dbivolaru, thanks for the reply.
I will try what you suggest, but why would i expect

tws.reqOpenOrders()
tws.eDisconnect()

to work as successful in killing the connection vs

tws.eDisconnect()

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants