Old tale TWS freak when markets move.
- Thread starter NoMoreOptions
- Start date
.... our Sonic was flawless.....I was logged off this morning as well, (thats why having a pair of accounts/back-up is required if your doing this for a living)
04/02/04 09:26:30 1144.50 1144.25 1144.50 97702
04/02/04 09:26:30 1144.25 1144.25 1144.50 97703
04/02/04 09:26:30 1144.50 1144.25 1144.50 97710
04/02/04 09:33:19 1143.50 1143.50 1143.75 116056
04/02/04 09:33:19 1143.75 1143.50 1143.75 116058
04/02/04 09:33:20 1143.75 1143.50 1143.75 116134
04/02/04 09:33:20 1143.50 1143.50 1143.75 116191
04/02/04 09:33:20 1143.50 1143.50 1143.75 116208
04/02/04 09:26:30 1144.50 1144.25 1144.50 97702
04/02/04 09:26:30 1144.25 1144.25 1144.50 97703
04/02/04 09:26:30 1144.50 1144.25 1144.50 97710
04/02/04 09:33:19 1143.50 1143.50 1143.75 116056
04/02/04 09:33:19 1143.75 1143.50 1143.75 116058
04/02/04 09:33:20 1143.75 1143.50 1143.75 116134
04/02/04 09:33:20 1143.50 1143.50 1143.75 116191
04/02/04 09:33:20 1143.50 1143.50 1143.75 116208
Perfect description of it, SAME HERE.
Quote from axeman:
I missed out on two good trades this morning because IB
was bouncing up and down near the open.
Couldnt seem to stay connected.
Did not research to see if it was a network issue.
My Realtick was fast and fine during the screwup.
peace
axeman
Quote from NoMoreOptions:
There are always jerks running around to reply to a report of IB problems. "Nah, it aint' happen to me". "Myins perfect". "Whadya
talking about". Like woman.
If you want to take it that way, fine. But they're just responding to all the people that post disconnects every time they happen. Some might even have good intentions.
Now, to maybe add some value...
I've had two accounts connected continously today since 07:00 - one to gw4 and the other to gw5. One was collecting data, and I just confirmed there are no gaps. I was using the other one actively without problems during the 07:00-10:00 time frame that others had trouble.
For those of you that were disconnected/had trouble, do you know which gateway you were connected to? In the C:\Jts\log.txt file, what values are shown for the following?
Hmds Connman Host: ctgw1.ibllc.com
Hmds Farm:ushmds1
Perhaps those who did not have problems could also post their values.
There are always jerks running around to reply to a report of IB problems. "Nah, it aint' happen to me". "Myins perfect". "Whadya
talking about". Like woman.
If you want to take it that way, fine. But they're just responding to all the people that post disconnects every time they happen. Some might even have good intentions.
Now, to maybe add some value...
I've had two accounts connected continously today since 07:00 - one to gw4 and the other to gw5. One was collecting data, and I just confirmed there are no gaps. I was using the other one actively without problems during the 07:00-10:00 time frame that others had trouble.
For those of you that were disconnected/had trouble, do you know which gateway you were connected to? In the C:\Jts\log.txt file, what values are shown for the following?
Hmds Connman Host: ctgw1.ibllc.com
Hmds Farm:ushmds1
Perhaps those who did not have problems could also post their values.
I was lucky and only lost connection for one minute from 9:31 to 9:32 AM today.
IB's realiability has been getting worse the past few months. I don't think they are anywhere close to the five 9s (99.999% uptime) during market hours..
It might vary for different users because there are many servers. One group of customers might have a really bad experience if their server crashes or becomes overloaded.
99.999% uptime means less than 6 seconds downtime per month during market hours, or about 1 minute downtime per year.
99.99% uptime means less than 1 minute downtime per month during market hours, or about 10 minutes downtime per year.
99.9% would be 10 minutes of downtime per month during market hours, or about 100 minutes downtime per year.
My own experience of the past month has been about 20 minutes of downtime, much more if you count degraded operation e.g. lagged quotes, so I would rate the uptime between 99% and 99.9%
IB's realiability has been getting worse the past few months. I don't think they are anywhere close to the five 9s (99.999% uptime) during market hours..
It might vary for different users because there are many servers. One group of customers might have a really bad experience if their server crashes or becomes overloaded.
99.999% uptime means less than 6 seconds downtime per month during market hours, or about 1 minute downtime per year.
99.99% uptime means less than 1 minute downtime per month during market hours, or about 10 minutes downtime per year.
99.9% would be 10 minutes of downtime per month during market hours, or about 100 minutes downtime per year.
My own experience of the past month has been about 20 minutes of downtime, much more if you count degraded operation e.g. lagged quotes, so I would rate the uptime between 99% and 99.9%
alanm, I was/am connected to GW6 and was logged off for about 6-7 minutes with the glitch commencing at 9:26 (est)......IB's TWS has been operating flawlessy for me for the past 6 weeks (fwiw)
>>I've had two accounts connected continously today since 07:00 - one to gw4 and the other to gw5.
For those of you that were disconnected/had trouble, do you know which gateway you were connected to?
Perhaps those who did not have problems could also post their values.<<<
>>I've had two accounts connected continously today since 07:00 - one to gw4 and the other to gw5.
For those of you that were disconnected/had trouble, do you know which gateway you were connected to?
Perhaps those who did not have problems could also post their values.<<<
Problems started for me at:
09:43:52 JTS-Listener2: Unknown broken socket situation.
This persisted, looping like this:
10:00:12 JTS-Ping: It's time to reset the connection.
10:00:12 JTS-Ping: The socket has been declared broken
10:00:12 JTS-Ping: Writing page file
10:00:13 JTS-Ping: Closing socket
10:00:13 JTS-Ping: setting disconnect time to 1080917983
10:00:13 JTS-Listener24: Error while listening - java.net.SocketException: socket closed
10:00:13 JTS-Ping: nextConnectTime=1080917987 base=0 random=2 range=6
10:00:13 JTS-Ping: sleeping for 4
10:00:17 JTS-Ping: Connecting
10:00:17 JTS-Listener24: Broken socket is already disconnected
10:00:17 JTS-Login: Creating socket
10:00:17 JTS-Listener24: Terminating
10:00:17 JTS-Login: m_encryptCollision = true
10:00:17 JTS-Login: Local port=4502
10:00:17 JTS-Login: Peer=4001
10:00:17 JTS-Listener25: Starting listener
10:00:18 JTS-Listener25: loginSuccess
10:00:18 JTS-Listener25: Requesting prelogon msg
10:00:18 JTS-Listener25: Activating ping thread
10:00:54 JTS-Ping: It's time to reset the connection.
10:00:54 JTS-Ping: The socket has been declared broken
I exited TWS shortly after this, used with my other broker for awhile, and when I restarted TWS around 10 minutes later it was OK.
09:43:52 JTS-Listener2: Unknown broken socket situation.
This persisted, looping like this:
10:00:12 JTS-Ping: It's time to reset the connection.
10:00:12 JTS-Ping: The socket has been declared broken
10:00:12 JTS-Ping: Writing page file
10:00:13 JTS-Ping: Closing socket
10:00:13 JTS-Ping: setting disconnect time to 1080917983
10:00:13 JTS-Listener24: Error while listening - java.net.SocketException: socket closed
10:00:13 JTS-Ping: nextConnectTime=1080917987 base=0 random=2 range=6
10:00:13 JTS-Ping: sleeping for 4
10:00:17 JTS-Ping: Connecting
10:00:17 JTS-Listener24: Broken socket is already disconnected
10:00:17 JTS-Login: Creating socket
10:00:17 JTS-Listener24: Terminating
10:00:17 JTS-Login: m_encryptCollision = true
10:00:17 JTS-Login: Local port=4502
10:00:17 JTS-Login: Peer=4001
10:00:17 JTS-Listener25: Starting listener
10:00:18 JTS-Listener25: loginSuccess
10:00:18 JTS-Listener25: Requesting prelogon msg
10:00:18 JTS-Listener25: Activating ping thread
10:00:54 JTS-Ping: It's time to reset the connection.
10:00:54 JTS-Ping: The socket has been declared broken
I exited TWS shortly after this, used with my other broker for awhile, and when I restarted TWS around 10 minutes later it was OK.