[QFJ-691] But when handling garbled messages and processing the pending queue Created: 12/Jul/12 Updated: 19/Dec/13 Resolved: 19/Dec/13 |
|
Status: | Closed |
Project: | QuickFIX/J |
Component/s: | Engine |
Affects Version/s: | 1.5.0 |
Fix Version/s: | None |
Type: | Bug | Priority: | Critical |
Reporter: | rohit qfj | Assignee: | Unassigned |
Resolution: | Incomplete | Votes: | 0 |
Labels: | None | ||
Environment: |
prod |
Description |
For the below use case, QFJ is not working correctly. Client doesn't send HB messages to server and server always sends TestRequest. 1) Client sends a garbled message. Example 34=35. QFJ just logs the message "invalid checksum or body length" private void nextHeartBeat(Message heartBeat) throws FieldNotFound, RejectLogon, state.incrNextTargetMsgSeqNum(); 7) But, the public void next(Message message) method after calling nextHeartBeat method, it just continue and process the nextQueued(); method as nextHeartBeat just returns and no further checks. Ideally nextHeartbeat should return a boolean flag and action accordingly. This happens due to combination of events. |
Comments |
Comment by rohit qfj [ 12/Jul/12 ] |
This bug is present in the latest 1.5.2 and all other previous branches |
Comment by Christoph John [ 10/Oct/12 ] |
Sorry, could you please be more specific on what you expect? What should happen after the verify method returns and why? Thanks |