[QFJ-705] Redundant ResendRequest is sent after logon when tag 789 based recovery is supposed to be used Created: 17/Sep/12 Updated: 18/Sep/12 Resolved: 18/Sep/12 |
|
| Status: | Closed |
| Project: | QuickFIX/J |
| Component/s: | Engine |
| Affects Version/s: | 1.5.0, 1.5.1, 1.5.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrzej Hajderek | Assignee: | Christoph John |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Hi, It looks like more and more people are experiencing the same issue - tag 789 support is incomplete. Please see: Below I propose a partial fix for the problem. Since it requires only two lines of code it should be easier to accept, assuming it does not break anything else. I propose to make the call to doTargetTooHigh(logon) in in nextLogon(Message logon) conditional: private void nextLogon(Message logon) throws FieldNotFound, RejectLogon, IncorrectDataFormat, The above condition ensures that when tag 789 mode recovery is enabled the ResendRequest will not be sent. In fact some trading platforms do not allow a redundant ResendRequest. I tested this fix with an initiator application connecting to Reuters MAPI FIX (Drop Copy). Regards, |
| Comments |
| Comment by Andrzej Hajderek [ 17/Sep/12 ] |
|
Sorry, the first link should have been: |
| Comment by Christoph John [ 18/Sep/12 ] |
|
Corrected link. |