[ts-gen] May release

[Bill Pippin]

Nils,

About the Monday and Friday releases:

> upgrading from an 2009-04-27 to shim-090706, I am experiencing
> some new problems.

Thanks for your detailed problem reporting:

> More precisely, running some order scripts, I get segmentation
> faults, when reaching the submit stage.  Not always ...
> ... when I enter the commands provided in risk.rb manually into
> a shim session, I get the same segmentation faults as before.

Good, a reproducable problem, even if only via manual input ...

> ... I tried to increase all wait commands, but no success.

... Perhaps not success, yet predictable failure can be almost as
useful.  The wait command serves to make the problem consistently
reproducable via an automated script, which makes my life much easier.
Again, thanks for your careful testing and problem reporting.

To cut to the chase, I've pushed another tarball if you still wish to
continue checking for improvements/changes in journalling. Today's
release *undoes* recent work on memory allocation, so don't expect
to see reductions in memory use, but today's daily should not crash
in the way you observed with the tarballs from last week. 

Or, if you want to wait until the work I'm doing with memory
stabilizes, I'll keep the list posted on this work from one week
to the next, with the next message probably around this Friday.

> As a side effect, I get records in the table OrderStatus with
> status 'Submitted' set, which are actually not submitted - they
> stay as prepared line in the tws screen when the segmentation
> fault occurs during the submit command.

Interesting.  The shim merely records order status messages as they
arrive, and their content is purely the responsibility of the IB tws.
If this problem goes away once the shim stays up and running, fine.

Otherwise, and given that the OrderStatus journal record exactly
matches the text that came in on the wire, which you can check by
using the save option to capture message input to the binary file
log/tws2shim.bin, and using the bin/msg.filter script for rough
translation, then you need to let us know on the list.  For now,
however, first things first: I'll keep you posted on the work with
memory allocation, and you can try out today's release if you so
choose.

Thanks,

Bill