Re: [Quickfix-developers] Tag not defined for this message type !!!
Brought to you by:
orenmnero
From: Kenny S. <ks...@co...> - 2011-10-03 14:45:41
|
Without looking at the data dictionaries, they should just be the same. The goal of the data dictionary is to tell QuickFIX how a counter party has tweaked the protocol. You want to match it with the person you are connecting with. If you have their dictionary, just use it. -- Kenny Stone Connamara Systems, LLC On Mon, Oct 3, 2011 at 8:59 AM, Rasheed Waraich <ras...@gm...>wrote: > Thanks Kenny for quick response. > > Can there be any issue in my data dictionary in this case? > > I am newbie to this QuickFIX world... so, it would be great if you can > guide me what I should fix in my data dictionary.... > > Please find attached with: > > 1) My_DD44.xml > 2) Broker_DD44.xml > > > On Mon, Oct 3, 2011 at 3:48 PM, Kenny Stone <ks...@co...> wrote: > >> If your broker says it should work, sounds like is a problem with them. >> >> The reject is telling you the message is rejects because of field 1. (371 >> is RefTagID). >> >> Do you have the data dictionary setup appropriately? >> >> -- >> Kenny Stone >> Connamara Systems, LLC >> >> >> On Mon, Oct 3, 2011 at 8:37 AM, Rasheed Waraich <ras...@gm... >> > wrote: >> >>> QuickFIX Documentation: >>> http://www.quickfixengine.org/quickfix/doc/html/index.html >>> QuickFIX Support: http://www.quickfixengine.org/services.html >>> >>> >>> >>> Hello Experts, >>> >>> I am sending a "QuoteRequest" message to my broker application and it is >>> 100% according to the provided specifications: >>> >>> 8=FIX.4.4_9=111_35=R_34=2_49=ClientStream_52=20111003-13 >>> :24:52.462_56=ServerStream_1=21281100001_38=1000_55=EURUSD_131=1_146=1_10=076_ >>> >>> But I keep getting "Tag not defined for this message type": >>> >>> 8=FIX.4.4_9=131_35=3_34=2_49=ServerStream_52=20111003-13:24:56.749_56=ClientStream_45=2_58=Tag >>> not defined for this message type_371=1_372=R_373=2_10=029_ >>> >>> Now I can't understand where is the issue. When I talk to broker support >>> they say it should work fine and the message shouldn't be rejected as my >>> QuoteRequest message is according to the specifications. >>> >>> I am badly stuck, it looks to me that its something else which is causing >>> this problem... >>> >>> Can someone guide me how should I debug it? How can I find the issue? >>> >>> Thanks in advance... >>> >>> -- >>> Regards >>> //R >>> >>> >>> ------------------------------------------------------------------------------ >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2dcopy1 >>> _______________________________________________ >>> Quickfix-developers mailing list >>> Qui...@li... >>> https://lists.sourceforge.net/lists/listinfo/quickfix-developers >>> >> >> > > > -- > Thanks > //R > |