[ts-gen] [Fwd: Re: cross session orders, client ids]

[pippin at owlriver.net]

Nils,

> ... appearently [PollTime] has no effect, the error shows up
immediatly.

Presumably you are talking about the 524 account data timeout error,
but I'd just like to be sure, since a lot happens during startup,
and diagnosis depens on where the shim stops.

If so, about the file log/tws2shim.bin:

> Apparently there is no log if the connection fails. Also, on the
> console which starts tws there is a message ...

21:08:14:690 JTS-EWriter24: [8:23:39:1:0:0:0:ERR] Unable write to socket
client{8} -

Clearly something is wrong with the IB tws; but that doesn't rule out
problems with the shim, and in fact it sounds like there is something
going wrong, I'm just not sure what.  Anyway, the "unable to write to
socket" message indicates a fatal blockage of some kind; not sure why
it's occurring, but once your problem is fixed, it will have gone away.

By the way, if the tws doesn't write to the shim, then the handshake
never happens, and you can't be seeing a 524 message; it must be
something else.  Now, for the case where it is a 524, and you don't
have any log information:

0.  Did you include the "save" option to the command line?  This
option causes the shim to open the files shim2tws.bin and
tws2shim.bin.

1.  Is there a directory "log" in the current working directory?  The
shim should have created one there if it did not already exist.  Or,
you may experiment with setting the LogFiles configuration variable
to a dot, by itself.

2.  Does this directory contain *anything* at all?  The shim should
create log files there, including the two bin files if the save
option was provided.  What about log/cmdinput.txt; is it there?

3.  Once given the *.bin files, does either have any bytes whatsoever?
If so, translations, via bin/req.filter and bin/msg.filter, would
be interesting; please consider posting them.

4.  Does the first part of bin/msg.filter include a handshake?

    43|
    20081217 17:31:45 EST|

Again, if not, you could not be seeing a 524 timeout.  What about
the next id message?  If that's the last, then yes, the account data
never arrived.

>                  ... if I cancel the API order(s), all connectivity
> problems disappear. ...

The shim may be confused by an order status message, or else perhaps
portfolio value.  Or else this could be some kind of tws problem; maybe
you'll find some tws feature is blocking the socket write, or the
account info data send.  Anyway, the binary save files will let us
diagnose what's going on.  Again, please consider posting them.

Thanks,

Bill