quickfix-developers — QuickFIX developers forum

RE: [Quickfix-developers] out of sequence messages

[Vijay S. Y. <vy...@op...>]

T3JlbiwNCiBUaGFua3MgZm9yIHJlcGx5aW5nLiBJIGFtIG5vdCBzdXJlLiBJIGFtIG5ldyB0byBR
dWlja0ZpeC4gQ291bGQgdGhlIGZhY3QgdGhhdCBhcHBsaWNhdGlvbiBjbGFzcyBhbmQgaW5pdGlh
dG9yIGFyZSBpbml0aWF0ZWQgaW4gdGhlIG1haW4gdGhyZWFkIGFuZCBhIHdvcmtlciB0aHJlYWQg
cHVsbHMgb3JkZXJzIGZyb20gdGhlIGRhdGFiYXNlIGFuZCBzZW5kcyBpdCB0byB0aGUgRklYIGVu
Z2luZSBoYXZlIGFueXRoaW5nIHRvIGRvIHdpdGggdGhlIHByb2JsZW0uIA0KIA0KLS0gdmlqYXkN
Cg0KCS0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tIA0KCUZyb206IE9yZW4gTWlsbGVyIFttYWls
dG86b3Jlbm1uZXJvQHlhaG9vLmNvbV0gDQoJU2VudDogVGh1IDMvMTgvMjAwNCA4OjI1IEFNIA0K
CVRvOiBWaWpheSBTaW5naCBZYWRhdjsgcXVpY2tmaXgtZGV2ZWxvcGVyc0BsaXN0cy5zb3VyY2Vm
b3JnZS5uZXQgDQoJQ2M6IA0KCVN1YmplY3Q6IFJlOiBbUXVpY2tmaXgtZGV2ZWxvcGVyc10gb3V0
IG9mIHNlcXVlbmNlIG1lc3NhZ2VzDQoJDQoJDQoNCglBbnkgaWRlYSB3aHkgdHdvIGxvZ29uIG1l
c3NhZ2VzIGFyZSBiZWluZyBzZW50Pw0KCQ0KCS0tLSBWaWpheSBTaW5naCBZYWRhdiA8dnlhZGF2
QG9wdGlvbnNtYXJrZXRtYWtpbmcuY29tPg0KCXdyb3RlOg0KCT4gSGVsbG8gQWxsLA0KCT4gIEkg
YW0gd3JpdGluZyBhbiBvcmRlciByb3V0aW5nIGdhdGV3YXkgdGhhdCBjb2xsZWN0cw0KCT4gb3Jk
ZXJzIGZyb20gdmFyaW91cyBjbGllbnRzIGFuZCBzZW5kcyB0aGVtIHRvIGEgRklYDQoJPiBhY2Nl
cHRvciBpLmUuIEkgYW0gdXNpbmcgdGhlIFF1aWNrRml4IGluaXRpYXRvciBpbg0KCT4gbXkgY29k
ZS4gVGhlIGluaXRpYXRvciBzZW5kcyBtZXNzYWdlcyB0byB0aGUNCgk+IGFjY2VwdG9yIG91dCBv
ZiBzZXF1ZW5jZS4gVGhpcyBsZWFkcyB0byBzZXNzaW9uDQoJPiB0ZXJtaW5hdGlvbiBhbmQgaW5j
b3JyZWN0IHByb2Nlc3NpbmcuIEFueSBpZGVhcyBhcmUNCgk+IHdlbGNvbWUgYW5kIGFwcHJlY2lh
dGVkLg0KCT4gDQoJPiBUaGFua3MsDQoJPiANCgk+IC0tIFZpamF5DQoJPiANCgk+DQoJOD1GSVgu
NC4xATk9NTkBMzU9QQEzND0xATQ5PU1FSEkBNTI9MjAwNDAzMTYtMTQ6MTI6MDYBNTY9T0NPTgE5
OD0wATEwOD0zMAExMD0xMzEBDQoJPg0KCT4NCgk4PUZJWC40LjEBOT00NwEzNT0wATM0PTIBNDk9
TUVISQE1Mj0yMDA0MDMxNi0xNDoxMjozOAE1Nj1PQ09OATEwPTA5MgENCgk+DQoJPg0KCTg9RklY
LjQuMQE5PTkzATM1PUQBMzQ9MwE0OT1NRUhJATUyPTIwMDQwMzE2LTE0OjEyOjUyATU2PU9DT04B
MT1NUU9UATExPTMBMjE9MQEzOD0xMDABNDA9MQE1ND0BNTU9TVNGVAE1OT0wATEwPTA1MwENCgk+
DQoJPg0KCTg9RklYLjQuMQE5PTU5ATM1PUEBMzQ9NQE0OT1NRUhJATUyPTIwMDQwMzE2LTE0OjE0
OjE4ATU2PU9DT04BOTg9MAExMDg9MzABMTA9MTQwAQ0KCT4NCgk+DQoJOD1GSVguNC4xATk9OTEB
MzU9RAEzND02ATQ5PU1FSEkBNTI9MjAwNDAzMTYtMTQ6MTQ6MzgBNTY9T0NPTgExPU1RT1QBMTE9
NQEyMT0xATM4PTEBNDA9MQE1ND0BATU1PVNQWAE1OT0wATEwPTE2MAENCgk+DQoJPg0KCTg9RklY
LjQuMQE5PTEyMAEzNT1EATM0PTMBNDM9WQE0OT1NRUhJATUyPTIwMDQwMzE2LTE0OjE0OjQyATU2
PU9DT04BMTIyPTIwMDQwMzE2LTE0OjEyOjUyATE9TVFPVAExMT0zATIxPTEBMzg9MTAwATQwPTEB
NTQ9ATU1PU1TRlQBNTk9MAExMD0xNDIBDQoJPg0KCT4NCgk4PUZJWC40LjEBOT05MgEzNT1EATM0
PTcBNDk9TUVISQE1Mj0yMDA0MDMxNi0xNDoxNDo0MgE1Nj1PQ09OATE9TVFPVAExMT02ATIxPTEB
Mzg9MTIBNDA9MQE1ND0BATU1PVNQWAE1OT0wATEwPTIwOAENCgk+DQoJPg0KCTg9RklYLjQuMQE5
PTYwATM1PUEBMzQ9MTABNDk9TUVISQE1Mj0yMDA0MDMxNi0xNDoxNDo1MQE1Nj1PQ09OATk4PTAB
MTA4PTMwATEwPTE3MwENCgk+IA0KCT4gQXMgeW91IGNhbiBzZWUgc2VxdWVuY2UgbnVtYmVycyAx
LTMgd2VyZSBzZW50IGluDQoJPiBvcmRlci4gU2VxdWVuY2UgbnVtYmVyIDQgaXMgbWlzc2luZyBh
bmQgc2VxdWVuY2UNCgk+IG51bWJlciAzIGlzIHJlc2VudCBhZnRlciBzZXF1ZW5jZSA2LiBTZXF1
ZW5jZSA4IGFuZA0KCT4gOSBhcmUgbWlzc2luZy4NCgk+IA0KCT4gSSBhbSBwYXNpbmcgQyMgY29k
ZSBiZWxvdyAoSSBoYXZlIHN0cmlwcGVkIG9mZiB0aGUNCgk+IHRyeS9jYXRjaCBibG9ja3MgZm9y
IGJyZXZpdHkncyBzYWtlKQ0KCT4gDQoJPiBuYW1lc3BhY2UgSU1UQ19GSVhJbml0aWF0b3INCgk+
IHsNCgk+ICBjbGFzcyBFeGVjdXRvcg0KCT4gIHsNCgk+ICAgcHJpdmF0ZSBTb2NrZXRJbml0aWF0
b3IgbV9pbml0aWF0b3I7DQoJPiAgIHByaXZhdGUgVGhyZWFkIFdvcmtlclRocmVhZDsNCgk+ICAg
cHVibGljIEV4ZWN1dG9yKCkNCgk+ICAgew0KCT4gICB9DQoJPiAgIHB1YmxpYyB2b2lkIEdvKCkN
Cgk+ICAgew0KCT4gICAgIFNlc3Npb25TZXR0aW5ncyBzZXR0aW5ncyA9IG5ldw0KCT4gU2Vzc2lv
blNldHRpbmdzKCJPQ09OTkVSLkNGRyIpOw0KCT4gICAgIEFwcGxpY2F0aW9uIGFwcGxpY2F0aW9u
ID0gbmV3IEFwcGxpY2F0aW9uKCk7DQoJPiAgICAgRmlsZVN0b3JlRmFjdG9yeSBmYWN0b3J5ID0g
bmV3DQoJPiBGaWxlU3RvcmVGYWN0b3J5KHNldHRpbmdzKTsNCgk+ICAgICBGaWxlTG9nRmFjdG9y
eSBsb2dGYWN0b3J5ID0gbmV3DQoJPiBGaWxlTG9nRmFjdG9yeSgib3V0cHV0Iik7DQoJPiAgICAg
TWVzc2FnZUZhY3RvcnkgbWVzc2FnZUZhY3RvcnkgPSBuZXcNCgk+IERlZmF1bHRNZXNzYWdlRmFj
dG9yeSgpOw0KCT4gICAgIG1faW5pdGlhdG9yID0gbmV3IFNvY2tldEluaXRpYXRvciAoYXBwbGlj
YXRpb24sDQoJPiAgICAgICAgICAgICAgICAgZmFjdG9yeSwNCgk+ICAgICAgICAgICAgICAgICBz
ZXR0aW5ncywNCgk+ICAgICAgICAgICAgICAgICBsb2dGYWN0b3J5LA0KCT4gICAgICAgICAgICAg
ICAgIG1lc3NhZ2VGYWN0b3J5KTsNCgk+ICAgICBtX2luaXRpYXRvci5zdGFydCgpOw0KCT4gICAg
IENvbnNvbGUuV3JpdGVMaW5lICgiSW5pdGlhdG9yIHN0YXJ0ZWQiKTsNCgk+ICAgICB3aGlsZSAo
IWFwcGxpY2F0aW9uLklzQ29ubmVjdGVkKCkpDQoJPiAgICAgew0KCT4gICAgICBDb25zb2xlLldy
aXRlTGluZSAoIldhaXRpbmcgdG8gZXN0YWJsaXNoIGENCgk+IGNvbm5lY3Rpb24gd2l0aCBGSVgg
c2VydmVyIik7DQoJPiAgICAgIFRocmVhZC5TbGVlcCgxMDApOw0KCT4gICAgIH0NCgk+ICAgICBQ
cm9jZXNzT3JkZXJzKCk7DQoJPg0KCT4gICB9DQoJPiAgIHB1YmxpYyB2b2lkIFN0b3AoKSB7bV9p
bml0aWF0b3Iuc3RvcCgpO30NCgk+ICAgcHJpdmF0ZSB2b2lkIFByb2Nlc3NPcmRlcnMoKQ0KCT4g
ICB7DQoJPiAgICBTcWxDb25uZWN0aW9uIENvbm49bmV3IFNxbENvbm5lY3Rpb24oKTsNCgk+ICAg
IENvbm4uQ29ubmVjdGlvblN0cmluZz0iRGF0YSBTb3VyY2U9MTAuNjAuMC4xMDQ7DQoJPiBJbnRl
Z3JhdGVkIFNlY3VyaXR5PVNTUEk7IiArDQoJPiAgICAgIkluaXRpYWwgQ2F0YWxvZz1pbXQ7IHVp
ZD1zYTtwd2Q9O0Nvbm5lY3QNCgk+IFRpbWVvdXQ9NSI7DQoJPiAgICAgICANCgk+ICAgIFNxbENv
bW1hbmQgbXlDTUQ9bmV3IFNxbENvbW1hbmQoKTsNCgk+ICAgIG15Q01ELkNvbW1hbmRUeXBlPUNv
bW1hbmRUeXBlLlN0b3JlZFByb2NlZHVyZTsNCgk+ICAgIG15Q01ELkNvbW1hbmRUZXh0PSJHZXRP
cmRlcnMiOw0KCT4gICAgbXlDTUQuQ29ubmVjdGlvbj1Db25uOw0KCT4gIA0KCT4NCglteUNNRC5Q
YXJhbWV0ZXJzLkFkZCgiQGNPcmRlclN0YXR1cyIsU3FsRGJUeXBlLkNoYXIsMSkuVmFsdWU9J04n
Ow0KCT4gICANCgk+ICAgIFNxbERhdGFBZGFwdGVyIGRhOw0KCT4gICAgZGE9bmV3IFNxbERhdGFB
ZGFwdGVyKCk7DQoJPiAgICBkYS5TZWxlY3RDb21tYW5kPW15Q01EOw0KCT4gICAgRGF0YVNldCBk
cz1uZXcgRGF0YVNldCgpOw0KCT4gICAgQ29ubi5PcGVuKCk7DQoJPiAgICB3aGlsZSh0cnVlKQ0K
CT4gICAgew0KCT4gICAgICBkYS5GaWxsKGRzKTsNCgk+ICAgICAgQ29ubi5DbG9zZSgpOw0KCT4g
ICAgDQoJPg0KCURhdGFSb3dbXWN1cnJSb3dzPWRzLlRhYmxlc1swXS5TZWxlY3QobnVsbCxudWxs
LERhdGFWaWV3Um93U3RhdGUuQ3VycmVudFJvd3MpOw0KCT4gICAgICBmb3JlYWNoKERhdGFSb3cg
bXlSb3cgaW4gY3VyclJvd3MpDQoJPiAgICAgew0KCT4gICAgICAgQ29uc29sZS5Xcml0ZUxpbmUo
IlN1Ym1pdHRpbmcgb3JkZXIgd2l0aA0KCT4gY2xpZW50IG9yZGVyIGlkID0gIitteVJvd1sib3Jk
ZXJpZCJdKTsNCgk+ICAgICAgIFNlbmRPcmRlcihDb252ZXJ0LlRvSW50MzIobXlSb3dbIm9yZGVy
aWQiXSksDQoJPiAgICAgICAgQ29udmVydC5Ub1N0cmluZyhteVJvd1sic3ltYm9sIl0pLA0KCT4g
ICAgICAgIENvbnZlcnQuVG9DaGFyKG15Um93WyJvcmRlcnNpZGUiXSksDQoJPiAgICAgICAgQ29u
dmVydC5Ub0ludDMyKG15Um93WyJxdHkiXSkpOw0KCT4gICAgIH0NCgk+ICAgICBDb25zb2xlLldy
aXRlKCJObyBuZXcgb3JkZXJzIHRvIGJlIHN1Ym1pdHRlZCIpOw0KCT4gICAgIA0KCT4gICAgfQ0K
CT4gICB9DQoJPiAgDQoJPiAgIA0KCT4gIA0KCT4gICBwdWJsaWMgdm9pZCBTZW5kT3JkZXIoaW50
IG9pZCxzdHJpbmcgb3N5bSxjaGFyDQoJPiBvc2QsaW50IG9xdHkpDQoJPiAgIHsNCgk+ICAgIE1l
c3NhZ2Ugb3JkZXI7DQoJPiAgICBTaWRlIHNpZGU7DQoJPiAgICBDbE9yZElEIGlkPW5ldyBDbE9y
ZElEKG9pZC5Ub1N0cmluZygpKTsNCgk+ICAgIEhhbmRsSW5zdCBpbnN0PW5ldw0KCT4NCglIYW5k
bEluc3QoSGFuZGxJbnN0LkFVVE9NQVRFRF9FWEVDVVRJT05fT1JERVJfUFJJVkFURSk7DQoJPiAg
ICBTeW1ib2wgc3ltPW5ldyBTeW1ib2wob3N5bSk7DQoJPiAgICBTaWRlIHNkPW5ldyBTaWRlKG9z
ZCk7DQoJPiAgICBPcmRUeXBlIG90eXA9bmV3IE9yZFR5cGUoT3JkVHlwZS5NQVJLRVQpOw0KCT4g
ICAgUXVpY2tGaXg0MS5OZXdPcmRlclNpbmdsZSBuZXdPcmRlclNpbmdsZT1uZXcNCgk+IFF1aWNr
Rml4NDEuTmV3T3JkZXJTaW5nbGUoaWQsaW5zdCxzeW0sc2Qsb3R5cCk7DQoJPiAgIA0KCT4gICAg
bmV3T3JkZXJTaW5nbGUuc2V0KG5ldyBBY2NvdW50KCJNUU9UIikpOw0KCT4gICAgbmV3T3JkZXJT
aW5nbGUuc2V0KG5ldyBPcmRlclF0eShvcXR5KSk7DQoJPiAgICBuZXdPcmRlclNpbmdsZS5zZXQo
bmV3DQoJPiBUaW1lSW5Gb3JjZShUaW1lSW5Gb3JjZS5EQVkpKTsNCgk+ICAgIG5ld09yZGVyU2lu
Z2xlLmdldEhlYWRlcigpLnNldEZpZWxkKG5ldw0KCT4gU2VuZGVyQ29tcElEKCJNRUhJIikpOw0K
CT4gICAgbmV3T3JkZXJTaW5nbGUuZ2V0SGVhZGVyKCkuc2V0RmllbGQobmV3DQoJPiBUYXJnZXRD
b21wSUQoIk9DT04iKSk7DQoJPiAgDQoJPiAgICBvcmRlciA9IG5ld09yZGVyU2luZ2xlOw0KCT4g
ICAgU2Vzc2lvbi5zZW5kVG9UYXJnZXQob3JkZXIpOw0KCT4gICB9DQoJPiAgfQ0KCT4gfQ0KCT4N
Cgk+IA0KCT4NCglOGMKsSFNewrXDqcWhxaBYwqzCssWhJ8KyxaDDnnXCvMuGBMOCw6LFvsOsU8K6
w5or4oCwwqlsFsK3xb4uKcOuw4bDm8KtwqLCuMWh4oCTxaHDnsKxw6nDrXnDlsOyDQoJwqnDonpU
aG3CuMKnwrDDusOewrInXsW+w5bCp3QhDsKhw7HFvsKdOijCtcOnIcW+4oCwaOKAmifCrC3DpsKr
wp3Dq8Oewq8rYcWgeB/CruKAsMW4wrp3WuKEosOpw61qWy3CosOMwqzCtcOpxaF2aMKnxaDDi2tq
w5jCqMW+G23Cp8O/w5p2w4osdnco4oC6w7bCneKAsMO1w6PCvRrigJNaHOKAsMO3w6t/KMKnJeKA
sMOJEMK6JyR+LF16w7fCpcKi4oCUwqvCsmbCouKAkynDoOKAkystQsOoxZPigJjDuMKxdcOrw57i
gJPFoF7CrsOJYsKyw5sswqLDqsOcecO6K8KBw6nDnsK2G23CpsOPw7/igJMrLcKyw4ouwq3Dh8W4
wqLCuB7CncOrf+KAkystwrPDuWLCssOYwqd+wo/DqsK6JyR+LF16w7fCpcKi4oCUwqsNCgkNCgkN
CglfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoJRG8geW91IFlhaG9vIT8NCglZ
YWhvbyEgTWFpbCAtIE1vcmUgcmVsaWFibGUsIG1vcmUgc3RvcmFnZSwgbGVzcyBzcGFtDQoJaHR0
cDovL21haWwueWFob28uY29tDQoJDQoNCg==

Re: [Quickfix-developers] out of sequence messages

[Oren M. <ore...@ya...>]

Any idea why two logon messages are being sent?

--- Vijay Singh Yadav <vy...@op...>
wrote:
> Hello All,
>  I am writing an order routing gateway that collects
> orders from various clients and sends them to a FIX
> acceptor i.e. I am using the QuickFix initiator in
> my code. The initiator sends messages to the
> acceptor out of sequence. This leads to session
> termination and incorrect processing. Any ideas are
> welcome and appreciated.
>  
> Thanks,
>  
> -- Vijay
>  
>
8=FIX.4.1
9=59
35=A
34=1
49=MEHI
52=20040316-14:12:06
56=OCON
98=0
108=30
10=131

> 
>
8=FIX.4.1
9=47
35=0
34=2
49=MEHI
52=20040316-14:12:38
56=OCON
10=092

> 
>
8=FIX.4.1
9=93
35=D
34=3
49=MEHI
52=20040316-14:12:52
56=OCON
1=MQOT
11=3
21=1
38=100
40=1
54=
55=MSFT
59=0
10=053

> 
>
8=FIX.4.1
9=59
35=A
34=5
49=MEHI
52=20040316-14:14:18
56=OCON
98=0
108=30
10=140

> 
>
8=FIX.4.1
9=91
35=D
34=6
49=MEHI
52=20040316-14:14:38
56=OCON
1=MQOT
11=5
21=1
38=1
40=1
54=

55=SPX
59=0
10=160

> 
>
8=FIX.4.1
9=120
35=D
34=3
43=Y
49=MEHI
52=20040316-14:14:42
56=OCON
122=20040316-14:12:52
1=MQOT
11=3
21=1
38=100
40=1
54=
55=MSFT
59=0
10=142

> 
>
8=FIX.4.1
9=92
35=D
34=7
49=MEHI
52=20040316-14:14:42
56=OCON
1=MQOT
11=6
21=1
38=12
40=1
54=

55=SPX
59=0
10=208

> 
>
8=FIX.4.1
9=60
35=A
34=10
49=MEHI
52=20040316-14:14:51
56=OCON
98=0
108=30
10=173

>  
> As you can see sequence numbers 1-3 were sent in
> order. Sequence number 4 is missing and sequence
> number 3 is resent after sequence 6. Sequence 8 and
> 9 are missing.
>  
> I am pasing C# code below (I have stripped off the
> try/catch blocks for brevity's sake)
>  
> namespace IMTC_FIXInitiator
> {
>  class Executor
>  {
>   private SocketInitiator m_initiator;
>   private Thread WorkerThread;
>   public Executor()
>   {
>   }
>   public void Go()
>   {
>     SessionSettings settings = new
> SessionSettings("OCONNER.CFG");
>     Application application = new Application();
>     FileStoreFactory factory = new
> FileStoreFactory(settings);
>     FileLogFactory logFactory = new
> FileLogFactory("output");
>     MessageFactory messageFactory = new
> DefaultMessageFactory();
>     m_initiator = new SocketInitiator (application,
>                 factory, 
>                 settings,
>                 logFactory,
>                 messageFactory);
>     m_initiator.start();
>     Console.WriteLine ("Initiator started");
>     while (!application.IsConnected())
>     {
>      Console.WriteLine ("Waiting to establish a
> connection with FIX server");
>      Thread.Sleep(100);
>     }
>     ProcessOrders();
> 
>   }
>   public void Stop() {m_initiator.stop();}
>   private void ProcessOrders()
>   {
>    SqlConnection Conn=new SqlConnection();
>    Conn.ConnectionString="Data Source=10.60.0.104;
> Integrated Security=SSPI;" +
>     "Initial Catalog=imt; uid=sa;pwd=;Connect
> Timeout=5";
>        
>    SqlCommand myCMD=new SqlCommand();
>    myCMD.CommandType=CommandType.StoredProcedure;
>    myCMD.CommandText="GetOrders"; 
>    myCMD.Connection=Conn;
>   
>
myCMD.Parameters.Add("@cOrderStatus",SqlDbType.Char,1).Value='N';
>    
>    SqlDataAdapter da;
>    da=new SqlDataAdapter();
>    da.SelectCommand=myCMD;
>    DataSet ds=new DataSet();
>    Conn.Open();
>    while(true)
>    {
>      da.Fill(ds);
>      Conn.Close();
>     
>
DataRow[]currRows=ds.Tables[0].Select(null,null,DataViewRowState.CurrentRows);
>      foreach(DataRow myRow in currRows)
>     {
>       Console.WriteLine("Submitting order with
> client order id = "+myRow["orderid"]);
>       SendOrder(Convert.ToInt32(myRow["orderid"]),
>        Convert.ToString(myRow["symbol"]),
>        Convert.ToChar(myRow["orderside"]),
>        Convert.ToInt32(myRow["qty"]));
>     }
>     Console.Write("No new orders to be submitted");
>      
>    }
>   }
>   
>    
>   
>   public void SendOrder(int oid,string osym,char
> osd,int oqty)
>   {
>    Message order;
>    Side side;
>    ClOrdID id=new ClOrdID(oid.ToString());
>    HandlInst inst=new
>
HandlInst(HandlInst.AUTOMATED_EXECUTION_ORDER_PRIVATE);
>    Symbol sym=new Symbol(osym);
>    Side sd=new Side(osd);
>    OrdType otyp=new OrdType(OrdType.MARKET);
>    QuickFix41.NewOrderSingle newOrderSingle=new
> QuickFix41.NewOrderSingle(id,inst,sym,sd,otyp);
>    
>    newOrderSingle.set(new Account("MQOT"));
>    newOrderSingle.set(new OrderQty(oqty));
>    newOrderSingle.set(new
> TimeInForce(TimeInForce.DAY));
>    newOrderSingle.getHeader().setField(new
> SenderCompID("MEHI"));
>    newOrderSingle.getHeader().setField(new
> TargetCompID("OCON"));
>   
>    order = newOrderSingle;
>    Session.sendToTarget(order);
>   }
>  }
> }
> 
>  
>
N¬HS^µéšŠX¬²š'²ŠÞu¼ˆÂâžìSºÚ+‰©l·ž.)îÆÛ­¢¸š–šÞ±éíyÖò
©âzThm¸§°úÞ²'^žÖ§t!¡ñž:(µç!ž‰h‚'¬-櫝ëÞ¯+aŠx®‰ŸºwZ™éíj[-¢Ì¬µéšvh§ŠËkjبžm§ÿÚvÊ,vw(›ö‰õã½–Z‰÷ë(§%‰Éº'$~,]z÷¥¢—«²f¢–)à–+-B蜑ø±uëޖŠ^®Éb²Û,¢êÜyú+éÞ¶m¦Ïÿ–+-²Ê.­ÇŸ¢¸ë–+-³ùb²Ø§~êº'$~,]z÷¥¢—«


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

[Quickfix-developers] out of sequence messages

[Vijay S. Y. <vy...@op...>]

SGVsbG8gQWxsLA0KIEkgYW0gd3JpdGluZyBhbiBvcmRlciByb3V0aW5nIGdhdGV3YXkgdGhhdCBj
b2xsZWN0cyBvcmRlcnMgZnJvbSB2YXJpb3VzIGNsaWVudHMgYW5kIHNlbmRzIHRoZW0gdG8gYSBG
SVggYWNjZXB0b3IgaS5lLiBJIGFtIHVzaW5nIHRoZSBRdWlja0ZpeCBpbml0aWF0b3IgaW4gbXkg
Y29kZS4gVGhlIGluaXRpYXRvciBzZW5kcyBtZXNzYWdlcyB0byB0aGUgYWNjZXB0b3Igb3V0IG9m
IHNlcXVlbmNlLiBUaGlzIGxlYWRzIHRvIHNlc3Npb24gdGVybWluYXRpb24gYW5kIGluY29ycmVj
dCBwcm9jZXNzaW5nLiBBbnkgaWRlYXMgYXJlIHdlbGNvbWUgYW5kIGFwcHJlY2lhdGVkLg0KIA0K
VGhhbmtzLA0KIA0KLS0gVmlqYXkNCiANCjg9RklYLjQuMQE5PTU5ATM1PUEBMzQ9MQE0OT1NRUhJ
ATUyPTIwMDQwMzE2LTE0OjEyOjA2ATU2PU9DT04BOTg9MAExMDg9MzABMTA9MTMxAQ0KDQo4PUZJ
WC40LjEBOT00NwEzNT0wATM0PTIBNDk9TUVISQE1Mj0yMDA0MDMxNi0xNDoxMjozOAE1Nj1PQ09O
ATEwPTA5MgENCg0KOD1GSVguNC4xATk9OTMBMzU9RAEzND0zATQ5PU1FSEkBNTI9MjAwNDAzMTYt
MTQ6MTI6NTIBNTY9T0NPTgExPU1RT1QBMTE9MwEyMT0xATM4PTEwMAE0MD0xATU0PQE1NT1NU0ZU
ATU5PTABMTA9MDUzAQ0KDQo4PUZJWC40LjEBOT01OQEzNT1BATM0PTUBNDk9TUVISQE1Mj0yMDA0
MDMxNi0xNDoxNDoxOAE1Nj1PQ09OATk4PTABMTA4PTMwATEwPTE0MAENCg0KOD1GSVguNC4xATk9
OTEBMzU9RAEzND02ATQ5PU1FSEkBNTI9MjAwNDAzMTYtMTQ6MTQ6MzgBNTY9T0NPTgExPU1RT1QB
MTE9NQEyMT0xATM4PTEBNDA9MQE1ND0BATU1PVNQWAE1OT0wATEwPTE2MAENCg0KOD1GSVguNC4x
ATk9MTIwATM1PUQBMzQ9MwE0Mz1ZATQ5PU1FSEkBNTI9MjAwNDAzMTYtMTQ6MTQ6NDIBNTY9T0NP
TgExMjI9MjAwNDAzMTYtMTQ6MTI6NTIBMT1NUU9UATExPTMBMjE9MQEzOD0xMDABNDA9MQE1ND0B
NTU9TVNGVAE1OT0wATEwPTE0MgENCg0KOD1GSVguNC4xATk9OTIBMzU9RAEzND03ATQ5PU1FSEkB
NTI9MjAwNDAzMTYtMTQ6MTQ6NDIBNTY9T0NPTgExPU1RT1QBMTE9NgEyMT0xATM4PTEyATQwPTEB
NTQ9AQE1NT1TUFgBNTk9MAExMD0yMDgBDQoNCjg9RklYLjQuMQE5PTYwATM1PUEBMzQ9MTABNDk9
TUVISQE1Mj0yMDA0MDMxNi0xNDoxNDo1MQE1Nj1PQ09OATk4PTABMTA4PTMwATEwPTE3MwENCiAN
CkFzIHlvdSBjYW4gc2VlIHNlcXVlbmNlIG51bWJlcnMgMS0zIHdlcmUgc2VudCBpbiBvcmRlci4g
U2VxdWVuY2UgbnVtYmVyIDQgaXMgbWlzc2luZyBhbmQgc2VxdWVuY2UgbnVtYmVyIDMgaXMgcmVz
ZW50IGFmdGVyIHNlcXVlbmNlIDYuIFNlcXVlbmNlIDggYW5kIDkgYXJlIG1pc3NpbmcuDQogDQpJ
IGFtIHBhc2luZyBDIyBjb2RlIGJlbG93IChJIGhhdmUgc3RyaXBwZWQgb2ZmIHRoZSB0cnkvY2F0
Y2ggYmxvY2tzIGZvciBicmV2aXR5J3Mgc2FrZSkNCiANCm5hbWVzcGFjZSBJTVRDX0ZJWEluaXRp
YXRvcg0Kew0KIGNsYXNzIEV4ZWN1dG9yDQogew0KICBwcml2YXRlIFNvY2tldEluaXRpYXRvciBt
X2luaXRpYXRvcjsNCiAgcHJpdmF0ZSBUaHJlYWQgV29ya2VyVGhyZWFkOw0KICBwdWJsaWMgRXhl
Y3V0b3IoKQ0KICB7DQogIH0NCiAgcHVibGljIHZvaWQgR28oKQ0KICB7DQogICAgU2Vzc2lvblNl
dHRpbmdzIHNldHRpbmdzID0gbmV3IFNlc3Npb25TZXR0aW5ncygiT0NPTk5FUi5DRkciKTsNCiAg
ICBBcHBsaWNhdGlvbiBhcHBsaWNhdGlvbiA9IG5ldyBBcHBsaWNhdGlvbigpOw0KICAgIEZpbGVT
dG9yZUZhY3RvcnkgZmFjdG9yeSA9IG5ldyBGaWxlU3RvcmVGYWN0b3J5KHNldHRpbmdzKTsNCiAg
ICBGaWxlTG9nRmFjdG9yeSBsb2dGYWN0b3J5ID0gbmV3IEZpbGVMb2dGYWN0b3J5KCJvdXRwdXQi
KTsNCiAgICBNZXNzYWdlRmFjdG9yeSBtZXNzYWdlRmFjdG9yeSA9IG5ldyBEZWZhdWx0TWVzc2Fn
ZUZhY3RvcnkoKTsNCiAgICBtX2luaXRpYXRvciA9IG5ldyBTb2NrZXRJbml0aWF0b3IgKGFwcGxp
Y2F0aW9uLA0KICAgICAgICAgICAgICAgIGZhY3RvcnksIA0KICAgICAgICAgICAgICAgIHNldHRp
bmdzLA0KICAgICAgICAgICAgICAgIGxvZ0ZhY3RvcnksDQogICAgICAgICAgICAgICAgbWVzc2Fn
ZUZhY3RvcnkpOw0KICAgIG1faW5pdGlhdG9yLnN0YXJ0KCk7DQogICAgQ29uc29sZS5Xcml0ZUxp
bmUgKCJJbml0aWF0b3Igc3RhcnRlZCIpOw0KICAgIHdoaWxlICghYXBwbGljYXRpb24uSXNDb25u
ZWN0ZWQoKSkNCiAgICB7DQogICAgIENvbnNvbGUuV3JpdGVMaW5lICgiV2FpdGluZyB0byBlc3Rh
Ymxpc2ggYSBjb25uZWN0aW9uIHdpdGggRklYIHNlcnZlciIpOw0KICAgICBUaHJlYWQuU2xlZXAo
MTAwKTsNCiAgICB9DQogICAgUHJvY2Vzc09yZGVycygpOw0KDQogIH0NCiAgcHVibGljIHZvaWQg
U3RvcCgpIHttX2luaXRpYXRvci5zdG9wKCk7fQ0KICBwcml2YXRlIHZvaWQgUHJvY2Vzc09yZGVy
cygpDQogIHsNCiAgIFNxbENvbm5lY3Rpb24gQ29ubj1uZXcgU3FsQ29ubmVjdGlvbigpOw0KICAg
Q29ubi5Db25uZWN0aW9uU3RyaW5nPSJEYXRhIFNvdXJjZT0xMC42MC4wLjEwNDsgSW50ZWdyYXRl
ZCBTZWN1cml0eT1TU1BJOyIgKw0KICAgICJJbml0aWFsIENhdGFsb2c9aW10OyB1aWQ9c2E7cHdk
PTtDb25uZWN0IFRpbWVvdXQ9NSI7DQogICAgICAgDQogICBTcWxDb21tYW5kIG15Q01EPW5ldyBT
cWxDb21tYW5kKCk7DQogICBteUNNRC5Db21tYW5kVHlwZT1Db21tYW5kVHlwZS5TdG9yZWRQcm9j
ZWR1cmU7DQogICBteUNNRC5Db21tYW5kVGV4dD0iR2V0T3JkZXJzIjsgDQogICBteUNNRC5Db25u
ZWN0aW9uPUNvbm47DQogICBteUNNRC5QYXJhbWV0ZXJzLkFkZCgiQGNPcmRlclN0YXR1cyIsU3Fs
RGJUeXBlLkNoYXIsMSkuVmFsdWU9J04nOw0KICAgDQogICBTcWxEYXRhQWRhcHRlciBkYTsNCiAg
IGRhPW5ldyBTcWxEYXRhQWRhcHRlcigpOw0KICAgZGEuU2VsZWN0Q29tbWFuZD1teUNNRDsNCiAg
IERhdGFTZXQgZHM9bmV3IERhdGFTZXQoKTsNCiAgIENvbm4uT3BlbigpOw0KICAgd2hpbGUodHJ1
ZSkNCiAgIHsNCiAgICAgZGEuRmlsbChkcyk7DQogICAgIENvbm4uQ2xvc2UoKTsNCiAgICAgRGF0
YVJvd1tdY3VyclJvd3M9ZHMuVGFibGVzWzBdLlNlbGVjdChudWxsLG51bGwsRGF0YVZpZXdSb3dT
dGF0ZS5DdXJyZW50Um93cyk7DQogICAgIGZvcmVhY2goRGF0YVJvdyBteVJvdyBpbiBjdXJyUm93
cykNCiAgICB7DQogICAgICBDb25zb2xlLldyaXRlTGluZSgiU3VibWl0dGluZyBvcmRlciB3aXRo
IGNsaWVudCBvcmRlciBpZCA9ICIrbXlSb3dbIm9yZGVyaWQiXSk7DQogICAgICBTZW5kT3JkZXIo
Q29udmVydC5Ub0ludDMyKG15Um93WyJvcmRlcmlkIl0pLA0KICAgICAgIENvbnZlcnQuVG9TdHJp
bmcobXlSb3dbInN5bWJvbCJdKSwNCiAgICAgICBDb252ZXJ0LlRvQ2hhcihteVJvd1sib3JkZXJz
aWRlIl0pLA0KICAgICAgIENvbnZlcnQuVG9JbnQzMihteVJvd1sicXR5Il0pKTsNCiAgICB9DQog
ICAgQ29uc29sZS5Xcml0ZSgiTm8gbmV3IG9yZGVycyB0byBiZSBzdWJtaXR0ZWQiKTsNCiAgICAg
DQogICB9DQogIH0NCiAgDQogICANCiAgDQogIHB1YmxpYyB2b2lkIFNlbmRPcmRlcihpbnQgb2lk
LHN0cmluZyBvc3ltLGNoYXIgb3NkLGludCBvcXR5KQ0KICB7DQogICBNZXNzYWdlIG9yZGVyOw0K
ICAgU2lkZSBzaWRlOw0KICAgQ2xPcmRJRCBpZD1uZXcgQ2xPcmRJRChvaWQuVG9TdHJpbmcoKSk7
DQogICBIYW5kbEluc3QgaW5zdD1uZXcgSGFuZGxJbnN0KEhhbmRsSW5zdC5BVVRPTUFURURfRVhF
Q1VUSU9OX09SREVSX1BSSVZBVEUpOw0KICAgU3ltYm9sIHN5bT1uZXcgU3ltYm9sKG9zeW0pOw0K
ICAgU2lkZSBzZD1uZXcgU2lkZShvc2QpOw0KICAgT3JkVHlwZSBvdHlwPW5ldyBPcmRUeXBlKE9y
ZFR5cGUuTUFSS0VUKTsNCiAgIFF1aWNrRml4NDEuTmV3T3JkZXJTaW5nbGUgbmV3T3JkZXJTaW5n
bGU9bmV3IFF1aWNrRml4NDEuTmV3T3JkZXJTaW5nbGUoaWQsaW5zdCxzeW0sc2Qsb3R5cCk7DQog
ICANCiAgIG5ld09yZGVyU2luZ2xlLnNldChuZXcgQWNjb3VudCgiTVFPVCIpKTsNCiAgIG5ld09y
ZGVyU2luZ2xlLnNldChuZXcgT3JkZXJRdHkob3F0eSkpOw0KICAgbmV3T3JkZXJTaW5nbGUuc2V0
KG5ldyBUaW1lSW5Gb3JjZShUaW1lSW5Gb3JjZS5EQVkpKTsNCiAgIG5ld09yZGVyU2luZ2xlLmdl
dEhlYWRlcigpLnNldEZpZWxkKG5ldyBTZW5kZXJDb21wSUQoIk1FSEkiKSk7DQogICBuZXdPcmRl
clNpbmdsZS5nZXRIZWFkZXIoKS5zZXRGaWVsZChuZXcgVGFyZ2V0Q29tcElEKCJPQ09OIikpOw0K
ICANCiAgIG9yZGVyID0gbmV3T3JkZXJTaW5nbGU7DQogICBTZXNzaW9uLnNlbmRUb1RhcmdldChv
cmRlcik7DQogIH0NCiB9DQp9DQoNCiANCg==

RE: [Quickfix-developers] Compiling Error - Linux Solution

[Oren M. <ore...@ya...>]

Ahh ok.  Changing that forces it to regenerate the
make files and you don't have autotools installed.  I
forgot that debian is very conservative about what it
installs.  Well I suppose you could install autotools.
 It's a good thing to have if you are going to be
developing with open source tools.  Autotools is the
combination of automake, autoconf, and libtool.  They
are what generates the makefiles for QuickFIX which is
done for you in the distribution, but if you change
the input files it needs to regenerate.  Is installing
these an option for you?

--oren

--- "Leanne T. Smith" <le...@en...> wrote:
> Oren -
>  To disable compilation of the unit tests I
> commented out SUBDIRS = test
> under quickfix/src/C++/Makefile.am. I got the below
> error:
> 
> lea@fla:~/quickfix$ make
> make  all-recursive
> make[1]: Entering directory `/home/leanne/quickfix'
> Making all in src
> make[2]: Entering directory
> `/home/leanne/quickfix/src'
> Making all in C++
> make[3]: Entering directory
> `/home/leanne/quickfix/src/C++'
> cd ../.. && \
>   automake-1.6 --foreign  src/C++/Makefile
> /bin/sh: automake-1.6: command not found
> make[3]: *** [Makefile.in] Error 127
> make[3]: Leaving directory
> `/home/leanne/quickfix/src/C++'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory
> `/home/leanne/quickfix/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/leanne/quickfix'
> make: *** [all] Error 2
> 
> any ideas?
> 
> On Wed, 2004-03-17 at 11:03, Oren Miller wrote:
> > Oh ok, pretty old school.  I wasn't actually aware
> > they were continuing on the 2.95 branch.  2.95.3
> was
> > the last version in the line that I thought was
> widely
> > distributed.  In any case those versions
> definately
> > had even worse template support, so it wouldn't
> > surprise me if it was using an unreasonable amount
> of
> > memory.  We do most of our builds off of the 3.x
> > branch nowadays.  I'm actually a little nervous
> about
> > you not being able to run unit tests because I am
> > unfamiliar with that compiler, but definately be
> sure
> > to run the acceptance tests!
> >  
> > --- "Leanne T. Smith" <le...@en...> wrote:
> > > Oren -
> > > 
> > > I'm running - 
> > > gcc version 2.95.4 20011002 (Debian prerelease)
> > > 
> > > I'll try to compile w/o unit tests for now and
> see
> > > how that works.
> > > Thanks for your comments/suggestions!
> > > 
> > > Leanne
> > > 
> > > On Wed, 2004-03-17 at 10:39, Oren Miller wrote:
> > > > There really isn't a good way to answer that
> > > because
> > > > it depends on the version of gcc you are
> using. 
> > > Some
> > > > are greedier than others.  What version are
> you
> > > using?
> > > > 
> > > > What is generally true with gcc compilers is
> they
> > > are
> > > > incredibly inneficient when compiling
> templates,
> > > and
> > > > our unit test framework is heavily template
> based.
> > >  I
> > > > would like to change this because it also
> slows
> > > down
> > > > compile times.
> > > > 
> > > > I would try to compile without the unit tests
> for
> > > now.
> > > >  You will have to rely on the acceptance tests
> to
> > > > verify the build is good.  To disable
> compilation
> > > of
> > > > the unit tests just open op the
> > > > quickfix/src/C++/Makefile.am and comment out
> the
> > > > SUBDIRS = test
> > > > 
> > > > --- "Leanne T. Smith" <le...@en...>
> wrote:
> > > > > Oren - 
> > > > > 
> > > > > Do you happen to know the minimal RAM &
> virtual
> > > > > memory needed to compile
> > > > > quickfix? I'd rather compile quickfix in
> > > production
> > > > > mode.
> > > > > 
> > > > > Here are my RAM & virtual memory stats.
> > > > > 
> > > > > 08:15:47 up 13 days, 15:50,  1 user,  load
> > > average:
> > > > > 0.00, 0.24, 0.34
> > > > > 42 processes: 41 sleeping, 1 running, 0
> zombie,
> > > 0
> > > > > stopped
> > > > > CPU states:   0.4% user,   0.2% system,  
> 0.0%
> > > nice,
> > > > >  99.4% idle
> > > > > Mem:    124700K total,   113160K used,   
> 11540K
> > > > > free,    25276K buffers
> > > > > Swap:   305224K total,    22728K used,  
> 282496K
> > > > > free,    33584K cached
> > > > > 
> > > > > I set CXXFLAGS="-O0" where it was originally
> set
> > > to
> > > > > CXXFLAGS="-g" and
> > > > > re-ran ./configure. I'm still unable to
> compile.
> > > Any
> > > > > ideas?
> > > > > 
> > > > > Thanks!
> > > > >  
> > > > > 
> > > > > On Wed, 2004-03-17 at 01:41, Miller, Oren
> wrote:
> > > > > > Leanne,
> > > > > > 
> > > > > > I believe when this happens it generally
> means
> > > > > that g++ doesn't have enough memory
> available to
> > > it.
> > > > >  Any idea how much ram and virtual memory
> you
> > > have
> > > > > allocated to that box?
> > > > > > 
> > > > > > One thing you can try without messing
> around
> > > with
> > > > > any of that stuff is to turn off compiler
> > > > > optimizations.  This should lessen the
> memory
> > > > > requirement.  Just set the CXXFLAGS
> environment
> > > > > variable to -O0 and run ./configure and make
> > > again. 
> > > > > See if that pulls you through the
> compilation
> > > with
> > > > > your current configuration.
> > > > > > 
> > > > > > You probably won't want to run in
> production
> > > with
> > > > > that build but it will at least get you up
> and
> > > > > running while you resolve the memory issue.
> > > > > > 
> > > > > > --oren
> > > > > > 
> > > > > > -----Original Message-----
> > > > > > From:	Leanne T. Smith
> > > [mailto:le...@en...]
> > > > > > Sent:	Tue 3/16/2004 4:01 PM
> > > > > > To:
> qui...@li...
> > > > > > Cc:	
> > > > > > Subject:	[Quickfix-developers] Compiling
> Error
> > > -
> > > > > Linux Solution
> > > > > > I'm receiving a g++ compiling error for
> > > QuickFIX
> > > > > on Linux. I followed
> > > > > > the Installation Documentation, so I'm not
> > > sure I
> > > > > could be missing. I've
> > > > > > attached the error below. Please let me
> know
> > > if
> > > > > you have any idea what I
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

RE: [Quickfix-developers] Compiling Error - Linux Solution

[Leanne T. S. <le...@en...>]

Oren -
 To disable compilation of the unit tests I commented out SUBDIRS = test
under quickfix/src/C++/Makefile.am. I got the below error:

lea@fla:~/quickfix$ make
make  all-recursive
make[1]: Entering directory `/home/leanne/quickfix'
Making all in src
make[2]: Entering directory `/home/leanne/quickfix/src'
Making all in C++
make[3]: Entering directory `/home/leanne/quickfix/src/C++'
cd ../.. && \
  automake-1.6 --foreign  src/C++/Makefile
/bin/sh: automake-1.6: command not found
make[3]: *** [Makefile.in] Error 127
make[3]: Leaving directory `/home/leanne/quickfix/src/C++'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/leanne/quickfix/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/leanne/quickfix'
make: *** [all] Error 2

any ideas?

On Wed, 2004-03-17 at 11:03, Oren Miller wrote:
> Oh ok, pretty old school.  I wasn't actually aware
> they were continuing on the 2.95 branch.  2.95.3 was
> the last version in the line that I thought was widely
> distributed.  In any case those versions definately
> had even worse template support, so it wouldn't
> surprise me if it was using an unreasonable amount of
> memory.  We do most of our builds off of the 3.x
> branch nowadays.  I'm actually a little nervous about
> you not being able to run unit tests because I am
> unfamiliar with that compiler, but definately be sure
> to run the acceptance tests!
>  
> --- "Leanne T. Smith" <le...@en...> wrote:
> > Oren -
> > 
> > I'm running - 
> > gcc version 2.95.4 20011002 (Debian prerelease)
> > 
> > I'll try to compile w/o unit tests for now and see
> > how that works.
> > Thanks for your comments/suggestions!
> > 
> > Leanne
> > 
> > On Wed, 2004-03-17 at 10:39, Oren Miller wrote:
> > > There really isn't a good way to answer that
> > because
> > > it depends on the version of gcc you are using. 
> > Some
> > > are greedier than others.  What version are you
> > using?
> > > 
> > > What is generally true with gcc compilers is they
> > are
> > > incredibly inneficient when compiling templates,
> > and
> > > our unit test framework is heavily template based.
> >  I
> > > would like to change this because it also slows
> > down
> > > compile times.
> > > 
> > > I would try to compile without the unit tests for
> > now.
> > >  You will have to rely on the acceptance tests to
> > > verify the build is good.  To disable compilation
> > of
> > > the unit tests just open op the
> > > quickfix/src/C++/Makefile.am and comment out the
> > > SUBDIRS = test
> > > 
> > > --- "Leanne T. Smith" <le...@en...> wrote:
> > > > Oren - 
> > > > 
> > > > Do you happen to know the minimal RAM & virtual
> > > > memory needed to compile
> > > > quickfix? I'd rather compile quickfix in
> > production
> > > > mode.
> > > > 
> > > > Here are my RAM & virtual memory stats.
> > > > 
> > > > 08:15:47 up 13 days, 15:50,  1 user,  load
> > average:
> > > > 0.00, 0.24, 0.34
> > > > 42 processes: 41 sleeping, 1 running, 0 zombie,
> > 0
> > > > stopped
> > > > CPU states:   0.4% user,   0.2% system,   0.0%
> > nice,
> > > >  99.4% idle
> > > > Mem:    124700K total,   113160K used,    11540K
> > > > free,    25276K buffers
> > > > Swap:   305224K total,    22728K used,   282496K
> > > > free,    33584K cached
> > > > 
> > > > I set CXXFLAGS="-O0" where it was originally set
> > to
> > > > CXXFLAGS="-g" and
> > > > re-ran ./configure. I'm still unable to compile.
> > Any
> > > > ideas?
> > > > 
> > > > Thanks!
> > > >  
> > > > 
> > > > On Wed, 2004-03-17 at 01:41, Miller, Oren wrote:
> > > > > Leanne,
> > > > > 
> > > > > I believe when this happens it generally means
> > > > that g++ doesn't have enough memory available to
> > it.
> > > >  Any idea how much ram and virtual memory you
> > have
> > > > allocated to that box?
> > > > > 
> > > > > One thing you can try without messing around
> > with
> > > > any of that stuff is to turn off compiler
> > > > optimizations.  This should lessen the memory
> > > > requirement.  Just set the CXXFLAGS environment
> > > > variable to -O0 and run ./configure and make
> > again. 
> > > > See if that pulls you through the compilation
> > with
> > > > your current configuration.
> > > > > 
> > > > > You probably won't want to run in production
> > with
> > > > that build but it will at least get you up and
> > > > running while you resolve the memory issue.
> > > > > 
> > > > > --oren
> > > > > 
> > > > > -----Original Message-----
> > > > > From:	Leanne T. Smith
> > [mailto:le...@en...]
> > > > > Sent:	Tue 3/16/2004 4:01 PM
> > > > > To:	qui...@li...
> > > > > Cc:	
> > > > > Subject:	[Quickfix-developers] Compiling Error
> > -
> > > > Linux Solution
> > > > > I'm receiving a g++ compiling error for
> > QuickFIX
> > > > on Linux. I followed
> > > > > the Installation Documentation, so I'm not
> > sure I
> > > > could be missing. I've
> > > > > attached the error below. Please let me know
> > if
> > > > you have any idea what I
> > > > > might be overlooking. Thanks.
> > > > > 
> > > > > 
> > > > > lea@fla:~/quickfix$ make
> > > > > make  all-recursive
> > > > > make[1]: Entering directory
> > > > `/home/leanne/quickfix'
> > > > > Making all in src
> > > > > make[2]: Entering directory
> > > > `/home/leanne/quickfix/src'
> > > > > Making all in C++
> > > > > make[3]: Entering directory
> > > > `/home/leanne/quickfix/src/C++'
> > > > > Making all in test
> > > > > make[4]: Entering directory
> > > > `/home/leanne/quickfix/src/C++/test'
> > > > > source='MessagesTestCase.cpp'
> > > > object='MessagesTestCase.lo' libtool=yes \
> > > > > depfile='.deps/MessagesTestCase.Plo'
> > > > > tmpdepfile='.deps/MessagesTestCase.TPlo' \
> > > > > depmode=gcc /bin/sh ../../../depcomp \
> > > > > /bin/sh ../../../libtool --mode=compile g++
> > > > -DHAVE_CONFIG_H -I. -I.
> > > > > -I../../.. -I..    -g -O2 -Wall  
> > > > -I/usr/include/libxml2/libxml
> > > > > -I/usr/include/libxml2 -I/include
> > -I/include/linux
> > > > -c -o
> > > > > MessagesTestCase.lo `test -f
> > > > 'MessagesTestCase.cpp' || echo
> > > > > './'`MessagesTestCase.cpp
> > > > >  g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I..
> > -g
> > > > -O2 -Wall
> > > > > -I/usr/include/libxml2/libxml
> > > > -I/usr/include/libxml2 -I/include
> > > > > -I/include/linux -c MessagesTestCase.cpp
> > > > > -Wp,-MD,.deps/MessagesTestCase.TPlo  -fPIC
> > -DPIC
> > > > -o
> > > > > .libs/MessagesTestCase.o
> > > > > g++: Internal compiler error: program cc1plus
> > got
> > > > fatal signal 9
> > > > > make[4]: *** [MessagesTestCase.lo] Error 1
> > > > > make[4]: Leaving directory
> > > > `/home/leanne/quickfix/src/C++/test'
> > > > > make[3]: *** [all-recursive] Error 1
> > > > > make[3]: Leaving directory
> > > > `/home/leanne/quickfix/src/C++'
> > > > > make[2]: *** [all-recursive] Error 1
> > > > > make[2]: Leaving directory
> > > > `/home/leanne/quickfix/src'
> > > > > make[1]: *** [all-recursive] Error 1
> > > > > make[1]: Leaving directory
> > `/home/leanne/quickfix'
> > > > > make: *** [all] Error 2
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > >
> > > >
> > >
> >
> -------------------------------------------------------
> > > > > This SF.Net email is sponsored by: IBM Linux
> > > > Tutorials
> > > > > Free Linux tutorial presented by Daniel
> > Robbins,
> > > > President and CEO of
> > > > > GenToo technologies. Learn everything from
> > > > fundamentals to system
> > > > >
> > > >
> > >
> >
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > > > >
> > _______________________________________________
> > > > > Quickfix-developers mailing list
> > > > > Qui...@li...
> > > > >
> > 
> === message truncated ===
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - More reliable, more storage, less spam
> http://mail.yahoo.com
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 

RE: [Quickfix-developers] Compiling Error - Linux Solution

[Oren M. <ore...@ya...>]

Oh ok, pretty old school.  I wasn't actually aware
they were continuing on the 2.95 branch.  2.95.3 was
the last version in the line that I thought was widely
distributed.  In any case those versions definately
had even worse template support, so it wouldn't
surprise me if it was using an unreasonable amount of
memory.  We do most of our builds off of the 3.x
branch nowadays.  I'm actually a little nervous about
you not being able to run unit tests because I am
unfamiliar with that compiler, but definately be sure
to run the acceptance tests!
 
--- "Leanne T. Smith" <le...@en...> wrote:
> Oren -
> 
> I'm running - 
> gcc version 2.95.4 20011002 (Debian prerelease)
> 
> I'll try to compile w/o unit tests for now and see
> how that works.
> Thanks for your comments/suggestions!
> 
> Leanne
> 
> On Wed, 2004-03-17 at 10:39, Oren Miller wrote:
> > There really isn't a good way to answer that
> because
> > it depends on the version of gcc you are using. 
> Some
> > are greedier than others.  What version are you
> using?
> > 
> > What is generally true with gcc compilers is they
> are
> > incredibly inneficient when compiling templates,
> and
> > our unit test framework is heavily template based.
>  I
> > would like to change this because it also slows
> down
> > compile times.
> > 
> > I would try to compile without the unit tests for
> now.
> >  You will have to rely on the acceptance tests to
> > verify the build is good.  To disable compilation
> of
> > the unit tests just open op the
> > quickfix/src/C++/Makefile.am and comment out the
> > SUBDIRS = test
> > 
> > --- "Leanne T. Smith" <le...@en...> wrote:
> > > Oren - 
> > > 
> > > Do you happen to know the minimal RAM & virtual
> > > memory needed to compile
> > > quickfix? I'd rather compile quickfix in
> production
> > > mode.
> > > 
> > > Here are my RAM & virtual memory stats.
> > > 
> > > 08:15:47 up 13 days, 15:50,  1 user,  load
> average:
> > > 0.00, 0.24, 0.34
> > > 42 processes: 41 sleeping, 1 running, 0 zombie,
> 0
> > > stopped
> > > CPU states:   0.4% user,   0.2% system,   0.0%
> nice,
> > >  99.4% idle
> > > Mem:    124700K total,   113160K used,    11540K
> > > free,    25276K buffers
> > > Swap:   305224K total,    22728K used,   282496K
> > > free,    33584K cached
> > > 
> > > I set CXXFLAGS="-O0" where it was originally set
> to
> > > CXXFLAGS="-g" and
> > > re-ran ./configure. I'm still unable to compile.
> Any
> > > ideas?
> > > 
> > > Thanks!
> > >  
> > > 
> > > On Wed, 2004-03-17 at 01:41, Miller, Oren wrote:
> > > > Leanne,
> > > > 
> > > > I believe when this happens it generally means
> > > that g++ doesn't have enough memory available to
> it.
> > >  Any idea how much ram and virtual memory you
> have
> > > allocated to that box?
> > > > 
> > > > One thing you can try without messing around
> with
> > > any of that stuff is to turn off compiler
> > > optimizations.  This should lessen the memory
> > > requirement.  Just set the CXXFLAGS environment
> > > variable to -O0 and run ./configure and make
> again. 
> > > See if that pulls you through the compilation
> with
> > > your current configuration.
> > > > 
> > > > You probably won't want to run in production
> with
> > > that build but it will at least get you up and
> > > running while you resolve the memory issue.
> > > > 
> > > > --oren
> > > > 
> > > > -----Original Message-----
> > > > From:	Leanne T. Smith
> [mailto:le...@en...]
> > > > Sent:	Tue 3/16/2004 4:01 PM
> > > > To:	qui...@li...
> > > > Cc:	
> > > > Subject:	[Quickfix-developers] Compiling Error
> -
> > > Linux Solution
> > > > I'm receiving a g++ compiling error for
> QuickFIX
> > > on Linux. I followed
> > > > the Installation Documentation, so I'm not
> sure I
> > > could be missing. I've
> > > > attached the error below. Please let me know
> if
> > > you have any idea what I
> > > > might be overlooking. Thanks.
> > > > 
> > > > 
> > > > lea@fla:~/quickfix$ make
> > > > make  all-recursive
> > > > make[1]: Entering directory
> > > `/home/leanne/quickfix'
> > > > Making all in src
> > > > make[2]: Entering directory
> > > `/home/leanne/quickfix/src'
> > > > Making all in C++
> > > > make[3]: Entering directory
> > > `/home/leanne/quickfix/src/C++'
> > > > Making all in test
> > > > make[4]: Entering directory
> > > `/home/leanne/quickfix/src/C++/test'
> > > > source='MessagesTestCase.cpp'
> > > object='MessagesTestCase.lo' libtool=yes \
> > > > depfile='.deps/MessagesTestCase.Plo'
> > > > tmpdepfile='.deps/MessagesTestCase.TPlo' \
> > > > depmode=gcc /bin/sh ../../../depcomp \
> > > > /bin/sh ../../../libtool --mode=compile g++
> > > -DHAVE_CONFIG_H -I. -I.
> > > > -I../../.. -I..    -g -O2 -Wall  
> > > -I/usr/include/libxml2/libxml
> > > > -I/usr/include/libxml2 -I/include
> -I/include/linux
> > > -c -o
> > > > MessagesTestCase.lo `test -f
> > > 'MessagesTestCase.cpp' || echo
> > > > './'`MessagesTestCase.cpp
> > > >  g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I..
> -g
> > > -O2 -Wall
> > > > -I/usr/include/libxml2/libxml
> > > -I/usr/include/libxml2 -I/include
> > > > -I/include/linux -c MessagesTestCase.cpp
> > > > -Wp,-MD,.deps/MessagesTestCase.TPlo  -fPIC
> -DPIC
> > > -o
> > > > .libs/MessagesTestCase.o
> > > > g++: Internal compiler error: program cc1plus
> got
> > > fatal signal 9
> > > > make[4]: *** [MessagesTestCase.lo] Error 1
> > > > make[4]: Leaving directory
> > > `/home/leanne/quickfix/src/C++/test'
> > > > make[3]: *** [all-recursive] Error 1
> > > > make[3]: Leaving directory
> > > `/home/leanne/quickfix/src/C++'
> > > > make[2]: *** [all-recursive] Error 1
> > > > make[2]: Leaving directory
> > > `/home/leanne/quickfix/src'
> > > > make[1]: *** [all-recursive] Error 1
> > > > make[1]: Leaving directory
> `/home/leanne/quickfix'
> > > > make: *** [all] Error 2
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > >
> > >
> >
>
-------------------------------------------------------
> > > > This SF.Net email is sponsored by: IBM Linux
> > > Tutorials
> > > > Free Linux tutorial presented by Daniel
> Robbins,
> > > President and CEO of
> > > > GenToo technologies. Learn everything from
> > > fundamentals to system
> > > >
> > >
> >
>
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > > >
> _______________________________________________
> > > > Quickfix-developers mailing list
> > > > Qui...@li...
> > > >
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

RE: [Quickfix-developers] Compiling Error - Linux Solution

[Leanne T. S. <le...@en...>]

Oren -

I'm running - 
gcc version 2.95.4 20011002 (Debian prerelease)

I'll try to compile w/o unit tests for now and see how that works.
Thanks for your comments/suggestions!

Leanne

On Wed, 2004-03-17 at 10:39, Oren Miller wrote:
> There really isn't a good way to answer that because
> it depends on the version of gcc you are using.  Some
> are greedier than others.  What version are you using?
> 
> What is generally true with gcc compilers is they are
> incredibly inneficient when compiling templates, and
> our unit test framework is heavily template based.  I
> would like to change this because it also slows down
> compile times.
> 
> I would try to compile without the unit tests for now.
>  You will have to rely on the acceptance tests to
> verify the build is good.  To disable compilation of
> the unit tests just open op the
> quickfix/src/C++/Makefile.am and comment out the
> SUBDIRS = test
> 
> --- "Leanne T. Smith" <le...@en...> wrote:
> > Oren - 
> > 
> > Do you happen to know the minimal RAM & virtual
> > memory needed to compile
> > quickfix? I'd rather compile quickfix in production
> > mode.
> > 
> > Here are my RAM & virtual memory stats.
> > 
> > 08:15:47 up 13 days, 15:50,  1 user,  load average:
> > 0.00, 0.24, 0.34
> > 42 processes: 41 sleeping, 1 running, 0 zombie, 0
> > stopped
> > CPU states:   0.4% user,   0.2% system,   0.0% nice,
> >  99.4% idle
> > Mem:    124700K total,   113160K used,    11540K
> > free,    25276K buffers
> > Swap:   305224K total,    22728K used,   282496K
> > free,    33584K cached
> > 
> > I set CXXFLAGS="-O0" where it was originally set to
> > CXXFLAGS="-g" and
> > re-ran ./configure. I'm still unable to compile. Any
> > ideas?
> > 
> > Thanks!
> >  
> > 
> > On Wed, 2004-03-17 at 01:41, Miller, Oren wrote:
> > > Leanne,
> > > 
> > > I believe when this happens it generally means
> > that g++ doesn't have enough memory available to it.
> >  Any idea how much ram and virtual memory you have
> > allocated to that box?
> > > 
> > > One thing you can try without messing around with
> > any of that stuff is to turn off compiler
> > optimizations.  This should lessen the memory
> > requirement.  Just set the CXXFLAGS environment
> > variable to -O0 and run ./configure and make again. 
> > See if that pulls you through the compilation with
> > your current configuration.
> > > 
> > > You probably won't want to run in production with
> > that build but it will at least get you up and
> > running while you resolve the memory issue.
> > > 
> > > --oren
> > > 
> > > -----Original Message-----
> > > From:	Leanne T. Smith [mailto:le...@en...]
> > > Sent:	Tue 3/16/2004 4:01 PM
> > > To:	qui...@li...
> > > Cc:	
> > > Subject:	[Quickfix-developers] Compiling Error -
> > Linux Solution
> > > I'm receiving a g++ compiling error for QuickFIX
> > on Linux. I followed
> > > the Installation Documentation, so I'm not sure I
> > could be missing. I've
> > > attached the error below. Please let me know if
> > you have any idea what I
> > > might be overlooking. Thanks.
> > > 
> > > 
> > > lea@fla:~/quickfix$ make
> > > make  all-recursive
> > > make[1]: Entering directory
> > `/home/leanne/quickfix'
> > > Making all in src
> > > make[2]: Entering directory
> > `/home/leanne/quickfix/src'
> > > Making all in C++
> > > make[3]: Entering directory
> > `/home/leanne/quickfix/src/C++'
> > > Making all in test
> > > make[4]: Entering directory
> > `/home/leanne/quickfix/src/C++/test'
> > > source='MessagesTestCase.cpp'
> > object='MessagesTestCase.lo' libtool=yes \
> > > depfile='.deps/MessagesTestCase.Plo'
> > > tmpdepfile='.deps/MessagesTestCase.TPlo' \
> > > depmode=gcc /bin/sh ../../../depcomp \
> > > /bin/sh ../../../libtool --mode=compile g++
> > -DHAVE_CONFIG_H -I. -I.
> > > -I../../.. -I..    -g -O2 -Wall  
> > -I/usr/include/libxml2/libxml
> > > -I/usr/include/libxml2 -I/include -I/include/linux
> > -c -o
> > > MessagesTestCase.lo `test -f
> > 'MessagesTestCase.cpp' || echo
> > > './'`MessagesTestCase.cpp
> > >  g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I.. -g
> > -O2 -Wall
> > > -I/usr/include/libxml2/libxml
> > -I/usr/include/libxml2 -I/include
> > > -I/include/linux -c MessagesTestCase.cpp
> > > -Wp,-MD,.deps/MessagesTestCase.TPlo  -fPIC -DPIC
> > -o
> > > .libs/MessagesTestCase.o
> > > g++: Internal compiler error: program cc1plus got
> > fatal signal 9
> > > make[4]: *** [MessagesTestCase.lo] Error 1
> > > make[4]: Leaving directory
> > `/home/leanne/quickfix/src/C++/test'
> > > make[3]: *** [all-recursive] Error 1
> > > make[3]: Leaving directory
> > `/home/leanne/quickfix/src/C++'
> > > make[2]: *** [all-recursive] Error 1
> > > make[2]: Leaving directory
> > `/home/leanne/quickfix/src'
> > > make[1]: *** [all-recursive] Error 1
> > > make[1]: Leaving directory `/home/leanne/quickfix'
> > > make: *** [all] Error 2
> > > 
> > > 
> > > 
> > > 
> > > 
> > >
> >
> -------------------------------------------------------
> > > This SF.Net email is sponsored by: IBM Linux
> > Tutorials
> > > Free Linux tutorial presented by Daniel Robbins,
> > President and CEO of
> > > GenToo technologies. Learn everything from
> > fundamentals to system
> > >
> >
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > > _______________________________________________
> > > Quickfix-developers mailing list
> > > Qui...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> > > 
> > > 
> > > 
> > > 
> > >
> >
> -------------------------------------------------------
> > > This SF.Net email is sponsored by: IBM Linux
> > Tutorials
> > > Free Linux tutorial presented by Daniel Robbins,
> > President and CEO of
> > > GenToo technologies. Learn everything from
> > fundamentals to system
> > >
> >
> administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
> > > _______________________________________________
> > > Quickfix-developers mailing list
> > > Qui...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> > 
> > 
> > 
> > 
> >
> -------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux
> > Tutorials
> > Free Linux tutorial presented by Daniel Robbins,
> > President and CEO of
> > GenToo technologies. Learn everything from
> > fundamentals to system
> >
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > _______________________________________________
> > Quickfix-developers mailing list
> > Qui...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - More reliable, more storage, less spam
> http://mail.yahoo.com

RE: [Quickfix-developers] Handling FIX Messages From An External Source

[Oren M. <ore...@ya...>]

Yeah Jon, you can just use the constructor of the
message class to parse.  The only thing you need to
worry about is if you are passing around messages with
repeating groups you must pass in a DataDictionary to
the constructor with the appropriate FIX version or
the message will not have enough information to parse.
 This isn't a problem with message types like
NewOrderSingle, ExecutionReport etc.

--oren

--- "Dahl, Jon" <JD...@cm...> wrote:
> Well, that is basically what I am doing. I'm using
> the Message class for
> extraction.
> 
> Just wanted to know if there was anything else I
> should be using when
> dealing with
> an external FIX message.
> 
> JD
> 
> -----Original Message-----
> From: Miller, Oren
> [mailto:OM...@ri...] 
> Sent: Tuesday, March 16, 2004 8:40 AM
> To: Dahl, Jon;
> qui...@li...
> Subject: Re: [Quickfix-developers] Handling FIX
> Messages From An
> External Source
> 
> 
> Hmm,
> 
> Can't you just make a copy of the ExecutionReport
> message, lookup the
> clordid, set the correct sender and target compids
> and send it along to
> the client?
> 
> --oren
> 
> --------------------------
> Sent from my BlackBerry Wireless Handheld
> 
> 
> -----Original Message-----
> From: Dahl, Jon <JD...@cm...>
> To: qui...@li...
> <qui...@li...>
> Sent: Mon Mar 15 10:45:08 2004
> Subject: [Quickfix-developers] Handling FIX Messages
> From An External
> Source
> 
> Currently, we are writing an Order Entry Gateway
> that will handle
> requests from clients and forward the message off to
> the engine in FIX
> Format. Execution Report Messages will be returned
> in FIX format as
> well.
> 
> The response message from the engine will not have
> correct SenderCompID
> and TargetCompID fields in it. So I will need to be
> able to extract
> fields from the message and place them in a valid
> ExecutionReport
> message to be sent off to the correct client. I will
> be returned the
> original ClOrdID from the engine so there shouldn't
> be a problem
> returning it to the correct client if I cache
> requests.
> 
> My biggest ? is having the ability to parse the
> ExecutionReport message
> for fields to build the ExecutionReport message
> being sent back to the
> client. Right now, it looks like the Message class
> is the place to
> start. Anyone else have any suggestions how to parse
> the fields out?
> Would MessageCracker blow up if the SenderCompID and
> TargetCompID are
> not a valid Session connected?
> 
> Thanks,
> 
> JD
> 
> P.S. - Kudos on the new
> website(http://www.quickfixengine.org).
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux
> Tutorials
> Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> GenToo technologies. Learn everything from
> fundamentals to system
>
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=ick
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
>
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux
> Tutorials
> Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> GenToo technologies. Learn everything from
> fundamentals to system
>
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
>
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

Re: [Quickfix-developers] Double logout sent

[Oren M. <ore...@ya...>]

Oh I think probably a couple weeks.  It's going to be
a very small point release.

--- Apichat Banyatsupasil <sar...@ly...> wrote:
> Oren,
>     Thanks for answer. The new features sound very
> good to me. I will check out the cvs version.
>     However, I believe my client will not be
> comfortable with the non-release product. Could you
> give the estimate time for the release of 1.7.1
> please?
> 
> Thanks,
> Apichat
> 
> ---
> _____________________________
> Apichat Banyatsupasil
> Director of Software Development
> Intelligent Brain Consulting Co., Ltd.
> 287/23-24 Surawong Rd 2nd Fl,
> Suriyawong, Bangrak,
> Bangkok 10500
> Thailand
> Office +66 (2) 635-7655, +66 (2) 635-6702
> Fax  +66 (2) 635-7603
> Cell +66 (9) 131-4009
> URL  http://www.intelligentbrain.com
> 
> 
> 
> 
> 
> 
> 
> 
> --------- Original Message ---------
> 
> DATE: Mon, 15 Mar 2004 22:22:58
> From: Oren Miller <ore...@ya...>
> To: sar...@ly...,
> qui...@li...
> Cc: 
> 
> >Support for proper logoff is really the one of two
> >important pieces of functionality missing from
> current
> >releases of QuickFIX.  The bad news is that 1.7.0
> >suffers from this same issue.  The good news is
> that
> >supports for this functionality is currently
> available
> >in the CVS repository.  We plan on doing a 1.7.1
> >release with this feature as well as support for
> >variable length sessions.
> >
> >If you would like proper support for logout's, I
> would
> >suggest going with the CVS version.  Logout's are
> done
> >either explicitly by calling the logoff() method on
> >the session.  Calling logon will bring the session
> >back on line.  Also, when calling stop on the
> >initiator and acceptor, all open sessions will go
> >through a proper logoff sequence before QuickFIX
> shuts
> >down.
> >
> >--oren
> >
> >--- Apichat Banyatsupasil <sar...@ly...>
> wrote:
> >> Hi,
> >>    I currently use QuickFix 1.7.0, java version.
> I
> >> have problem that when I try to send logout
> message,
> >> the second logout is also sent automatically by
> >> QuickFIX. This seems to be the same problem as 
> >>
>
>http://sourceforge.net/mailarchive/message.php?msg_id=6306713
> >> and
> >>
>
>http://sourceforge.net/mailarchive/message.php?msg_id=6314798
> >> 
> >> however, none of them provide solutions. They
> >> provide only workaround which could bring another
> >> problem.
> >> 
> >> Could anyone help me with this please?
> >> 
> >> Thanks,
> >> Apichat
> >> _____________________________
> >> Apichat Banyatsupasil
> >> Director of Software Development
> >> Intelligent Brain Consulting Co., Ltd.
> >> 287/23-24 Surawong Rd 2nd Fl,
> >> Suriyawong, Bangrak,
> >> Bangkok 10500
> >> Thailand
> >> Office +66 (2) 635-7655, +66 (2) 635-6702
> >> Fax  +66 (2) 635-7603
> >> Cell +66 (9) 131-4009
> >> URL  http://www.intelligentbrain.com
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >>
>
>____________________________________________________________
> >> Find what you are looking for with the Lycos
> Yellow
> >> Pages
> >>
>
>http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
> >> 
> >> 
> >>
>
>-------------------------------------------------------
> >> This SF.Net email is sponsored by: IBM Linux
> >> Tutorials
> >> Free Linux tutorial presented by Daniel Robbins,
> >> President and CEO of
> >> GenToo technologies. Learn everything from
> >> fundamentals to system
> >>
>
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> >> _______________________________________________
> >> Quickfix-developers mailing list
> >> Qui...@li...
> >>
>
>https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> >
> >
> >__________________________________
> >Do you Yahoo!?
> >Yahoo! Mail - More reliable, more storage, less
> spam
> >http://mail.yahoo.com
> >
> 
> 
> 
>
____________________________________________________________
> Find what you are looking for with the Lycos Yellow
> Pages
>
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux
> Tutorials
> Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> GenToo technologies. Learn everything from
> fundamentals to system
>
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
>
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

RE: [Quickfix-developers] Compiling Error - Linux Solution

[Oren M. <ore...@ya...>]

There really isn't a good way to answer that because
it depends on the version of gcc you are using.  Some
are greedier than others.  What version are you using?

What is generally true with gcc compilers is they are
incredibly inneficient when compiling templates, and
our unit test framework is heavily template based.  I
would like to change this because it also slows down
compile times.

I would try to compile without the unit tests for now.
 You will have to rely on the acceptance tests to
verify the build is good.  To disable compilation of
the unit tests just open op the
quickfix/src/C++/Makefile.am and comment out the
SUBDIRS = test

--- "Leanne T. Smith" <le...@en...> wrote:
> Oren - 
> 
> Do you happen to know the minimal RAM & virtual
> memory needed to compile
> quickfix? I'd rather compile quickfix in production
> mode.
> 
> Here are my RAM & virtual memory stats.
> 
> 08:15:47 up 13 days, 15:50,  1 user,  load average:
> 0.00, 0.24, 0.34
> 42 processes: 41 sleeping, 1 running, 0 zombie, 0
> stopped
> CPU states:   0.4% user,   0.2% system,   0.0% nice,
>  99.4% idle
> Mem:    124700K total,   113160K used,    11540K
> free,    25276K buffers
> Swap:   305224K total,    22728K used,   282496K
> free,    33584K cached
> 
> I set CXXFLAGS="-O0" where it was originally set to
> CXXFLAGS="-g" and
> re-ran ./configure. I'm still unable to compile. Any
> ideas?
> 
> Thanks!
>  
> 
> On Wed, 2004-03-17 at 01:41, Miller, Oren wrote:
> > Leanne,
> > 
> > I believe when this happens it generally means
> that g++ doesn't have enough memory available to it.
>  Any idea how much ram and virtual memory you have
> allocated to that box?
> > 
> > One thing you can try without messing around with
> any of that stuff is to turn off compiler
> optimizations.  This should lessen the memory
> requirement.  Just set the CXXFLAGS environment
> variable to -O0 and run ./configure and make again. 
> See if that pulls you through the compilation with
> your current configuration.
> > 
> > You probably won't want to run in production with
> that build but it will at least get you up and
> running while you resolve the memory issue.
> > 
> > --oren
> > 
> > -----Original Message-----
> > From:	Leanne T. Smith [mailto:le...@en...]
> > Sent:	Tue 3/16/2004 4:01 PM
> > To:	qui...@li...
> > Cc:	
> > Subject:	[Quickfix-developers] Compiling Error -
> Linux Solution
> > I'm receiving a g++ compiling error for QuickFIX
> on Linux. I followed
> > the Installation Documentation, so I'm not sure I
> could be missing. I've
> > attached the error below. Please let me know if
> you have any idea what I
> > might be overlooking. Thanks.
> > 
> > 
> > lea@fla:~/quickfix$ make
> > make  all-recursive
> > make[1]: Entering directory
> `/home/leanne/quickfix'
> > Making all in src
> > make[2]: Entering directory
> `/home/leanne/quickfix/src'
> > Making all in C++
> > make[3]: Entering directory
> `/home/leanne/quickfix/src/C++'
> > Making all in test
> > make[4]: Entering directory
> `/home/leanne/quickfix/src/C++/test'
> > source='MessagesTestCase.cpp'
> object='MessagesTestCase.lo' libtool=yes \
> > depfile='.deps/MessagesTestCase.Plo'
> > tmpdepfile='.deps/MessagesTestCase.TPlo' \
> > depmode=gcc /bin/sh ../../../depcomp \
> > /bin/sh ../../../libtool --mode=compile g++
> -DHAVE_CONFIG_H -I. -I.
> > -I../../.. -I..    -g -O2 -Wall  
> -I/usr/include/libxml2/libxml
> > -I/usr/include/libxml2 -I/include -I/include/linux
> -c -o
> > MessagesTestCase.lo `test -f
> 'MessagesTestCase.cpp' || echo
> > './'`MessagesTestCase.cpp
> >  g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I.. -g
> -O2 -Wall
> > -I/usr/include/libxml2/libxml
> -I/usr/include/libxml2 -I/include
> > -I/include/linux -c MessagesTestCase.cpp
> > -Wp,-MD,.deps/MessagesTestCase.TPlo  -fPIC -DPIC
> -o
> > .libs/MessagesTestCase.o
> > g++: Internal compiler error: program cc1plus got
> fatal signal 9
> > make[4]: *** [MessagesTestCase.lo] Error 1
> > make[4]: Leaving directory
> `/home/leanne/quickfix/src/C++/test'
> > make[3]: *** [all-recursive] Error 1
> > make[3]: Leaving directory
> `/home/leanne/quickfix/src/C++'
> > make[2]: *** [all-recursive] Error 1
> > make[2]: Leaving directory
> `/home/leanne/quickfix/src'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/home/leanne/quickfix'
> > make: *** [all] Error 2
> > 
> > 
> > 
> > 
> > 
> >
>
-------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux
> Tutorials
> > Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> > GenToo technologies. Learn everything from
> fundamentals to system
> >
>
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> > _______________________________________________
> > Quickfix-developers mailing list
> > Qui...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> > 
> > 
> > 
> > 
> >
>
-------------------------------------------------------
> > This SF.Net email is sponsored by: IBM Linux
> Tutorials
> > Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> > GenToo technologies. Learn everything from
> fundamentals to system
> >
>
administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
> > _______________________________________________
> > Quickfix-developers mailing list
> > Qui...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux
> Tutorials
> Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> GenToo technologies. Learn everything from
> fundamentals to system
>
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
>
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

RE: [Quickfix-developers] Compiling Error - Linux Solution

[Leanne T. S. <le...@en...>]

Oren - 

Do you happen to know the minimal RAM & virtual memory needed to compile
quickfix? I'd rather compile quickfix in production mode.

Here are my RAM & virtual memory stats.

08:15:47 up 13 days, 15:50,  1 user,  load average: 0.00, 0.24, 0.34
42 processes: 41 sleeping, 1 running, 0 zombie, 0 stopped
CPU states:   0.4% user,   0.2% system,   0.0% nice,  99.4% idle
Mem:    124700K total,   113160K used,    11540K free,    25276K buffers
Swap:   305224K total,    22728K used,   282496K free,    33584K cached

I set CXXFLAGS="-O0" where it was originally set to CXXFLAGS="-g" and
re-ran ./configure. I'm still unable to compile. Any ideas?

Thanks!
 

On Wed, 2004-03-17 at 01:41, Miller, Oren wrote:
> Leanne,
> 
> I believe when this happens it generally means that g++ doesn't have enough memory available to it.  Any idea how much ram and virtual memory you have allocated to that box?
> 
> One thing you can try without messing around with any of that stuff is to turn off compiler optimizations.  This should lessen the memory requirement.  Just set the CXXFLAGS environment variable to -O0 and run ./configure and make again.  See if that pulls you through the compilation with your current configuration.
> 
> You probably won't want to run in production with that build but it will at least get you up and running while you resolve the memory issue.
> 
> --oren
> 
> -----Original Message-----
> From:	Leanne T. Smith [mailto:le...@en...]
> Sent:	Tue 3/16/2004 4:01 PM
> To:	qui...@li...
> Cc:	
> Subject:	[Quickfix-developers] Compiling Error - Linux Solution
> I'm receiving a g++ compiling error for QuickFIX on Linux. I followed
> the Installation Documentation, so I'm not sure I could be missing. I've
> attached the error below. Please let me know if you have any idea what I
> might be overlooking. Thanks.
> 
> 
> lea@fla:~/quickfix$ make
> make  all-recursive
> make[1]: Entering directory `/home/leanne/quickfix'
> Making all in src
> make[2]: Entering directory `/home/leanne/quickfix/src'
> Making all in C++
> make[3]: Entering directory `/home/leanne/quickfix/src/C++'
> Making all in test
> make[4]: Entering directory `/home/leanne/quickfix/src/C++/test'
> source='MessagesTestCase.cpp' object='MessagesTestCase.lo' libtool=yes \
> depfile='.deps/MessagesTestCase.Plo'
> tmpdepfile='.deps/MessagesTestCase.TPlo' \
> depmode=gcc /bin/sh ../../../depcomp \
> /bin/sh ../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I.
> -I../../.. -I..    -g -O2 -Wall   -I/usr/include/libxml2/libxml
> -I/usr/include/libxml2 -I/include -I/include/linux -c -o
> MessagesTestCase.lo `test -f 'MessagesTestCase.cpp' || echo
> './'`MessagesTestCase.cpp
>  g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I.. -g -O2 -Wall
> -I/usr/include/libxml2/libxml -I/usr/include/libxml2 -I/include
> -I/include/linux -c MessagesTestCase.cpp
> -Wp,-MD,.deps/MessagesTestCase.TPlo  -fPIC -DPIC -o
> .libs/MessagesTestCase.o
> g++: Internal compiler error: program cc1plus got fatal signal 9
> make[4]: *** [MessagesTestCase.lo] Error 1
> make[4]: Leaving directory `/home/leanne/quickfix/src/C++/test'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/home/leanne/quickfix/src/C++'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/leanne/quickfix/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/leanne/quickfix'
> make: *** [all] Error 2
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers

RE: [Quickfix-developers] Compiling Error - Linux Solution

[Miller, O. <OM...@ri...>]

Leanne,

I believe when this happens it generally means that g++ doesn't have =
enough memory available to it.  Any idea how much ram and virtual memory =
you have allocated to that box?

One thing you can try without messing around with any of that stuff is =
to turn off compiler optimizations.  This should lessen the memory =
requirement.  Just set the CXXFLAGS environment variable to -O0 and run =
./configure and make again.  See if that pulls you through the =
compilation with your current configuration.

You probably won't want to run in production with that build but it will =
at least get you up and running while you resolve the memory issue.

--oren

-----Original Message-----
From:	Leanne T. Smith [mailto:le...@en...]
Sent:	Tue 3/16/2004 4:01 PM
To:	qui...@li...
Cc:=09
Subject:	[Quickfix-developers] Compiling Error - Linux Solution
I'm receiving a g++ compiling error for QuickFIX on Linux. I followed
the Installation Documentation, so I'm not sure I could be missing. I've
attached the error below. Please let me know if you have any idea what I
might be overlooking. Thanks.


lea@fla:~/quickfix$ make
make  all-recursive
make[1]: Entering directory `/home/leanne/quickfix'
Making all in src
make[2]: Entering directory `/home/leanne/quickfix/src'
Making all in C++
make[3]: Entering directory `/home/leanne/quickfix/src/C++'
Making all in test
make[4]: Entering directory `/home/leanne/quickfix/src/C++/test'
source=3D'MessagesTestCase.cpp' object=3D'MessagesTestCase.lo' =
libtool=3Dyes \
depfile=3D'.deps/MessagesTestCase.Plo'
tmpdepfile=3D'.deps/MessagesTestCase.TPlo' \
depmode=3Dgcc /bin/sh ../../../depcomp \
/bin/sh ../../../libtool --mode=3Dcompile g++ -DHAVE_CONFIG_H -I. -I.
-I../../.. -I..    -g -O2 -Wall   -I/usr/include/libxml2/libxml
-I/usr/include/libxml2 -I/include -I/include/linux -c -o
MessagesTestCase.lo `test -f 'MessagesTestCase.cpp' || echo
'./'`MessagesTestCase.cpp
 g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I.. -g -O2 -Wall
-I/usr/include/libxml2/libxml -I/usr/include/libxml2 -I/include
-I/include/linux -c MessagesTestCase.cpp
-Wp,-MD,.deps/MessagesTestCase.TPlo  -fPIC -DPIC -o
.libs/MessagesTestCase.o
g++: Internal compiler error: program cc1plus got fatal signal 9
make[4]: *** [MessagesTestCase.lo] Error 1
make[4]: Leaving directory `/home/leanne/quickfix/src/C++/test'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/leanne/quickfix/src/C++'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/leanne/quickfix/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/leanne/quickfix'
make: *** [all] Error 2





-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Quickfix-developers] Compiling Error - Linux Solution

[Leanne T. S. <le...@en...>]

I'm receiving a g++ compiling error for QuickFIX on Linux. I followed
the Installation Documentation, so I'm not sure I could be missing. I've
attached the error below. Please let me know if you have any idea what I
might be overlooking. Thanks.


lea@fla:~/quickfix$ make
make  all-recursive
make[1]: Entering directory `/home/leanne/quickfix'
Making all in src
make[2]: Entering directory `/home/leanne/quickfix/src'
Making all in C++
make[3]: Entering directory `/home/leanne/quickfix/src/C++'
Making all in test
make[4]: Entering directory `/home/leanne/quickfix/src/C++/test'
source='MessagesTestCase.cpp' object='MessagesTestCase.lo' libtool=yes \
depfile='.deps/MessagesTestCase.Plo'
tmpdepfile='.deps/MessagesTestCase.TPlo' \
depmode=gcc /bin/sh ../../../depcomp \
/bin/sh ../../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I.
-I../../.. -I..    -g -O2 -Wall   -I/usr/include/libxml2/libxml
-I/usr/include/libxml2 -I/include -I/include/linux -c -o
MessagesTestCase.lo `test -f 'MessagesTestCase.cpp' || echo
'./'`MessagesTestCase.cpp
 g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I.. -g -O2 -Wall
-I/usr/include/libxml2/libxml -I/usr/include/libxml2 -I/include
-I/include/linux -c MessagesTestCase.cpp
-Wp,-MD,.deps/MessagesTestCase.TPlo  -fPIC -DPIC -o
.libs/MessagesTestCase.o
g++: Internal compiler error: program cc1plus got fatal signal 9
make[4]: *** [MessagesTestCase.lo] Error 1
make[4]: Leaving directory `/home/leanne/quickfix/src/C++/test'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/leanne/quickfix/src/C++'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/leanne/quickfix/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/leanne/quickfix'
make: *** [all] Error 2

Re: [Quickfix-developers] Double logout sent

[Apichat B. <sar...@ly...>]

Oren,
    Thanks for answer. The new features sound very good to me. I will check out the cvs version.
    However, I believe my client will not be comfortable with the non-release product. Could you give the estimate time for the release of 1.7.1 please?

Thanks,
Apichat

---
_____________________________
Apichat Banyatsupasil
Director of Software Development
Intelligent Brain Consulting Co., Ltd.
287/23-24 Surawong Rd 2nd Fl,
Suriyawong, Bangrak,
Bangkok 10500
Thailand
Office +66 (2) 635-7655, +66 (2) 635-6702
Fax  +66 (2) 635-7603
Cell +66 (9) 131-4009
URL  http://www.intelligentbrain.com








--------- Original Message ---------

DATE: Mon, 15 Mar 2004 22:22:58
From: Oren Miller <ore...@ya...>
To: sar...@ly..., qui...@li...
Cc: 

>Support for proper logoff is really the one of two
>important pieces of functionality missing from current
>releases of QuickFIX.  The bad news is that 1.7.0
>suffers from this same issue.  The good news is that
>supports for this functionality is currently available
>in the CVS repository.  We plan on doing a 1.7.1
>release with this feature as well as support for
>variable length sessions.
>
>If you would like proper support for logout's, I would
>suggest going with the CVS version.  Logout's are done
>either explicitly by calling the logoff() method on
>the session.  Calling logon will bring the session
>back on line.  Also, when calling stop on the
>initiator and acceptor, all open sessions will go
>through a proper logoff sequence before QuickFIX shuts
>down.
>
>--oren
>
>--- Apichat Banyatsupasil <sar...@ly...> wrote:
>> Hi,
>>    I currently use QuickFix 1.7.0, java version. I
>> have problem that when I try to send logout message,
>> the second logout is also sent automatically by
>> QuickFIX. This seems to be the same problem as 
>>
>http://sourceforge.net/mailarchive/message.php?msg_id=6306713
>> and
>>
>http://sourceforge.net/mailarchive/message.php?msg_id=6314798
>> 
>> however, none of them provide solutions. They
>> provide only workaround which could bring another
>> problem.
>> 
>> Could anyone help me with this please?
>> 
>> Thanks,
>> Apichat
>> _____________________________
>> Apichat Banyatsupasil
>> Director of Software Development
>> Intelligent Brain Consulting Co., Ltd.
>> 287/23-24 Surawong Rd 2nd Fl,
>> Suriyawong, Bangrak,
>> Bangkok 10500
>> Thailand
>> Office +66 (2) 635-7655, +66 (2) 635-6702
>> Fax  +66 (2) 635-7603
>> Cell +66 (9) 131-4009
>> URL  http://www.intelligentbrain.com
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>____________________________________________________________
>> Find what you are looking for with the Lycos Yellow
>> Pages
>>
>http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
>> 
>> 
>>
>-------------------------------------------------------
>> This SF.Net email is sponsored by: IBM Linux
>> Tutorials
>> Free Linux tutorial presented by Daniel Robbins,
>> President and CEO of
>> GenToo technologies. Learn everything from
>> fundamentals to system
>>
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>> _______________________________________________
>> Quickfix-developers mailing list
>> Qui...@li...
>>
>https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Mail - More reliable, more storage, less spam
>http://mail.yahoo.com
>



____________________________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10

RE: [Quickfix-developers] Handling FIX Messages From An External Source

[Dahl, J. <JD...@cm...>]

Well, that is basically what I am doing. I'm using the Message class for
extraction.

Just wanted to know if there was anything else I should be using when
dealing with
an external FIX message.

JD

-----Original Message-----
From: Miller, Oren [mailto:OM...@ri...]=20
Sent: Tuesday, March 16, 2004 8:40 AM
To: Dahl, Jon; qui...@li...
Subject: Re: [Quickfix-developers] Handling FIX Messages From An
External Source


Hmm,

Can't you just make a copy of the ExecutionReport message, lookup the
clordid, set the correct sender and target compids and send it along to
the client?

--oren

--------------------------
Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: Dahl, Jon <JD...@cm...>
To: qui...@li...
<qui...@li...>
Sent: Mon Mar 15 10:45:08 2004
Subject: [Quickfix-developers] Handling FIX Messages From An External
Source

Currently, we are writing an Order Entry Gateway that will handle
requests from clients and forward the message off to the engine in FIX
Format. Execution Report Messages will be returned in FIX format as
well.

The response message from the engine will not have correct SenderCompID
and TargetCompID fields in it. So I will need to be able to extract
fields from the message and place them in a valid ExecutionReport
message to be sent off to the correct client. I will be returned the
original ClOrdID from the engine so there shouldn't be a problem
returning it to the correct client if I cache requests.

My biggest ? is having the ability to parse the ExecutionReport message
for fields to build the ExecutionReport message being sent back to the
client. Right now, it looks like the Message class is the place to
start. Anyone else have any suggestions how to parse the fields out?
Would MessageCracker blow up if the SenderCompID and TargetCompID are
not a valid Session connected?

Thanks,

JD

P.S. - Kudos on the new website(http://www.quickfixengine.org).


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

Re: [Quickfix-developers] Handling FIX Messages From An External Source

[Miller, O. <OM...@ri...>]

Hmm,

Can't you just make a copy of the ExecutionReport message, lookup the =
clordid, set the correct sender and target compids and send it along to =
the client?

--oren

--------------------------
Sent from my BlackBerry Wireless Handheld


-----Original Message-----
From: Dahl, Jon <JD...@cm...>
To: qui...@li... =
<qui...@li...>
Sent: Mon Mar 15 10:45:08 2004
Subject: [Quickfix-developers] Handling FIX Messages From An External =
Source

Currently, we are writing an Order Entry Gateway that will handle
requests from clients
and forward the message off to the engine in FIX Format. Execution
Report Messages will
be returned in FIX format as well.

The response message from the engine will not have correct SenderCompID
and TargetCompID
fields in it. So I will need to be able to extract fields from the
message and place them
in a valid ExecutionReport message to be sent off to the correct client.
I will be returned
the original ClOrdID from the engine so there shouldn't be a problem
returning it to the
correct client if I cache requests.

My biggest ? is having the ability to parse the ExecutionReport message
for fields to build
the ExecutionReport message being sent back to the client. Right now, it
looks like the
Message class is the place to start. Anyone else have any suggestions
how to parse the fields
out? Would MessageCracker blow up if the SenderCompID and TargetCompID
are not a valid Session
connected?

Thanks,

JD

P.S. - Kudos on the new website(http://www.quickfixengine.org).


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=3Dick
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Quickfix-developers] out of sequence numbers

[Vijay S. Y. <vy...@op...>]

SGVsbG8gQWxsLA0KIEkgYW0gd3JpdGluZyBhbiBvcmRlciByb3V0aW5nIGdhdGV3YXkgdGhhdCBj
b2xsZWN0cyBvcmRlcnMgZnJvbSB2YXJpb3VzIGNsaWVudHMgYW5kIHNlbmRzIHRoZW0gdG8gYSBG
SVggYWNjZXB0b3IgaS5lLiBJIGFtIHVzaW5nIHRoZSBRdWlja0ZpeCBpbml0aWF0b3IgaW4gbXkg
Y29kZS4gVGhlIGluaXRpYXRvciBzZW5kcyBtZXNzYWdlcyB0byB0aGUgYWNjZXB0b3Igb3V0IG9m
IHNlcXVlbmNlLiBUaGlzIGxlYWRzIHRvIHNlc3Npb24gdGVybWluYXRpb24gYW5kIGluY29ycmVj
dCBwcm9jZXNzaW5nLiBBbnkgaWRlYXMgYXJlIHdlbGNvbWUgYW5kIGFwcHJlY2lhdGVkLg0KIA0K
VGhhbmtzLA0KIA0KLS0gVmlqYXkNCiANCjg9RklYLjQuMQE5PTU5ATM1PUEBMzQ9MQE0OT1NRUhJ
ATUyPTIwMDQwMzE2LTE0OjEyOjA2ATU2PU9DT04BOTg9MAExMDg9MzABMTA9MTMxAQ0KDQo4PUZJ
WC40LjEBOT00NwEzNT0wATM0PTIBNDk9TUVISQE1Mj0yMDA0MDMxNi0xNDoxMjozOAE1Nj1PQ09O
ATEwPTA5MgENCg0KOD1GSVguNC4xATk9OTMBMzU9RAEzND0zATQ5PU1FSEkBNTI9MjAwNDAzMTYt
MTQ6MTI6NTIBNTY9T0NPTgExPU1RT1QBMTE9MwEyMT0xATM4PTEwMAE0MD0xATU0PQE1NT1NU0ZU
ATU5PTABMTA9MDUzAQ0KDQo4PUZJWC40LjEBOT01OQEzNT1BATM0PTUBNDk9TUVISQE1Mj0yMDA0
MDMxNi0xNDoxNDoxOAE1Nj1PQ09OATk4PTABMTA4PTMwATEwPTE0MAENCg0KOD1GSVguNC4xATk9
OTEBMzU9RAEzND02ATQ5PU1FSEkBNTI9MjAwNDAzMTYtMTQ6MTQ6MzgBNTY9T0NPTgExPU1RT1QB
MTE9NQEyMT0xATM4PTEBNDA9MQE1ND0BATU1PVNQWAE1OT0wATEwPTE2MAENCg0KOD1GSVguNC4x
ATk9MTIwATM1PUQBMzQ9MwE0Mz1ZATQ5PU1FSEkBNTI9MjAwNDAzMTYtMTQ6MTQ6NDIBNTY9T0NP
TgExMjI9MjAwNDAzMTYtMTQ6MTI6NTIBMT1NUU9UATExPTMBMjE9MQEzOD0xMDABNDA9MQE1ND0B
NTU9TVNGVAE1OT0wATEwPTE0MgENCg0KOD1GSVguNC4xATk9OTIBMzU9RAEzND03ATQ5PU1FSEkB
NTI9MjAwNDAzMTYtMTQ6MTQ6NDIBNTY9T0NPTgExPU1RT1QBMTE9NgEyMT0xATM4PTEyATQwPTEB
NTQ9AQE1NT1TUFgBNTk9MAExMD0yMDgBDQoNCjg9RklYLjQuMQE5PTYwATM1PUEBMzQ9MTABNDk9
TUVISQE1Mj0yMDA0MDMxNi0xNDoxNDo1MQE1Nj1PQ09OATk4PTABMTA4PTMwATEwPTE3MwENCiAN
CkFzIHlvdSBjYW4gc2VlIHNlcXVlbmNlIG51bWJlcnMgMS0zIHdlcmUgc2VudCBpbiBvcmRlci4g
U2VxdWVuY2UgbnVtYmVyIDQgaXMgbWlzc2luZyBhbmQgc2VxdWVuY2UgbnVtYmVyIDMgaXMgcmVz
ZW50IGFmdGVyIHNlcXVlbmNlIDYuIFNlcXVlbmNlIDggYW5kIDkgYXJlIG1pc3NpbmcuDQogDQpJ
IGFtIHBhc2luZyBDIyBjb2RlIGJlbG93IChJIGhhdmUgc3RyaXBwZWQgb2ZmIHRoZSB0cnkvY2F0
Y2ggYmxvY2tzIGZvciBicmV2aXR5J3Mgc2FrZSkNCiANCm5hbWVzcGFjZSBJTVRDX0ZJWEluaXRp
YXRvcg0Kew0KIGNsYXNzIEV4ZWN1dG9yDQogew0KICBwcml2YXRlIFNvY2tldEluaXRpYXRvciBt
X2luaXRpYXRvcjsNCiAgcHJpdmF0ZSBUaHJlYWQgV29ya2VyVGhyZWFkOw0KICBwdWJsaWMgRXhl
Y3V0b3IoKQ0KICB7DQogIH0NCiAgcHVibGljIHZvaWQgR28oKQ0KICB7DQogICAgU2Vzc2lvblNl
dHRpbmdzIHNldHRpbmdzID0gbmV3IFNlc3Npb25TZXR0aW5ncygiT0NPTk5FUi5DRkciKTsNCiAg
ICBBcHBsaWNhdGlvbiBhcHBsaWNhdGlvbiA9IG5ldyBBcHBsaWNhdGlvbigpOw0KICAgIEZpbGVT
dG9yZUZhY3RvcnkgZmFjdG9yeSA9IG5ldyBGaWxlU3RvcmVGYWN0b3J5KHNldHRpbmdzKTsNCiAg
ICBGaWxlTG9nRmFjdG9yeSBsb2dGYWN0b3J5ID0gbmV3IEZpbGVMb2dGYWN0b3J5KCJvdXRwdXQi
KTsNCiAgICBNZXNzYWdlRmFjdG9yeSBtZXNzYWdlRmFjdG9yeSA9IG5ldyBEZWZhdWx0TWVzc2Fn
ZUZhY3RvcnkoKTsNCiAgICBtX2luaXRpYXRvciA9IG5ldyBTb2NrZXRJbml0aWF0b3IgKGFwcGxp
Y2F0aW9uLA0KICAgICAgICAgICAgICAgIGZhY3RvcnksIA0KICAgICAgICAgICAgICAgIHNldHRp
bmdzLA0KICAgICAgICAgICAgICAgIGxvZ0ZhY3RvcnksDQogICAgICAgICAgICAgICAgbWVzc2Fn
ZUZhY3RvcnkpOw0KICAgIG1faW5pdGlhdG9yLnN0YXJ0KCk7DQogICAgQ29uc29sZS5Xcml0ZUxp
bmUgKCJJbml0aWF0b3Igc3RhcnRlZCIpOw0KICAgIHdoaWxlICghYXBwbGljYXRpb24uSXNDb25u
ZWN0ZWQoKSkNCiAgICB7DQogICAgIENvbnNvbGUuV3JpdGVMaW5lICgiV2FpdGluZyB0byBlc3Rh
Ymxpc2ggYSBjb25uZWN0aW9uIHdpdGggRklYIHNlcnZlciIpOw0KICAgICBUaHJlYWQuU2xlZXAo
MTAwKTsNCiAgICB9DQogICAgUHJvY2Vzc09yZGVycygpOw0KDQogIH0NCiAgcHVibGljIHZvaWQg
U3RvcCgpIHttX2luaXRpYXRvci5zdG9wKCk7fQ0KICBwcml2YXRlIHZvaWQgUHJvY2Vzc09yZGVy
cygpDQogIHsNCiAgIFNxbENvbm5lY3Rpb24gQ29ubj1uZXcgU3FsQ29ubmVjdGlvbigpOw0KICAg
Q29ubi5Db25uZWN0aW9uU3RyaW5nPSJEYXRhIFNvdXJjZT0xMC42MC4wLjEwNDsgSW50ZWdyYXRl
ZCBTZWN1cml0eT1TU1BJOyIgKw0KICAgICJJbml0aWFsIENhdGFsb2c9aW10OyB1aWQ9c2E7cHdk
PTtDb25uZWN0IFRpbWVvdXQ9NSI7DQogICAgICAgDQogICBTcWxDb21tYW5kIG15Q01EPW5ldyBT
cWxDb21tYW5kKCk7DQogICBteUNNRC5Db21tYW5kVHlwZT1Db21tYW5kVHlwZS5TdG9yZWRQcm9j
ZWR1cmU7DQogICBteUNNRC5Db21tYW5kVGV4dD0iR2V0T3JkZXJzIjsgDQogICBteUNNRC5Db25u
ZWN0aW9uPUNvbm47DQogICBteUNNRC5QYXJhbWV0ZXJzLkFkZCgiQGNPcmRlclN0YXR1cyIsU3Fs
RGJUeXBlLkNoYXIsMSkuVmFsdWU9J04nOw0KICAgDQogICBTcWxEYXRhQWRhcHRlciBkYTsNCiAg
IGRhPW5ldyBTcWxEYXRhQWRhcHRlcigpOw0KICAgZGEuU2VsZWN0Q29tbWFuZD1teUNNRDsNCiAg
IERhdGFTZXQgZHM9bmV3IERhdGFTZXQoKTsNCiAgIENvbm4uT3BlbigpOw0KICAgd2hpbGUodHJ1
ZSkNCiAgIHsNCiAgICAgZGEuRmlsbChkcyk7DQogICAgIENvbm4uQ2xvc2UoKTsNCiAgICAgRGF0
YVJvd1tdY3VyclJvd3M9ZHMuVGFibGVzWzBdLlNlbGVjdChudWxsLG51bGwsRGF0YVZpZXdSb3dT
dGF0ZS5DdXJyZW50Um93cyk7DQogICAgIGZvcmVhY2goRGF0YVJvdyBteVJvdyBpbiBjdXJyUm93
cykNCiAgICB7DQogICAgICBDb25zb2xlLldyaXRlTGluZSgiU3VibWl0dGluZyBvcmRlciB3aXRo
IGNsaWVudCBvcmRlciBpZCA9ICIrbXlSb3dbIm9yZGVyaWQiXSk7DQogICAgICBTZW5kT3JkZXIo
Q29udmVydC5Ub0ludDMyKG15Um93WyJvcmRlcmlkIl0pLA0KICAgICAgIENvbnZlcnQuVG9TdHJp
bmcobXlSb3dbInN5bWJvbCJdKSwNCiAgICAgICBDb252ZXJ0LlRvQ2hhcihteVJvd1sib3JkZXJz
aWRlIl0pLA0KICAgICAgIENvbnZlcnQuVG9JbnQzMihteVJvd1sicXR5Il0pKTsNCiAgICB9DQog
ICAgQ29uc29sZS5Xcml0ZSgiTm8gbmV3IG9yZGVycyB0byBiZSBzdWJtaXR0ZWQiKTsNCiAgICAg
DQogICB9DQogIH0NCiAgDQogICANCiAgDQogIHB1YmxpYyB2b2lkIFNlbmRPcmRlcihpbnQgb2lk
LHN0cmluZyBvc3ltLGNoYXIgb3NkLGludCBvcXR5KQ0KICB7DQogICBNZXNzYWdlIG9yZGVyOw0K
ICAgU2lkZSBzaWRlOw0KICAgQ2xPcmRJRCBpZD1uZXcgQ2xPcmRJRChvaWQuVG9TdHJpbmcoKSk7
DQogICBIYW5kbEluc3QgaW5zdD1uZXcgSGFuZGxJbnN0KEhhbmRsSW5zdC5BVVRPTUFURURfRVhF
Q1VUSU9OX09SREVSX1BSSVZBVEUpOw0KICAgU3ltYm9sIHN5bT1uZXcgU3ltYm9sKG9zeW0pOw0K
ICAgU2lkZSBzZD1uZXcgU2lkZShvc2QpOw0KICAgT3JkVHlwZSBvdHlwPW5ldyBPcmRUeXBlKE9y
ZFR5cGUuTUFSS0VUKTsNCiAgIFF1aWNrRml4NDEuTmV3T3JkZXJTaW5nbGUgbmV3T3JkZXJTaW5n
bGU9bmV3IFF1aWNrRml4NDEuTmV3T3JkZXJTaW5nbGUoaWQsaW5zdCxzeW0sc2Qsb3R5cCk7DQog
ICANCiAgIG5ld09yZGVyU2luZ2xlLnNldChuZXcgQWNjb3VudCgiTVFPVCIpKTsNCiAgIG5ld09y
ZGVyU2luZ2xlLnNldChuZXcgT3JkZXJRdHkob3F0eSkpOw0KICAgbmV3T3JkZXJTaW5nbGUuc2V0
KG5ldyBUaW1lSW5Gb3JjZShUaW1lSW5Gb3JjZS5EQVkpKTsNCiAgIG5ld09yZGVyU2luZ2xlLmdl
dEhlYWRlcigpLnNldEZpZWxkKG5ldyBTZW5kZXJDb21wSUQoIk1FSEkiKSk7DQogICBuZXdPcmRl
clNpbmdsZS5nZXRIZWFkZXIoKS5zZXRGaWVsZChuZXcgVGFyZ2V0Q29tcElEKCJPQ09OIikpOw0K
ICANCiAgIG9yZGVyID0gbmV3T3JkZXJTaW5nbGU7DQogICBTZXNzaW9uLnNlbmRUb1RhcmdldChv
cmRlcik7DQogIH0NCiB9DQp9DQoNCiANCg==

Re: [Quickfix-developers] Double logout sent

[Oren M. <ore...@ya...>]

Support for proper logoff is really the one of two
important pieces of functionality missing from current
releases of QuickFIX.  The bad news is that 1.7.0
suffers from this same issue.  The good news is that
supports for this functionality is currently available
in the CVS repository.  We plan on doing a 1.7.1
release with this feature as well as support for
variable length sessions.

If you would like proper support for logout's, I would
suggest going with the CVS version.  Logout's are done
either explicitly by calling the logoff() method on
the session.  Calling logon will bring the session
back on line.  Also, when calling stop on the
initiator and acceptor, all open sessions will go
through a proper logoff sequence before QuickFIX shuts
down.

--oren

--- Apichat Banyatsupasil <sar...@ly...> wrote:
> Hi,
>    I currently use QuickFix 1.7.0, java version. I
> have problem that when I try to send logout message,
> the second logout is also sent automatically by
> QuickFIX. This seems to be the same problem as 
>
http://sourceforge.net/mailarchive/message.php?msg_id=6306713
> and
>
http://sourceforge.net/mailarchive/message.php?msg_id=6314798
> 
> however, none of them provide solutions. They
> provide only workaround which could bring another
> problem.
> 
> Could anyone help me with this please?
> 
> Thanks,
> Apichat
> _____________________________
> Apichat Banyatsupasil
> Director of Software Development
> Intelligent Brain Consulting Co., Ltd.
> 287/23-24 Surawong Rd 2nd Fl,
> Suriyawong, Bangrak,
> Bangkok 10500
> Thailand
> Office +66 (2) 635-7655, +66 (2) 635-6702
> Fax  +66 (2) 635-7603
> Cell +66 (9) 131-4009
> URL  http://www.intelligentbrain.com
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
____________________________________________________________
> Find what you are looking for with the Lycos Yellow
> Pages
>
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux
> Tutorials
> Free Linux tutorial presented by Daniel Robbins,
> President and CEO of
> GenToo technologies. Learn everything from
> fundamentals to system
>
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
>
https://lists.sourceforge.net/lists/listinfo/quickfix-developers


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

[Quickfix-developers] Handling FIX Messages From An External Source

[Dahl, J. <JD...@cm...>]

Currently, we are writing an Order Entry Gateway that will handle
requests from clients
and forward the message off to the engine in FIX Format. Execution
Report Messages will
be returned in FIX format as well.

The response message from the engine will not have correct SenderCompID
and TargetCompID
fields in it. So I will need to be able to extract fields from the
message and place them
in a valid ExecutionReport message to be sent off to the correct client.
I will be returned
the original ClOrdID from the engine so there shouldn't be a problem
returning it to the
correct client if I cache requests.

My biggest ? is having the ability to parse the ExecutionReport message
for fields to build
the ExecutionReport message being sent back to the client. Right now, it
looks like the
Message class is the place to start. Anyone else have any suggestions
how to parse the fields
out? Would MessageCracker blow up if the SenderCompID and TargetCompID
are not a valid Session
connected?

Thanks,

JD

P.S. - Kudos on the new website(http://www.quickfixengine.org).

[Quickfix-developers] Double logout sent

[Apichat B. <sar...@ly...>]

Hi,
   I currently use QuickFix 1.7.0, java version. I have problem that when I try to send logout message, the second logout is also sent automatically by QuickFIX. This seems to be the same problem as 
http://sourceforge.net/mailarchive/message.php?msg_id=6306713
and
http://sourceforge.net/mailarchive/message.php?msg_id=6314798

however, none of them provide solutions. They provide only workaround which could bring another problem.

Could anyone help me with this please?

Thanks,
Apichat
_____________________________
Apichat Banyatsupasil
Director of Software Development
Intelligent Brain Consulting Co., Ltd.
287/23-24 Surawong Rd 2nd Fl,
Suriyawong, Bangrak,
Bangkok 10500
Thailand
Office +66 (2) 635-7655, +66 (2) 635-6702
Fax  +66 (2) 635-7603
Cell +66 (9) 131-4009
URL  http://www.intelligentbrain.com










____________________________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10

Re: [Quickfix-developers] Incoming Message Log

[Oren M. <ore...@ya...>]

Martin,

The log currently doesn't server this purpose.  The
logging in QuickFIX is rather primitive, and is
intended for plain old logging as opposed to data
storage.

If you do want to use the logs in this manner, you
would have to write something yourself.  This would be
easy to do as you can just use the Message class to
parse each line for you.  So you essentially need to
read a line, pass it into the message along with the
sessions data dictionary, and then you will have
everything.

This is a little risky to do with logs.  If you do
this you will have to make sure to clear the logs
everyday, otherwise messages get appended and you will
have stale orders from the previous day.  You may want
to consider just storing messages of interest coming
from the fromApp callback instead of relying on the
logs, who'se implementation may change in the future. 
For instance we have discussed combining the incoming
and outgoing logs into one file so the sequence of
message processing can be accurately viewed.

--oren

--- "Martin.Derkenne" <mar...@ac...>
wrote:
> Hi,
>  
> It would be very convenient for me to access the log
> file for the
> incoming message stream. This would allow me to
> build up a picture of
> the trades and orders present for a user during the
> trading day (where a
> client reconnects to a cut-down FIX 4.1 server)
>  
> It seems that there is currently no programmatic way
> to really access
> the contents of the incoming log file - it is
> hidden. I can fetch
> messages from the store, but not from the log. 
>  
> The question is to customize or not. Have I missed a
> path to request the
> QuickFIx library to fetch these log messages for me,
> or do I need to
> implement my own specialty class? I suspect the
> latter. 
>  
> Any comments appreciated
>  
> Martin Derkenne
> 

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com

Re: [Quickfix-developers] Fault Tolerance; Sybase/Oracle

[Oren M. <ore...@ya...>]

QuickFIX doesn't have any mechanisms to act as a fault
tolerant server.  Being a core implementation of a FIX
engine, it trys to excel in this aspect as opposed to
trying to reimplement such things that others are
better equipped to produce.  Generally you can use
third party software that is especially designed for
these scenarios and integrate them with QuickFIX.  I
do not know if there is open source software that does
this, but would be interested to find out.  Creating
you're own fault tolerant system is also an option. 
Since such a thing would only need to meet you're
specific needs, it would only need to implement a
subset of what many systems provide.

As per Oracle/Sybase.  I know that several users have
done implementations of this, but so far none of them
have been contributed back to the project.  You can
either see if someone is willing to donate this, or
you will have to implement one yourself.  It's pretty
easy to do and can be done reusing much of the mysql
code.

--oren

--- "Verma, Sanjay" <SV...@Cr...> wrote:
> We need to run multiple instances of QuickFix so
> that if one fails,
> customers can fail-over to the other one. This seems
> like a common
> requirement. I would like to hear from others in the
> community about how
> have they tackled this problem. It seems that the
> two instances will have to
> share the message store. Is there any functionality
> available that
> facilitates this. 
> 
> Also, are there any plans to support databases other
> than MySQL for message
> store. We run Sybase/Oracle here and I was wondering
> if anyone has
> implemented a message store in one of these
> databases.
> 
> Thanks.
> 
> Sanjay Verma
> DISCLAIMER
> e-mail, and any attachments thereto, is intended
> only for use by the
> addressee(s) named herein and may contain legally
> privileged and/or
> confidential information. If you are not the
> intended recipient of this
> e-mail, you are hereby notified that any
> dissemination, distribution or
> copying of this e-mail, and any attachments thereto,
> is strictly prohibited.
> If you have received this e-mail in error, please
> immediately notify me and
> permanently delete the original and any copy of any
> e-mail and any printout
> thereof.
> 
> E-mail transmission cannot be guaranteed to be
> secure or error-free. The
> sender therefore does not accept liability for any
> errors or omissions in
> the contents of this message which arise as a result
> of e-mail transmission.
> REGARDING PRIVACY AND CONFIDENTIALITY
> Crown Financial Group may, at its discretion,
> monitor and review the content
> of all e-mail communications.
> 
> 

__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com

[Quickfix-developers] Incoming Message Log

[Martin.Derkenne <mar...@ac...>]

Hi,
=20
It would be very convenient for me to access the log file for the
incoming message stream. This would allow me to build up a picture of
the trades and orders present for a user during the trading day (where a
client reconnects to a cut-down FIX 4.1 server)
=20
It seems that there is currently no programmatic way to really access
the contents of the incoming log file - it is hidden. I can fetch
messages from the store, but not from the log.=20
=20
The question is to customize or not. Have I missed a path to request the
QuickFIx library to fetch these log messages for me, or do I need to
implement my own specialty class? I suspect the latter.=20
=20
Any comments appreciated
=20
Martin Derkenne

[Quickfix-developers] Fault Tolerance; Sybase/Oracle

[Verma, S. <SV...@Cr...>]

We need to run multiple instances of QuickFix so that if one fails,
customers can fail-over to the other one. This seems like a common
requirement. I would like to hear from others in the community about how
have they tackled this problem. It seems that the two instances will have to
share the message store. Is there any functionality available that
facilitates this. 

Also, are there any plans to support databases other than MySQL for message
store. We run Sybase/Oracle here and I was wondering if anyone has
implemented a message store in one of these databases.

Thanks.

Sanjay Verma
DISCLAIMER
e-mail, and any attachments thereto, is intended only for use by the
addressee(s) named herein and may contain legally privileged and/or
confidential information. If you are not the intended recipient of this
e-mail, you are hereby notified that any dissemination, distribution or
copying of this e-mail, and any attachments thereto, is strictly prohibited.
If you have received this e-mail in error, please immediately notify me and
permanently delete the original and any copy of any e-mail and any printout
thereof.

E-mail transmission cannot be guaranteed to be secure or error-free. The
sender therefore does not accept liability for any errors or omissions in
the contents of this message which arise as a result of e-mail transmission.
REGARDING PRIVACY AND CONFIDENTIALITY
Crown Financial Group may, at its discretion, monitor and review the content
of all e-mail communications.

RE: [Quickfix-developers] Linkage problems with VC++7 -- STL related

[bhuvana <bh...@ca...>]

Hello,

I am having trouble building the .Net version of the Quickfix
application.

I am getting the following types of errors when I try to build the
solution file of Quickfix:

1. In the references not able to find the path for the file
'quickfix_net'
2. C:\Documents and
Settings\bhuvana\Desktop\quickfix-1.7.0\quickfix\src\.NET\fix40\Allocati
on.cs(315): The type or namespace name 'Group' does not exist in the
class or namespace 'QuickFix' (are you missing an assembly reference?)
3. C:\Documents and
Settings\bhuvana\Desktop\quickfix-1.7.0\quickfix\src\.NET\fix40\Message.
cs(267): The type or namespace name 'Message' does not exist in the
class or namespace 'QuickFix' (are you missing an assembly reference?)


Thanks,
Bhuvana



-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of
Vijay Singh Yadav
Sent: Monday, March 08, 2004 4:32 PM
To: qui...@li...
Subject: [Quickfix-developers] Linkage problems with VC++7 -- STL
related

Hello All,
 I had a project in VC++ 6 that uses Quickfix and it worked flawlessly.
I have moved the code to VC++ 7 and I get the following errors. I am not
able to diagnose the problem. I am still using straight C++ API (i.e.
not .net)
=20
thanks,
=20
-- vijay
=20
----------
Linking...

LINK : warning LNK4075: ignoring '/EDITANDCONTINUE' due to
'/INCREMENTAL:NO' specification

quickfix_debug.lib(Acceptor.obj) : warning LNK4049: locally defined
symbol ??1logic_error@std@@UAE@XZ (public: virtual __thiscall
std::logic_error::~logic_error(void)) imported

quickfix_debug.lib(Dictionary.obj) : warning LNK4049: locally defined
symbol ??1logic_error@std@@UAE@XZ (public: virtual __thiscall
std::logic_error::~logic_error(void)) imported

quickfix_debug.lib(SessionFactory.obj) : warning LNK4049: locally
defined symbol ??1logic_error@std@@UAE@XZ (public: virtual __thiscall
std::logic_error::~logic_error(void)) imported

:

:

:

quickfix_debug.lib(Session.obj) : warning LNK4217: locally defined
symbol
??0logic_error@std@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allo
cator@D@2@@1@@Z (public: __thiscall std::logic_error::logic_error(class
std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> > const &)) imported in function "public:
__thiscall FIX::FieldConvertError::FieldConvertError(void)"
(??0FieldConvertError@FIX@@QAE@XZ)

quickfix_debug.lib(Message.obj) : warning LNK4049: locally defined
symbol
??0logic_error@std@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allo
cator@D@2@@1@@Z (public: __thiscall std::logic_error::logic_error(class
std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> > const &)) imported

quickfix_debug.lib(FieldMap.obj) : warning LNK4049: locally defined
symbol
??0logic_error@std@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allo
cator@D@2@@1@@Z (public: __thiscall std::logic_error::logic_error(class
std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> > const &)) imported

quickfix_debug.lib(Initiator.obj) : warning LNK4049: locally defined
symbol
??0logic_error@std@@QAE@ABV?$basic_string@DU?$char_traits@D@std@@V?$allo
cator@D@2@@1@@Z (public: __thiscall std::logic_error::logic_error(class
std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> > const &)) imported

quickfix_debug.lib(Acceptor.obj) : warning LNK4049: locally defined
symbol ??0logic_error@std@@QAE@ABV01@@Z (public: __thiscall
std::logic_error::logic_error(class std::logic_error const &)) imported

:

:

:

N=18HS^?X'u?=04 S +l=16.) ?? y=20
zThm? '^?t!
:(??!?h'-? +axwZ j[-?vh?kj =1Bm v,vw(? ??Z