QuickFIX/J

A validation configuration to bypass checking of "Tag appears more than once"

Details

  • Type: New Feature New Feature
  • Status: Resolved Resolved
  • Priority: Default Default
  • Resolution: Won't Fix
  • Affects Version/s: 1.3.3
  • Fix Version/s: None
  • Component/s: Engine
  • Labels:
    None

Description

If the received message contains some custom repeating group, QFJ will reject with "Tag appears more than once" error. We had to customize the dictionary to work around. A configuration allowing bypass this will be helpful

Activity

Hide
Ali Asghar added a comment - 11/Feb/09 10:05 PM

I am a developer working on a FIX implementation using QuickFix/J version 1.4. I am getting an error "Tag appears more than once". The tag it is complaining about is 9013 (a custom repeating group). You mention on the forum the you had to customize the dictionary to work around. I am new to QuickFix/J and I am not sure how to customize the data dictionary. Could you please let me know how you customized the dictionary? I am using FIX 4.4. Thanks

Show
Ali Asghar added a comment - 11/Feb/09 10:05 PM I am a developer working on a FIX implementation using QuickFix/J version 1.4. I am getting an error "Tag appears more than once". The tag it is complaining about is 9013 (a custom repeating group). You mention on the forum the you had to customize the dictionary to work around. I am new to QuickFix/J and I am not sure how to customize the data dictionary. Could you please let me know how you customized the dictionary? I am using FIX 4.4. Thanks
Hide
Steve Bate added a comment - 03/Mar/09 7:08 AM

I don't know if you've found the information you want yet, but there is a description in the QFJ documentation. After reading that information, if you are still having problems please post a followup question.

Show
Steve Bate added a comment - 03/Mar/09 7:08 AM I don't know if you've found the information you want yet, but there is a description in the QFJ documentation. After reading that information, if you are still having problems please post a followup question.
Hide
Steve Bate added a comment - 03/Mar/09 7:10 AM

I changed this issue to a question, but it should remain a new feature request.

Show
Steve Bate added a comment - 03/Mar/09 7:10 AM I changed this issue to a question, but it should remain a new feature request.
Hide
Alvin Wang added a comment - 03/Mar/09 6:18 PM

Where can I find the description in QFJ doc? Could you provide a link?

Show
Alvin Wang added a comment - 03/Mar/09 6:18 PM Where can I find the description in QFJ doc? Could you provide a link?
Hide
Ganeshan Guruswamy added a comment - 25/Jun/09 3:47 PM

hi... we want a solution for same problem... "Tag appears more than once"

in my case the repeating tag is a user defined tag and want quickfix/j to ignore it...

please help

Show
Ganeshan Guruswamy added a comment - 25/Jun/09 3:47 PM hi... we want a solution for same problem... "Tag appears more than once" in my case the repeating tag is a user defined tag and want quickfix/j to ignore it... please help
Hide
Ali Asghar added a comment - 25/Jun/09 5:43 PM

This is a serious issue for us because we connect to Intercontinental Exchange (ICE) to receive trade data. ICE frequently adds new Custom Tags to their FIX messages and if that tag is not included in FIX44.xml then QuickFIX/J rejects messages. Even though in QuickFIX/J config file, I am setting

ValidateUserDefinedFields=N

This value should control quickfix behavior to control the user defined tag validation but it does not seem to be working.

I am using QuickFIX/J version 1.4?

Does any one know solution for this problem?

Show
Ali Asghar added a comment - 25/Jun/09 5:43 PM This is a serious issue for us because we connect to Intercontinental Exchange (ICE) to receive trade data. ICE frequently adds new Custom Tags to their FIX messages and if that tag is not included in FIX44.xml then QuickFIX/J rejects messages. Even though in QuickFIX/J config file, I am setting ValidateUserDefinedFields=N This value should control quickfix behavior to control the user defined tag validation but it does not seem to be working. I am using QuickFIX/J version 1.4? Does any one know solution for this problem?
Hide
Carey Bingham added a comment - 23/Sep/09 4:54 PM

This is also a serious issue for us for the saem reasons as Ali Asghar pointed out for ICE.

We are using the same version as well...We have turned off all validation but it seems to have no affect. Each time ICE adds custom tags or modifies the fix messages we get errors...The only solution is to revuild our dictionary and redploy the new generated classes.

Anyonw have a workaround? Or at least a fix implemented at this point.

ICE's cutover is of Nov 2 2009 and this is still a problem for us.

Show
Carey Bingham added a comment - 23/Sep/09 4:54 PM This is also a serious issue for us for the saem reasons as Ali Asghar pointed out for ICE. We are using the same version as well...We have turned off all validation but it seems to have no affect. Each time ICE adds custom tags or modifies the fix messages we get errors...The only solution is to revuild our dictionary and redploy the new generated classes. Anyonw have a workaround? Or at least a fix implemented at this point. ICE's cutover is of Nov 2 2009 and this is still a problem for us.
Hide
anton added a comment - 13/Oct/09 3:13 PM

The problem for many of us is important, so can anybody tell us how he has solved the problem?
Someone said that we should change the data dictionary, but how?
Someone said that there is a description about this in the documentation, but I didn't found anything.

Show
anton added a comment - 13/Oct/09 3:13 PM The problem for many of us is important, so can anybody tell us how he has solved the problem? Someone said that we should change the data dictionary, but how? Someone said that there is a description about this in the documentation, but I didn't found anything.
Hide
anton added a comment - 14/Oct/09 3:48 PM

In fact I was thinging its a bug because I was receiving tag appears more then once for tag(part of group) included in the dictionary that I am using.The problem was that some of the fields before the group were out of order,-when I fixed the dictionary the problem has been solved.
The strange here is that I was not receiving msg out of order(which sould be received when the order in group is wrong) and I didn't know that the problem is in the Order of the fields in the parent-group which contains the subgroup which contains the tag that repeats more then once.
So if you have a data dictionary which contains the correct groups and tags and you are receiving this message you can check the order of the tags, because it can cause message like the above one.
Hope it helps.

Tonko Lonko

Show
anton added a comment - 14/Oct/09 3:48 PM In fact I was thinging its a bug because I was receiving tag appears more then once for tag(part of group) included in the dictionary that I am using.The problem was that some of the fields before the group were out of order,-when I fixed the dictionary the problem has been solved. The strange here is that I was not receiving msg out of order(which sould be received when the order in group is wrong) and I didn't know that the problem is in the Order of the fields in the parent-group which contains the subgroup which contains the tag that repeats more then once. So if you have a data dictionary which contains the correct groups and tags and you are receiving this message you can check the order of the tags, because it can cause message like the above one. Hope it helps. Tonko Lonko
Hide
Dmitry added a comment - 22/Mar/10 12:13 PM

I use:

UseDataDictionary=Y
DataDictionary=FIX43.xml
ValidateUserDefinedFields=N
ValidateFieldsHaveValues=N

and its work =)

Show
Dmitry added a comment - 22/Mar/10 12:13 PM I use: UseDataDictionary=Y DataDictionary=FIX43.xml ValidateUserDefinedFields=N ValidateFieldsHaveValues=N and its work =)
Hide
Deelo added a comment - 21/Feb/12 3:18 AM

I'm having this problem as well...did anyone figure out a solution?

Show
Deelo added a comment - 21/Feb/12 3:18 AM I'm having this problem as well...did anyone figure out a solution?
Hide
Christoph John added a comment - 21/Feb/12 6:01 PM

Did you already try the suggestions above or the setting ValidateIncomingMessage=Y?

Show
Christoph John added a comment - 21/Feb/12 6:01 PM Did you already try the suggestions above or the setting ValidateIncomingMessage=Y?

People

Vote (4)
Watch (3)

Dates

  • Created:
    11/Feb/09 2:48 AM
    Updated:
    21/Feb/12 6:01 PM
    Resolved:
    06/Apr/10 2:24 AM