IB disconnections
- Thread starter 0008
- Start date
I mean think about it, we are talking about 180ms, not even a quarter of a second. That's ridiculous. IB is the only broker I have been with that likes to pink out all the time and then blame it on everybody's connection. It's bs.
Hi everyone!
When you get a disconnect in TWS do you get this error message in the log file:
Error reading from socket gw1.ibllc.com:4000 - java.net.SocketException: No buffer space available (maximum connections reached?): recv failed?
I googled a possible solution to this problem and increased the maximum user ports in the Windows XP registry (maxuserport under tcpip) but I'm not certain it helped.
Sometimes when I start a new software that uses ports (e.g. a browser) it creates this error, sometimes not. Windows Live Messenger is one of those apps that instantly kills the TWS connection. Once I close Live Messenger it reconnects. It's a totally reproducible bug. I just don't know if it's a bug in TWS (a Java bug), in Windows XP or what
(I'm running SP3).
It would be helpful if some IB programmers would look into this.
When you get a disconnect in TWS do you get this error message in the log file:
Error reading from socket gw1.ibllc.com:4000 - java.net.SocketException: No buffer space available (maximum connections reached?): recv failed?
I googled a possible solution to this problem and increased the maximum user ports in the Windows XP registry (maxuserport under tcpip) but I'm not certain it helped.
Sometimes when I start a new software that uses ports (e.g. a browser) it creates this error, sometimes not. Windows Live Messenger is one of those apps that instantly kills the TWS connection. Once I close Live Messenger it reconnects. It's a totally reproducible bug. I just don't know if it's a bug in TWS (a Java bug), in Windows XP or what
(I'm running SP3).It would be helpful if some IB programmers would look into this.
I guess I am just one of those traders content with high-quality data updated five times per second. There is no human on earth who can respond five times every second to price changes. Even if it's .2 seconds late, the aggregate is fine, and my systems have no need to see every single duplicate tick or every single trade size, so long as the aggregate shows them. So, I see no problem with IB data. Their charts suck, but that is for a different thread.
Update to my previous post:
I tested the latest TWS (886) and Java (1.6.0_07) setup on another Windows XP machine and it runs flawlessly, no matter what other apps I use, so obviously the cause for the disconnects lies in my machine and not with IB.
I restored the Windows default settings, and right now it appears to help.
I still think that network connections in Java might be sensitive to changes in TCP/IP parameters. Maybe some Java programmers like to comment on this.
I tested the latest TWS (886) and Java (1.6.0_07) setup on another Windows XP machine and it runs flawlessly, no matter what other apps I use, so obviously the cause for the disconnects lies in my machine and not with IB.
I restored the Windows default settings, and right now it appears to help.
I still think that network connections in Java might be sensitive to changes in TCP/IP parameters. Maybe some Java programmers like to comment on this.
Are you actually waiting to hear from IB support? Are we taling about the same IB?
I suggest you switch to the JVM that IB supports. They are pretty clear on their web site that they support JVM 1.5 (they don't list JVM 1.6)
I'm on JVM 1.5 and generally TWS works fine. Everyone i know who've tried 1.6 end up switching back to 1.5 for a variety of reasons (connectivity, UI being messed up etc.)