[FOLIO-2343] Investigate why checkin and checkout 100% failed in perf test Created: 05/Nov/19  Updated: 03/Jun/20  Resolved: 08/Nov/19

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

Type: Task Priority: TBD
Reporter: Hongwei Ji Assignee: Hongwei Ji
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: CP: sprint 76
Story Points: 1
Development Team: Core: Platform

 Description   

See https://jenkins-aws.indexdata.com/job/Automation/job/folio-perf-platform/312/performance/



 Comments   
Comment by Hongwei Ji [ 05/Nov/19 ]

Checkout failed due to

invalid uuid format of location_id, expecting ^[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[1-5][a-fA-F0-9]{3}-[89abAB][a-fA-F0-9]{3}-[a-fA-F0-9]{12}$ but it is null

Checkin failed due to

java.lang.NullPointerException
	at org.folio.circulation.domain.Item.inTransitToHome(Item.java:310)
	at org.folio.circulation.domain.UpdateItem.changeItemOnCheckIn(UpdateItem.java:74)
	at org.folio.circulation.domain.UpdateItem.onCheckIn(UpdateItem.java:33)
	at org.folio.circulation.resources.CheckInProcessAdapter.updateItem(CheckInProcessAdapter.java:93)
	at org.folio.circulation.support.Result.after(Result.java:312)
	at org.folio.circulation.support.Result.combineAfter(Result.java:151)
	at org.folio.circulation.resources.CheckInByBarcodeResource.lambda$checkin$4(CheckInByBarcodeResource.java:98)
	at java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:952)
	at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:926)
	at java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:443)
	at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
	at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
	at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
	at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
Comment by Hongwei Ji [ 08/Nov/19 ]

Errors are due to missing the new "effectiveLocationId" attribute. Updated data set will have it.

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