[OKAPI-740] "Wait for lock" when enabling module (with new timer feature) for supertenant - FOLIO Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: P2
Resolution: Done
Affects Version/s: 2.29.3
Fix Version/s: 2.30.0
Labels:
- back-end
- platform-backlog

Template:
Sprint:
CP: sprint 65
Story Points:
3
Development Team:
Core: Platform

Description

The nightly performance environment uses supertenant as the testing tenant. It has been failed to bootstrap modules since May 30. The log shows it failed at enabling mod-kb-ebsco-java module after the module implemented the new timer feature (https://github.com/folio-org/mod-kb-ebsco-java/pull/150). Chatted with adam, it needs to be looked into.

Okapi log:

20:53:48 INFO  TenantManager        handleTimer tenant=supertenant module=null seq1=0
20:53:48 INFO  OkapiClient          789212/proxy;028586/tenant REQ okapiClient supertenant POST http://172.31.72.156:9225/_/tenant
20:53:48 INFO  TenantManager        wait for lock supertenant_mod-kb-ebsco-java-2.4.0-SNAPSHOT.129_1
20:53:48 INFO  TenantManager        handleTimer done no=1
20:53:48 INFO  TenantManager        wait for lock supertenant_mod-kb-ebsco-java-2.4.0-SNAPSHOT.129_1 returned
20:53:50 INFO  OkapiClient          789212/proxy;028586/tenant RES 201 1290640us okapiClient http://172.31.72.156:9225/_/tenant
20:53:50 INFO  OkapiClient          789212/proxy;045990/tenantpermissions REQ okapiClient supertenant POST http://172.31.72.156:9202/_/tenantpermissions
20:53:50 INFO  OkapiClient          789212/proxy;045990/tenantpermissions RES 201 268499us okapiClient http://172.31.72.156:9202/_/tenantpermissions
20:53:50 INFO  TenantManager        handleTimer tenant=supertenant module=null seq1=0
20:53:50 INFO  OkapiClient          789212/proxy;639914/tenant REQ okapiClient supertenant POST http://172.31.72.156:9226/_/tenant
20:53:50 INFO  TenantManager        wait for lock supertenant_mod-kb-ebsco-java-2.4.0-SNAPSHOT.129_1
20:53:50 INFO  TenantManager        handleTimer done no=1
20:53:51 INFO  OkapiClient          789212/proxy;639914/tenant RES 201 1241089us okapiClient http://172.31.72.156:9226/_/tenant
20:53:51 INFO  OkapiClient          789212/proxy;626654/tenantpermissions REQ okapiClient supertenant POST http://172.31.72.156:9202/_/tenantpermissions
20:53:52 INFO  OkapiClient          789212/proxy;626654/tenantpermissions RES 201 373540us okapiClient http://172.31.72.156:9202/_/tenantpermissions
20:53:52 INFO  OkapiClient          789212/proxy;674054/tenant REQ okapiClient supertenant POST http://172.31.72.156:9227/_/tenant
20:53:52 INFO  TenantManager        handleTimer tenant=supertenant module=null seq1=0
20:53:52 INFO  TenantManager        wait for lock supertenant_mod-kb-ebsco-java-2.4.0-SNAPSHOT.129_1
20:53:52 INFO  TenantManager        handleTimer done no=1
...

mod-kb-ebsco-java log

03 Jun 2019 20:53:48:746 INFO  LogUtil [123504eqId] 172.31.68.108:38146 POST /_/tenant null HTTP_1_1 201 5 1165 tid=supertenant Created 
03 Jun 2019 20:54:48:297 INFO  PostgreSQLConnectionHandler [183055eqId] Connection disconnected - /172.31.73.96:5432

TestRail: Results

Attachments

Issue Links

blocks

FOLIO-2079 folio-perf-test "Timeout has been exceeded" after 3 hours

Closed

Activity

People

Assignee:: Adam Dickmeiss

Reporter:: Hongwei Ji

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 03/Jun/19 9:09 PM

Updated:: 03/Jan/20 2:32 PM

Resolved:: 04/Jun/19 12:24 PM

"Wait for lock" when enabling module (with new timer feature) for supertenant