Yesterday, the standalone TWS wouldn't come up. I hadn't done an upgrade so something had changed at IB upstream. Lots of exception spew but basically the classloader can't find something. I grabed the latest vesion andI tried it on a number of workstations (ubuntu 8.10) but no luck. So, this is is a major screwup, not some wierd memory leak thing.
Interestingly, launching TWS from Java Web Start worked which was strange but was able to muddle through.
This morning there is a new version for download at IB. I figured they got hammered yesterday and fixed it... No such luck... same problem.
I'm also hearing the Mac version is having similar problems but haven't investigated.
IB has always been very scary when it comes to software. As most long time IB users know, there is virtually no client application testing and the underlying design is dismal. But IB is one of the few with a full API and have been able to survive what would normally be fatal in a competitive software market.
I've been building distributed system software for 20 years and have long been concerned that IB was gonna eventually tip over (turns out that testing is pretty important). I "think" IB may be unstable in many of their core systems as well (certainly data distribution) but it wouldn't be a stretch to assume execution management isn't much better.
An example from a few months ago: IB had unstable feeds for ES and some other CME products... they apologized profusely (typical) and it came down to a single computer that they couldn't get parts for and blamed a vendor.. blah blah.
System redundancy isn't bleeding edge and it "appears" as though they don't do that part either.
I suggest IB may be close to a meltdown. They're certainly due for some serious competition. Fortunately, it looks like reasonable alternatives are appearing.
-glenn
Interestingly, launching TWS from Java Web Start worked which was strange but was able to muddle through.
This morning there is a new version for download at IB. I figured they got hammered yesterday and fixed it... No such luck... same problem.
I'm also hearing the Mac version is having similar problems but haven't investigated.
IB has always been very scary when it comes to software. As most long time IB users know, there is virtually no client application testing and the underlying design is dismal. But IB is one of the few with a full API and have been able to survive what would normally be fatal in a competitive software market.
I've been building distributed system software for 20 years and have long been concerned that IB was gonna eventually tip over (turns out that testing is pretty important). I "think" IB may be unstable in many of their core systems as well (certainly data distribution) but it wouldn't be a stretch to assume execution management isn't much better.
An example from a few months ago: IB had unstable feeds for ES and some other CME products... they apologized profusely (typical) and it came down to a single computer that they couldn't get parts for and blamed a vendor.. blah blah.
System redundancy isn't bleeding edge and it "appears" as though they don't do that part either.
I suggest IB may be close to a meltdown. They're certainly due for some serious competition. Fortunately, it looks like reasonable alternatives are appearing.
-glenn
