Investigation of empty catalog during heavy workload scenario

[alexandrudanciu]

The performance test based on MXD simulating workload generated by different company tiers displays an unexpected behavior. Starting with tier 5 and including tier 6, the OEM returns empty catalogs to the fleet managers although the requested assets exist in the database.

[ciprian-nicuta]

Legacy for the lucky one who gets this task in the future:

So basically for investigating this issue 3 repositories are involved:

• connector - containing the rest endpoint
  connector_changes.patch before applying check out the tag 0.6.3

• tractusx-edc - which uses connector as a dependency
  tractusx-edc_changes.patch before applying check out the tag release/0.7.1

• tutorial-resources - which runs the experiment
  tractusx-tutorial-resources_changes.patch before applying check out the branch jmeter-070-and-backend-service or main if by then it got merged

The patch tractusx-tutorial-resources_changes contains build_connect.sh - this is a file containing building and deploying automation, this is is your starting point use it with your local paths and dockerhub account and make sure you set your images as public after you push them the first time.

Please review this files and only apply the changes if you really need them.