Details
-
Bug
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
Lotus Bugfest
-
ACQ Sprint 155
-
2
-
Thunderjet
-
Lotus (R1 2022) Bug Fix
-
Implementation coding issue
Description
Overview:
Stopped to save in the DB after 12.04.2022 and applying 1.3.2 bugfix.
In scope of 1.3.2 bugfix only new permission was defined.
Also manual export Jobs are saved without issues.
On the Snapshot envs Job is saved without issues.
Steps to Reproduce:
- Schedule EDIFACT export Job.
Expected Results:
Job scheduled and appeared in the Postgres Database
Actual Results:
Job entity is sent to save in the DB, but is not appeared in the DB.
Interested job UUID please find in logs : 44912f2b-1765-42e0-b954-331cae933d88
mod-data-export-worker_Unknown_Job.log mod-data-export-spring_Unknown_Job.log
Kafka event is sent.
Possible reason
The reason why that happens is that when using the @Transactional annotation, the changes are not committed to the database until the entire method is completed.
Additional Information:
URL:
Interested parties:
TestRail: Results
Attachments
Issue Links
- blocks
-
MODEXPS-92 MODEXPS (mod-data-export-spring) Lotus BF release 1.3.3
-
- Closed
-
- relates to
-
MODEXPS-95 Authtoken required
-
- Closed
-