Force disconnecting a client connection inside IB gateway about ib-gateway-docker HOT 3 OPEN

Haven't had any similar trouble in this end with the freezing, but you should be able to run and attach to the container to see the log output, or do a volume mount to mount a local directory to the specified logging directory in the container.
I'm not aware of a way to force disconnect besides restarting the gateway container.

from ib-gateway-docker.

Yeah, I think the problem was that the client (which is the web api) losing the connection somehow but the other problem was that the IBG is not disconnecting the client. Once my web api started, a connection is established to IBG and I'd like to keep it open until I issue disconnect. If I leave the web api idle for few minutes the IB signal and reader are not working anymore (maybe a crash in the background thread), though I can still send the request to IBG. Because of this, IBG showing there's still an open client connection and I can't disconnect it, thus leaving it idle. And yes, there's no way but to restart IBG. Even if I shutdown the web api it didn't close the connection.

from ib-gateway-docker.

I've seen something similar to this, but where the gateway seems to not be getting updated values from IB, just returning the same account values to the client over and over. I'm not sure if they are related, and it likely isn't the host container, but I'm watching it. Proactive restarts of IB Gateway seem to be necessary at this point as well.

from ib-gateway-docker.