Re: [Quickfix-developers] mixed up pasting - please look here for details
Brought to you by:
orenmnero
Menu
▾
▴
Re: [Quickfix-developers] mixed up pasting - please look here for details
|
From: <gar...@su...> - 2003-03-04 22:17:03
|
Here is the message as it is stored on the sending side (where it looks=
right)
8=3DFIX.4.2=019=3D414=0135=3DJ=0134=3D4=0149=3DFMRFITST=0152=3D20030304=
-22:06:54=0156=3DSTNMMTST=01
6=3D99.991667=0115=3DUSD=0122=3D1=0148=3DCUSIP=0153=3D1000000=0154=3D1=01=
55=3DFIXED=01
60=3D20030304-21:14:27=0170=3DAllocation: 0=0171=3D3=0173=3D1=0111=3DNO=
NREF=0137=3D155888=01
75=3D20030304=0178=3D1=0179=3DFCUSM=0180=3D1000000=01154=3D999916.67=01=
6604=3DPartAllocID:1=01
106=3DGECC=01118=3D100=01124=3D1=0132=3D1000000=0117=3D155888_20031404_=
161427=0131=3D3=01
6640=3D99.991667=01381=3D999916.67=016609=3DCP=016611=3D100=016613=3DMO=
NEYMARKET=016614=3D1=01
6629=3DMATURITY=016637=3D20030604=0110=3D038=01
Here is the message as it is stored in my incoming message store (on th=
e
side that it is wrong)
8=3DFIX.4.2=019=3D414=0135=3DJ=0134=3D4=0149=3DFMRFITST=0152=3D20030304=
-22:06:54=0156=3DSTNMMTST=01
6=3D99.991667=0111=3DNONREF=0115=3DUSD=0117=3D155888_20031404_161427=01=
22=3D1=0131=3D3=0132=3D1000000
=0137=3D155888=0148=3DCUSIP=0153=3D1000000=0154=3D1=0155=3DFIXED=0160=3D=
20030304-21:14:27=01
70=3DAllocation: 0=0171=3D3=0173=3D1=0175=3D20030304=0178=3D1=0179=3DFC=
USM=0180=3D1000000=01106=3DGECC=01
118=3D100=01124=3D1=01154=3D999916.67=01381=3D999916.67=016604=3DPartAl=
locID:1=016609=3DCP=01
6611=3D100=016613=3DMONEYMARKET=016614=3D1=016629=3DMATURITY=016637=3D2=
0030604=016640=3D99.991667
=0110=3D038=01
Here also is my fromApp implementation so you can see that I am printin=
g
out the xml of the trade before storing it:
public void fromApp(org.quickfix.Message message,
SessionID sessionID)
throws FieldNotFound, UnsupportedMessageType, IncorrectTagValue=
{
LogUtil.debug ("Message received (" + sessionID + ") type: " +
message.getClass() + "\n " + message.toXML());
storeIncomingMessage (message, sessionID);
crack((org.quickfix.Message) message, sessionID);
}
Gary Mui
Prescient Markets, Inc 914-989-3118 (W)
445 Hamilton Avenue 914-422-3693 (F)
White Plains, NY 10601
Please visit us at http://www.cpmarket.com
=
=
=20
Oren Miller <ore...@ya...> =
=
=20
Sent by: To: =
qui...@li..., =
=20
qui...@li...ur quic=
kfi...@li... =
=20
ceforge.net cc: =
=
=20
Subj=
ect: Re: [Quickfix-developers] mixed up pasting - please look here for =
=20
deta=
ils =
=20
03/04/03 05:10 PM =
=
=20
Please respond to omiller =
=
=20
=
=
=20
=
=
=20
Field order is generally not important, except when it
comes to repeating groups where it is very important.
If the fields get out of order somewhere, that would
cause a problem trying to parse the message.
If you are getting messages from the QF callback, and
the session is given the correct DataDictionary, then
the fields should be in the same order on both sides
(assuming you are using QF on both sides, other
engines may vary the order).
If you can post the string of the stored message that
may provide a clue.
--- gar...@su... wrote:
>
> Yes, the data dictionary is exactly the same as the
> working version.
>
> One of the things I was wondering was whether it
> mattered where the native
> libraries were compiled. Right now I am packaging
> all the native libraries
> (stdc++, quickfix, quickfix_jni, xml2, and stlport)
> on one machine and am
> including those in my deployment package. Is it a
> coincidence that the
> machine that this works for is the same machine the
> libraries were compiled
> on?
>
> Also, does the order of the fields as they appear in
> the message store have
> any indication as to the order that is used when
> parsing and generating the
> message? As I mentioned in a different thread, I
> have an Incoming message
> store where I store every message received by the
> FIX engine. When I look
> at the allocation message in that message store, it
> does appear that some
> of the fields are not in the same order as in the
> FileStore of the sending
> FIX engine. Could the saving of the message into
> another message store
> somehow corrupt the field order?
>
>
>
> Gary Mui
> Prescient Markets, Inc 914-989-3118 (W)
> 445 Hamilton Avenue 914-422-3693 (F)
> White Plains, NY 10601
>
> Please visit us at http://www.cpmarket.com
>
>
>
>
>
> Oren Miller
> <ore...@ya...>
>
>
> Sent by:
> To: gar...@su...,
> qui...@li...
>
> qui...@li...ur cc:
>
>
> ceforge.net
> Subject: Re: [Quickfix-developers]
> mixed up pasting - please look here for
>
> details
>
>
>
>
> 03/04/03 04:32 PM
>
>
> Please respond to omiller
>
>
>
>
>
>
>
>
>
>
>
> Did you copy your data dictionary over to the new
> machine? The data dictionary of the receiving
> application would need to have the proper groups
> defined.
>
> --- gar...@su... wrote:
> > Oops - please ignore the prior email. I mixed up
> > the pasting of the
> > messages....
> >
> >
> >
> >
> > I've run into a serious problem that I haven't
> been
> > able to figure out.
> >
> > In trying to send across allocation messages
> (which
> > contain groups), I am
> > able to successfully do so on my development
> > platform. When I move the
> > receiving FIX engine to another environment (same
> > class machine, same java
> > version, same OS version-solaris 8), the receiving
> > side is unable to parse
> > the allocation message correctly which causes the
> > processing to fail.
> >
> > My outgoing message appears to be right in its XML
> > form while the incoming
> > message does not show the repeating group entries.
> > I am also including the
> > 'raw' format as printed in the output:
> >
> > Does anyone have any suggestions as to how to
> > proceed resolving this
> > problem? This is now holding up our UAT and
> > production release schedules.
> >
> > Thanks for any help,
> > Gary
> >
> > Outgoing
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
> > <20030304-20:12:54, FIX.4.2:FMRFITST->STNMMTST,
> > outgoing>
> >
> >
>
(8=3DFIX.4.2^A9=3D424^A35=3DJ^A34=3D474^A49=3DFMRFITST^A52=3D20030304-2=
0:12:56^A56=3DSTNMMTST^A6=3D99.991667^A15=3DUSD^A22=3D1^A48=3DCUSIP^A53=
=3D1000000^A54=3D1^A55=3DFIXED^A60=3D20030304-20:12:54^A70=3DAllocation=
:
>
> >
> >
>
0^A71=3D3^A73=3D1^A11=3DNONREF^A37=3D155882^A75=3D20030304^A78=3D1^A79=3D=
FCUSM^A80=3D1000000^A76=3DGECC^A154=3D999916.67^A6604=3DPartAllocID:1^A=
106=3DGECC^A118=3D100^A124=3D1^A32=3D1000000^A17=3D155882_20031204_1512=
54^A31=3D3^A6640=3D99.991667^A381=3D999916.67^A6609=3DCP^A6611=3D100^A6=
613=3DMONEYMARKET^A6614=3D1^A6629=3DMATURITY^A6637=3D20031204^A10=3D053=
^A)
>
> >
> >
> >
> > <message>
> > <header>
> > <field number=3D"8" value=3D"FIX.4.2"/>
> > <field number=3D"9" value=3D"372"/>
> > <field number=3D"35" value=3D"J"/>
> > </header>
> > <body>
> > <field number=3D"6" value=3D"99.991667"/>
> > <field number=3D"15" value=3D"USD"/>
> > <field number=3D"22" value=3D"1"/>
> > <field number=3D"48" value=3D"CUSIP"/>
> > <field number=3D"53" value=3D"1000000"/>
> > <field number=3D"54" value=3D"1"/>
> > <field number=3D"55" value=3D"FIXED"/>
> > <field number=3D"60" value=3D"20030304-20:12:54"/>
> > <field number=3D"70" value=3D"Allocation: 0"/>
> > <field number=3D"71" value=3D"3"/>
> > <field number=3D"73" value=3D"1"/>
> > <field number=3D"75" value=3D"20030304"/>
> > <field number=3D"78" value=3D"1"/>
> > <field number=3D"106" value=3D"GECC"/>
> > <field number=3D"118" value=3D"100"/>
> > <field number=3D"124" value=3D"1"/>
> > <field number=3D"381" value=3D"999916.67"/>
> > <field number=3D"6609" value=3D"CP"/>
> > <field number=3D"6611" value=3D"100"/>
> > <field number=3D"6613" value=3D"MONEYMARKET"/>
> > <field number=3D"6614" value=3D"1"/>
> > <field number=3D"6629" value=3D"MATURITY"/>
> > <field number=3D"6637" value=3D"20031204"/>
> > <group>
> > <field number=3D"11" value=3D"NONREF"/>
> > <field number=3D"37" value=3D"155882"/>
> > </group>
> > <group>
> > <field number=3D"79" value=3D"FCUSM"/>
> > <field number=3D"80" value=3D"1000000"/>
> > <field number=3D"76" value=3D"GECC"/>
> > <field number=3D"154" value=3D"999916.67"/>
> > <field number=3D"6604" value=3D"PartAllocID:1"/>
> > </group>
> > <group>
> > <field number=3D"32" value=3D"1000000"/>
> > <field number=3D"17"
> > value=3D"155882_20031204_151254"/>
> > <field number=3D"31" value=3D"3"/>
> > <field number=3D"6640" value=3D"99.991667"/>
> > </group>
> > </body>
> > <trailer>
> >
> >
> >
> >
> > Incoming
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > <20030304-20:12:56, FIX.4.2:STNMMTST->FMRFITST,
> > incoming>
> >
> >
>
(8=3DFIX.4.2^A9=3D424^A35=3DJ^A34=3D474^A49=3DFMRFITST^A52=3D20030304-2=
0:12:56^A56=3DSTNMMTST^A6=3D99.991667^A15=3DUSD^A22=3D1^A48=3DCUSIP^A53=
=3D1000000^A54=3D1^A55=3DFIXED^A60=3D20030304-20:12:54^A70=3DAllocation=
:
>
>
=3D=3D=3D message truncated =3D=3D=3D
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debu=
gger
for complex code. Debugging C/C++ programs can leave you feeling lost a=
nd
disoriented. TotalView can help you find your way. Available on major U=
NIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers
=
|
