Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ExecutionReport with properly configured additional field is erroneously rejected #18

Open
ghost opened this issue Apr 23, 2015 · 0 comments

Comments

@ghost
Copy link

ghost commented Apr 23, 2015

It's very easy to reproduce.

  1. Edit the FIX42.xml file and add field 204 ("CustomerOrFirm") to message type 8 ("ExecutionReport"). Make required = Y so it will show up in the GUI.
  2. Configure an initiator and an acceptor to use one FIX42 session. Connect them.
  3. From the acceptor, send an ExecutionReport. Make sure to correctly populate all of the fields, including CustomerOrFirm.

The initiator will REJECT the message, and the acceptor shows this:

8=FIX.4.2�9=123�35=3�34=187�49=INIT�52=20150423-17:28:03.937�56=ACCEPT�45=188�58=Tag not defined for this message type�371=204�372=8�373=2�10=130�

My quickfix.cfg file for the initiator looks like this:

[default]
FileStorePath=data/messenger/initiator
FileLogPath=log/initiator
ConnectionType=initiator
SenderCompID=INIT
TargetCompID=ACCEPT
SocketConnectHost=localhost
StartTime=00:00:00
EndTime=00:00:00
HeartBtInt=30
ReconnectInterval=5

[session]
BeginString=FIX.4.2
SocketConnectPort=9876

quickfix.cfg for the Acceptor looks like this:

[default]
FileStorePath=data/messenger/acceptor
FileLogPath=log/acceptor
ConnectionType=acceptor
SenderCompID=ACCEPT
TargetCompID=INIT
SocketConnectHost=localhost
StartTime=00:00:00
EndTime=00:00:00
HeartBtInt=30
ReconnectInterval=5

[session]
BeginString=FIX.4.2
SocketAcceptPort=9876

I am on:

java -version
java version "1.7.0_65"
OpenJDK Runtime Environment (fedora-2.5.2.5.fc20-x86_64 u65-b17)
OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants