[QFJ-387] Unsupported Message Type Created: 31/Dec/08 Updated: 20/Mar/11 Resolved: 20/Mar/11 |
|
Status: | Closed |
Project: | QuickFIX/J |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Other | Priority: | Default |
Reporter: | Reaz Ahmed | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Environment: |
DEV |
Description |
I am very new to QuickFixJ. The problem is, When ever we a QuoteReject (msgtype="b"), our system is generating a msgtype="j" with Cauase="Unsupported Message Type". I don't understand why we are generating the message where definition for msgtype="b" and the actual message we receive matches fine. Here is the log extract: 31-12-2008:15:15:45.586,FIX.4.4:TDSECLDNDEV->GSFXDEVPRICES:GSFXDEVPRICES: 8=FIX.4.4^A9=164^A35=b^A34=19^A49=GSFXDEVPRICES^A52=20081231-15:15:45.462^A56=TDS 31-12-2008:15:15:45.588,FIX.4.4:TDSECLDNDEV->GSFXDEVPRICES:GSFXDEVPRICES: Message 4 Rejected: Unsupported Message Type 31-12-2008:15:15:45.588,FIX.4.4:TDSECLDNDEV->GSFXDEVPRICES:GSFXDEVPRICES: 8=FIX.4.4^A9=113^A35=j^A34=49^A49=TDSECLDNDEV^A52=20081231-15:15:45.588^A56=GSFXD Please help. Thank you. Reaz. |
Comments |
Comment by Brad Harvey [ 01/Jan/09 ] |
It sounds like you may be using the message cracker and have not implemented the appropriate method for handling the fix 4.4 quote reject. |
Comment by Reaz Ahmed [ 05/Jan/09 ] |
Brad, As I am new to FIX, could you please elaborate which method I didn't implement? On my class that extends MessageCracker and implements Application I have an implementation for public void onMessage(QuoteRequest aQuoteReqtReject, SessionID aSessionId) where I just print the message received to the log. Is this is the method you are talking about? thanks for your reply. Reaz. |
Comment by Brad Harvey [ 06/Jan/09 ] |
Hi Reaz, Looking in the fix44.xml data dictionary I see this: <message name="MassQuoteAcknowledgement" msgtype="b" msgcat="app">
So I think you'll need to override onMessage(quickfix.fix44.MassQuoteAcknowledgement message, SessionID sessionID) Also make sure you're not calling super.onMessage. Cheers, |