ReallyRunning event misinterpreted after resubmit from backlogged WMS (#92612)

[sustr4]

This is a copy of original issue https://savannah.cern.ch/bugs/?92612 by Zdenek Salvet

ReallyRunning event is not handled correctly after deep resubmit
when it arrives earlier then Resubmission event from WMS
(WMS is not able to send events to LB server quickly enough).
"ReallyRunning on bad branch" is logged instead.

Zdenek Salvet

---

How about this? The idea is to perform the same action as for the RESUBMISSION event when the new event is apparently on newer branch (ie. the control went through WM once more), but the RESUBMISSION event itself is missing. I will not pretend I grasp the code fully, so please double check.

diff -u -r1.34 process_event.c
--- process_event.c 14 Dec 2011 10:44:18 -0000 1.34
+++ process_event.c 11 Apr 2012 12:16:30 -0000
@@ -323,8 +323,12 @@
fine_res = RET_GOODBRANCH;
}
else {

• res = RET_LATE;
• fine_res = RET_BADBRANCH;
• if(before_deep_resubmission(js->branch_tag_seqcode, e->any.seqcode)) {
• reset_branch(js, e);
• } else {
• res = RET_LATE;
• fine_res = RET_BADBRANCH;
• }
  }
  }
  else if ((js->last_seqcode != NULL) &&

Michal Vocu