RequestForPositions just hangs indefinitely
RequestForPositions just hangs indefinitely
19 Jun 2019, 10:34
Hello,
I have several FIX messages written, and all work completely fine, however I cannot seem to get RequestForPositions to work after a successful logon, I have followed the documentation and even ensured my message is structured exactly as described in the Rules of Engagement example.
Can someone confirm this works for them? If so, could you please take a look at my logs below and help figure out why it might be hanging?
[FIX] SENDING Logon 8=FIX.4.4|9=130|35=A|49=icmarkets.1234567|56=CSERVER|34=1|52=20190619-07:22:42.439|50=Trade|57=TRADE|98=0|108=30|141=Y|553=1234567|554=myPassword|10=005| [FIX] RESPONSE RECEIVED - LOGON COMPLETE. Response Obj ={"beginString":"FIX.4.4","bodyLength":"103","msgType":"A","msgSeqNum":"1","senderCompID":"CSERVER","senderSubID":"TRADE","sendingTime":"20190619-07:22:42.430","targetCompID":"icmarkets.1234567","targetSubID":"Trade","encryptMethod":"0","heartBtInt":"30","resetSeqNumFlag":"Y","checkSum":"123"} [FIX] SENDING RequestForPositions 8=FIX.4.4|9=87|35=AN|49=icmarkets.1234567|56=CSERVER|34=2|52=20190619-07:22:42.525|50=Trade|57=TRADE|710=client-id-20190619-07:22:42.525|10=155|
It just hangs indefinitely here.
Any help would be greatly appreciated, I'll try any suggestions.
Thank you,
Chris
Replies
PanagiotisCharalampous
19 Jun 2019, 11:51
Hi Chris,
If you are not familiar with C# then I don't think it will help you in anyway to run the demo app. The whole point would be to compare your implementation with the example project. Else you will just confirm yourself that the message is correct and that you get a response from the server. In any case, based on the available information, I guess that there should be something wrong with your implementation since everything else seems correct.
Best Regards,
Panagiotis
@PanagiotisCharalampous
Athenum
19 Jun 2019, 12:24
Hi Panagiotis,
I have been troubleshooting my implementation, and I have only reached out here as a final resort because all other FIX messages work fine with the same implementation. The only outlier is this specific FIX endpoint. However I understand you have tested it on your side, so there is not much you can do.
I will continue to troubleshoot all possible scenarios.
Thank you,
Chris
@Athenum
PanagiotisCharalampous
19 Jun 2019, 11:07
Hi Chris,
Thanks for posting in our forum. Your message seems correct. I also tried it with the example application and I had no issues, response is received. Could you try it as well?
Best Regards,
Panagiotis
@PanagiotisCharalampous