[QFJ-614] CLONE - can not parse cme definition message from cme file Created: 07/Jul/11  Updated: 01/Apr/14  Resolved: 01/Apr/14

Status: Closed
Project: QuickFIX/J
Component/s: Engine
Affects Version/s: 1.4.0
Fix Version/s: None

Type: Other Priority: Default
Reporter: Jonathan Felch Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by QFJ-615 CLONE - can not parse cme definition ... Closed

 Description   

Hello;

I can not parse cme definition message from cme file from ftp://ftp.cme.com/secdef.dat.gz

code:

DataDictionary sessionDictionary, applicationDictionary;

sessionDictionary = new DataDictionary("FIXT11.xml");
applicationDictionary = new DataDictionary("FIX50.xml");

Message message = new Message();

boolean doValidation = false;

message.fromString(messageString, sessionDictionary,
applicationDictionary, doValidation);

sample cme input and quickfixj output:

INFO: messageString
1128=89=36835=d49=CME34=42552=2009100416001803515=BRL22=848=2086048155=BR:C0107=BR:DOLV09P002850200=200910202=2850207=XBMF461=OPECCS462=2562=5711=1311=[N/A]305=8309=20460001827=0864=2865=5866=200906261145=0865=7866=200909301145=210059000870=1871=24872=1947=BRL969=0.0011140=100001141=11022=GBX264=51142=F1151=BR:DOL1180=259787=19850=0.00110=165

INFO: message
9=15235=d34=42549=CME52=2009100416001803515=BRL22=848=2086048155=BR:C0107=BR:DOLV09P002850200=200910202=2850207=XBMF461=OPECCS462=2562=5711=110=128

thank you;

Andrei

 Comments   
Comment by Jonathan Felch [ 07/Jul/11 ]

This is the same issue as QFJ-478 but my account was unable to reopen the existing issue which is not resolved.

The latest build from trunk continues to fail on a large number of records and also continues to be missing field definitions... Technically this file should be depending on FIX 5 SP2, which may be part of the problem... My attempts to generate code for FIX 5 SP 2 were unsuccessful.

Comment by Christoph John [ 01/Apr/14 ]

We should now be able to handle FIX5.0 SP2 since QF/J 1.5.3. Unfortunately the link in the description is not reachable any longer (but the ticket is some years old).

Generated at Mon Nov 03 05:40:34 UTC 2025 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.