I can telnet to this port and it opens up, so the Gateway is listening on the port.
This is likely your problem. TCP/IP socket connections that do not start the TWS API session conversation with a properly formatted "API\0" message or that send some other data. As you describe, TWS/IBGW will still accept additional TCP/IP connections, but an API session cannot start any longer until restart. Not sure whether that is by design or a side effect of the implementation.
Avoid any such TCP/IP connection requests from port scanners or port monitoring tools, or at least send a proper "API\0" message.
闯ü谤驳别苍
?
On Tue, Nov 19, 2024 at 10:57 AM, ?kos Maróy wrote:
Hi,
?
I found this interesting phenomenon today when trying to connect with a second client to a running TWS Gateway, that I'm getting a timeout error. At the same time, the gateway has an active connection running by a client, that still is operational and works. Of course the new connection is using a different client id than the existing one.
?
In all cases the connection is made to 127.0.0.1, to the same port 4002. I can telnet to this port and it opens up, so the Gateway is listening on the port. But a new client can't connect and gets a timeout.
?
What could cause this issue?
?
?
?kos
?
