Auto-Reject - Event Log Fehler - CaseId danach unbrauchbar
Description of the bug:
- ...
- ...
- ...
Current behavior:
zur Einordnung: Es geht um die Integration von FitConnect in dem Project KOBAconnect.
Wir mussten leider auf der Testumgebung feststellen das wenn mehrere Nachrichten in kurzer Zeit zu einer CaseId über FitConnect versendet und abgeholt werden, das ein Event-Log Fehler entstehen kann, welcher die Verarbeitung weitere Submissions verhindert. Die CaseId wird damit unbrauchbar und die Einreichung müsste damit erneut gestellt werden. Anbei der Fehler aus dem Log:
{"timestamp":"2025-12-03 12:00:34.345","message":"Auto-rejecting submission due the following problem(s): The Event-Log is inconsistent because it does not contain exactly one 'submit' event.","logger_name":"dev.fitko.fitconnect.client.subscriber.SubmissionReceiver","level":"INFO","submissionid":"caea9df7-549e-4709-a78a-e2660c93ca00","messagetype":"SUBMISSION","caseid":"0d519ad8-9e1a-4aa1-bb32-35c275b8cc72","correlationid":"11405_16eb7c1f-d0b2-42d0-8485-14ab7eadb4cb","destinationid":"3472480b-ceef-4e07-b2de-f2a33e5257d8","caller_class_name":"dev.fitko.fitconnect.client.subscriber.SubmissionReceiver","caller_method_name":"reject","caller_file_name":"SubmissionReceiver.java","caller_line_number":223} Könnten Sie den Fehler prüfen und einordnen ?
Wenn diese Fehlerkonstellation auf der Produktiv-Umgebung zum Pilotierungs-Start am 19.01.26 auftreten kann, benötigen wir dringendst eine Recovery-Strategie die mit allen Fachverfahrensherstellern abgestimmt ist.
Expected behavior:
Environments:
TEST
Additional Information:
Dependency / relationship to other issues:
Responsible person / team:
Transfer history to different teams
Contact persons including contact details:
Screenshots / Logs / Requests:
Checklist:
-
Add Severity label -
Add team label -
Related/affected issues/stories/epics linked and explained in the bug issue -
Creation of an automated test -
Bugfix deployed on DEV -
Bugfix tested on DEV -
Bugfix deployed on TEST -
Bugfix tested on TEST (possibly also by the connection project itself) -
Successful fix reported to Team Operations (Teams channel) -
Bugfix deployed on STAGE -
Bugfix tested on STAGE if necessary -
Bugfix deployed on PROD -
Bugfix tested on PROD (possibly also by the connection project itself) -
Final communication by Team Operations if necessary -
Internal documentation was checked and updated if necessary -
External documentation has been checked and updated if necessary -
Updated changelog if necessary