Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Does not pass X-Okapi-Request-Id

Description

All business modules that takes request from Okapi should pass on X-Okapi-Request-Id so that the call graph can be established.. mod-inventory does not do that.

Example url: /inventory/items?query=barcode%3D%3D1653577489

2019-09-13 09:45:10,626 INFO ProxyContext 117906/inventory REQ 10.0.2.2:46652 diku GET /inventory/items mod-authtoken-2.3.0-SNAPSHOT.53 mod-inventory-13.1.0-SNAPSHOT.170 2019-09-13 09:45:10,790 INFO ProxyContext 117906/inventory RES 202 163730us mod-authtoken-2.3.0-SNAPSHOT.53 http://10.0.2.15:9132/inventory/items?query=barcode%3D%3D1653577489 2019-09-13 09:45:11,154 INFO ProxyContext 117906/inventory RES 200 363755us mod-inventory-13.1.0-SNAPSHOT.170 http://10.0.2.15:9143/inventory/items?query=barcode%3D%3D1653577489

All intermediate steps omit the 117906 – the top-level request-Id.. From code inspection it appears that org.folio.inventory.support.http.client.OkapiHttpClient never passes on X-Okapi-Request-Id.

See https://folio-org.atlassian.net/browse/CIRC-452?focusedCommentId=107605&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel
for how it should look..

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:
Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Core: Platform

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 13, 2019 at 11:06 AM
Updated January 3, 2020 at 2:22 PM
Resolved September 18, 2019 at 2:07 PM
TestRail: Cases
TestRail: Runs

Flag notifications