When there are need for resending messages, not all the time resend all messages successfully. Once such an error occurred we checked the message body log and found some of the fix messages were not formed correctly. For example,

8=FIX.4.29=32735=834=122049=INT_SENDER52=20090427-13:31:07.03756=INT_RECEIVER57=fviger6=22.214=10015=CAD17=20090427093035_POW_B_0000088020=029=330=Canadian Equities31=22.232=10037=20090427093035_POW_B_0000088038=10039=144=22.254=155=POW60=20090427-

09:30:35.000150=1151=06100=portfolio=CL2,assettype=Equities10=187=FIX.4.29=32935=834=44549=INT_SENDER52=20090427-13:30:24.76256=INT_RECEIVER57=fviger6=56.5114=10015=CAD17=20090427093019_CNQ_B_0000014520=029=330=Canadian

Equities31=56.5132=10037=20090427093019_CNQ_B_0000014538=10039=144=56.5154=155=CNQ60=20090427-09:30:19.000150=1151=06100=portfolio=CL2,assettype=Equities10=007

It seems that the end of the first message and the start of the second are just messed together.
As we are using this version in production and this has caused several issues. I am wondering whether this issue has been identified and resolved in the newer versions. If not I am afraid we have to seek for a different engine.

Thanks

David