[FOLIO-1914] SPIKE: edge-rtac broken on folio-snapshot/folio-testing Created: 26/Mar/19  Updated: 03/Jun/20  Resolved: 27/Mar/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P3
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Cannot Reproduce Votes: 0
Labels: devops, platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: Core: Platform - Sprint 60
Story Points: 0.5
Development Team: Core: Platform

 Description   

edge-rtac is responding with an empty response to all requests:

<?xml version='1.0' encoding='UTF-8'?>
<holdings/>

The log for the edge-rtac shows:

14:22:57 INFO  OkapiClient          Successfully logged into FOLIO
14:22:57 INFO  OkapiClient          GET http://10.36.1.211:9130/rtac/a89eccf0-57a6-495e-898d-32b9b2210f2f tenant: diku token: eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJkaWt1IiwidXNlcl9pZCI6IjY3Y2Y5ODFhLWFmZTQtNTJkZi1hYWQxLWFmMjc5OGVhNGRlNCIsImNhY2hlX2tleSI6IjU4NDA4ODc2LTJmMWYtNDJhNC1hM2M4LTIzNzg4YjJjMTIyMCIsImlhdCI6MTU1MzYxMDE3NywidGVuYW50IjoiZGlrdSJ9.KDtMLE2nBGHHeUVZgvKnMPik2bX4r6DeBajwHiqAN4A
14:23:27 ERROR RtacOkapiClient      Exception: The timeout period of 30000ms has been exceeded while executing GET /rtac/a89eccf0-57a6-495e-898d-32b9b2210f2f for host 10.36.1.211
14:23:27 ERROR RtacHandler          Exception calling mod-rtac
java.util.concurrent.CompletionException: java.util.concurrent.TimeoutException: The timeout period of 30000ms has been exceeded while executing GET /rtac/a89eccf0-57a6-495e-898d-32b9b2210f2f for host 10.36.1.211

The log for mod-rtac shows no request ever reaches it.

Further investigation of Okapi logs is required.



 Comments   
Comment by Craig McNally [ 26/Mar/19 ]

Not sure what has changed, but it seems to be working now...

curl "http://folio-testing-backend01.aws.indexdata.com:8000/prod/rtac/folioRTAC?apikey=eyJzIjoicUN4NnBGbGZ1V0VER2kyUVNLYWIiLCJ0IjoiZGlrdSIsInUiOiJkaWt1In0=&mms_id=a89eccf0-57a6-495e-898d-32b9b2210f2f"
<?xml version='1.0' encoding='UTF-8'?>
<holdings>
  <holding>
    <id>bb5a6689-c008-4c96-8f8f-b666850ee12d</id>
    <callNumber>D15.H63 A3 2002</callNumber>
    <location>SECOND FLOOR</location>
    <status>Checked out</status>
    <dueDate>2017-01-19T12:42:21.000+0000</dueDate>
  </holding>
</holdings>
Comment by Wayne Schneider [ 27/Mar/19 ]

I am also unable to reproduce the problem today, either locally or on the hosted reference environments. I will chalk it up to demo gremlins and close the issue.

Generated at Thu Feb 08 23:16:49 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.