[QFJ-183] All incoming messages fromApp are being rejected Created: 24/May/07  Updated: 07/Jun/07  Resolved: 07/Jun/07

Status: Closed
Project: QuickFIX/J
Component/s: Message Generation
Affects Version/s: None
Fix Version/s: None

Type: Other Priority: Major
Reporter: Robert Jen Assignee: Steve Bate
Resolution: Fixed Votes: 0
Labels: None
Environment:

NetBeans 5.5
jdk 1.6



 Description   

Thanks for the wonderful quickfixj, and thanks in advance for shedding any light on this.

When receiving incoming messages which conform to spec, my engine rejects all of them. It's the same problem with two similar but separate projects (a 4.2 & a 4.3) with errors like these:

(Message 3 Rejected: Tag not defined for this message type:64)
(Message 46 Rejected: Tag not defined for this message type:55)
(Message 32 Rejected: Tag not defined for this message type:647)
(Message 5 Rejected: Unsupported Message Type)

I have user-defined these problem tags, still same error. My user-defined tags work as per messages I send out.
I get the "tag not defined" or "unsupported message type" or "tag not found" errors depending on how I tweak the data dictionary, but always an error.

Again many thanks in advance,



 Comments   
Comment by Steve Bate [ 25/May/07 ]

Just for clarification, you've defined the problem tags but have you added them to definitions of the messages that will use them?

Comment by Robert Jen [ 28/May/07 ]

On the 4.3 project, the "problem tags" are clearly on spec & defined in data dictionary & require no user definition. So I am puzzled by the error.

On the 4.2 project, the initial error is: Tag Not Found, even after (1) adding the user definition in the body of the java codes. On top of that I manually added the "problem tag" to the data dictionary (2) in the numerical tag definition, then I got a Tag Not Defined error. Then I also added the "problem tag" to the data dictionary (3) in the message definition sesion, which gave me an Unsupported Message Type error.

Thanks again in advance

Generated at Sun May 19 10:03:17 UTC 2024 using JIRA 7.5.2#75007-sha1:9f5725bb824792b3230a5d8716f0c13e296a3cae.