Skip to content

JSON Metaschema Prüfung für SET Metaschemas abschalten

Zusammenfassung

Follow-Up zu #366 (closed)

Es treten immer noch Fehler wegen nicht geladenen JSON-Schemas auf.

2022-04-11 10:00:36.361  INFO 1 --- [nio-8080-exec-2] d.f.z.service.EventWriterService         : Wrote event log entry 84793c0f-c77c-48fb-a043-3df7c1b04fde for event notify-submission
2022-04-11 10:00:36.404  INFO 1 --- [nio-8080-exec-2] d.f.z.service.EventWriterService         : Wrote event log entry 31dc18f3-3445-4a6f-a892-caed9176f736 for event notify-submission
2022-04-11 10:00:36.427  INFO 1 --- [nio-8080-exec-2] d.f.z.service.EventWriterService         : Wrote event log entry 44818a8c-3a88-4e74-8ce6-c9d57572899f for event notify-submission
2022-04-11 10:02:47.128  WARN 1 --- [nio-8080-exec-5] n.j.jsonschemafriend.SchemaStore         : Failed attempt to auto fetch to resolve: https://json-schema.org/draft/2020-12/schema
2022-04-11 10:02:47.130  WARN 1 --- [nio-8080-exec-5] net.jimblackler.jsonschemafriend.Schema  : No match for https://json-schema.org/draft/2020-12/schema
2022-04-11 10:04:58.198  WARN 1 --- [nio-8080-exec-5] n.j.jsonschemafriend.SchemaStore         : Failed attempt to auto fetch to resolve: https://json-schema.org/draft/2019-09/output/schema
2022-04-11 10:04:58.198  WARN 1 --- [nio-8080-exec-5] net.jimblackler.jsonschemafriend.Schema  : No match for https://json-schema.org/draft/2019-09/output/schema
2022-04-11 10:04:58.260  INFO 1 --- [nio-8080-exec-5] d.f.z.service.SubmissionService          : Submission c95cff90-b728-4c96-b1af-3ad507cdae9f marked as ACCEPTED.
2022-04-11 10:04:58.261  INFO 1 --- [nio-8080-exec-5] d.f.z.service.EventWriterService         : Wrote event log entry cd54f2f4-f231-40dd-ade8-35187ad8dca4 for event accept-submission
2022-04-11 11:00:10.100  INFO 1 --- [io-8080-exec-10] d.f.z.service.SubmissionService          : Submission 533b3f6a-7601-41dd-80e9-f1e96efbdb2d marked as ACCEPTED.
2022-04-11 11:00:10.101  INFO 1 --- [io-8080-exec-10] d.f.z.service.EventWriterService         : Wrote event log entry d3fd4662-8c28-4c5f-85f3-8ef9b5827eaf for event accept-submission
2022-04-11 11:00:10.364  INFO 1 --- [nio-8080-exec-4] d.f.z.service.SubmissionService          : Submission fdec4d81-f7a3-4435-ac5b-7947f0aa53af marked as ACCEPTED.
2022-04-11 11:00:10.365  INFO 1 --- [nio-8080-exec-4] d.f.z.service.EventWriterService         : Wrote event log entry b0fd918f-f15f-4d47-8258-daf62c8ec073 for event accept-submission

Schritte zum Reproduzieren

  1. ...
  2. ...
  3. ...

Wie verhält sich der aktuelle Fehler?

Der Fehler tritt nur im IT.N auf. Der erste Zugriff führt wegen Timeout zu einem 503 Fehler. Beim zweiten Versuch kann die Submission korrekt abgerufen werden.

Was ist das erwartete richtige Verhalten?

Die Submission kann beim ersten Versuch korrekt abgerufen werden.

Relevante Protokolle/Screenshots/Anfragen

Durchführungsplan

Edited by Florian Kaufmann