Interactive Brokers TWS API message code
Interactive Brokers TWS API message code: 507 (bad message length)
The error, as text you can copy
507- Kind
- TWS API message code
- Where you meet it
- In the TWS API, not in the Web API and not in an HTTP status
What does 507 (bad message length) mean on the Interactive Brokers API?
Listed by the vendor as "Bad Message Length (Java-only)". The page labels this Java only. An EOF exception was caught while reading from the socket. The vendor says this can occur on an attempt to connect with a client ID that is already in use, or if TWS is locked, closes, or breaks the connection.
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
How do I fix 507 (bad message length)?
The vendor's page says the client application should handle it and treat it as a sign that the socket connection is not valid. Connecting with a client ID that is not already in use avoids one of the listed causes.