Imported from previous forum
[ original email was from Chris Snell - Chris.snell@patsystems.com ]
Hi
We are using Registration Instructions (35=o) message to create accounts on one of our FIX gateways, some of the organisations happen to have Turkish Characters and we are having issues with QuickFIX/J accepting them into the system. (Í,ù,û ect)
QuickFIX is rejecting them when we specify them in tag 523 in the message and the reject we get is:
ERROR SocketAcceptorIoProcessor-0.0 quickfix.mina.acceptor.AcceptorIoHandler - Invalid LOGON message, disconnecting: Expected CheckSum=139, Received CheckSum=156
It seems like there are some issues calculating checksum values when special characters are used. The characters are displayed as question marks in the response message.
Has anyone run in to this type of issue before?
Regards
Chris
Hi Chris,
maybe a better place for this question is the QuickFIX/J mailing list: quickfixj-users List Signup and Options
However, if you are using a multi-byte charset (e.g. UTF-8) you might hit one of the following issues:
http://www.quickfixj.org/jira/browse/QFJ-382
http://www.quickfixj.org/jira/browse/QFJ-38
If you are not using a multi-byte charset, you might try to specify the Java options for using ISO-8859-1 encoding and see if that helps:
-Dfile.encoding=ISO-8859-1
You’ll have to specify that option when starting your Java process.
Good luck,
Christoph
Hi
We are using Registration Instructions (35=o) message to create accounts on one of our FIX gateways, some of the organisations happen to have Turkish Characters and we are having issues with QuickFIX/J accepting them into the system. (Í,ù,û ect)
QuickFIX is rejecting them when we specify them in tag 523 in the message and the reject we get is:
ERROR SocketAcceptorIoProcessor-0.0 quickfix.mina.acceptor.AcceptorIoHandler - Invalid LOGON message, disconnecting: Expected CheckSum=139, Received CheckSum=156
It seems like there are some issues calculating checksum values when special characters are used. The characters are displayed as question marks in the response message.
Has anyone run in to this type of issue before?
Regards
Chris
Hi Chris,
Apart from QuickFIX, note that FIX values should always be in ASCII except for encoded fields. There is no existing encoded fields in RegistrationInstructions. So be sure that your Turkish characters are ASCII.
Having said that, your error message seems relating to the Logon message and not to a RegistrationInstructions message…
Regards,
Xavier.
Hi
We are using Registration Instructions (35=o) message to create accounts on one of our FIX gateways, some of the organisations happen to have Turkish Characters and we are having issues with QuickFIX/J accepting them into the system. (Í,ù,û ect)
QuickFIX is rejecting them when we specify them in tag 523 in the message and the reject we get is:
ERROR SocketAcceptorIoProcessor-0.0 quickfix.mina.acceptor.AcceptorIoHandler - Invalid LOGON message, disconnecting: Expected CheckSum=139, Received CheckSum=156
It seems like there are some issues calculating checksum values when special characters are used. The characters are displayed as question marks in the response message.
Has anyone run in to this type of issue before?
Regards
Chris