JDBC exception after DB restarted

Description

Similar to https://folio-org.atlassian.net/browse/MODQM-340

Related:
https://folio-org.atlassian.net/browse/MODRS-189

(mod-entities-links-1.0.2)

 

After a database restart on a production orchid cluster libraries started to experience the following error in mod-quick-marc:
 "record cannot be found or loaded"
Redeploying mod-entities-links resolved the issue as described in this jira: https://folio-org.atlassian.net/browse/MODQM-340

From the logs:

Related:
mod-remote-storage: https://folio-org.atlassian.net/browse/MODRS-189
mod-data-export-worker: https://folio-org.atlassian.net/browse/MODEXPW-451

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

Redeploy mod-entities-links

Checklist

hide

TestRail: Results

Activity

Show:

Mamidi Likhitha December 19, 2023 at 5:33 AM

Hi I tried to replicate the issue but this issue is not reproducible in Poppy. 

cc:

Michelle Suranofsky November 17, 2023 at 1:38 PM

- confirming...we will try to recreate this with poppy.

Khalilah Gambrell November 15, 2023 at 7:20 PM

Thanks . We will not address this issue until it is verified that this issue is happening on a Poppy environment. 

cc:  

Michelle Suranofsky November 14, 2023 at 4:40 PM

- We haven't seen it with poppy....although I don't think we've tried to trigger it in any of the poppy test environments.

Khalilah Gambrell November 14, 2023 at 4:25 PM

Hey   - we are not going to fix for Orchid. Do you want us to fix this issue for Poppy. IOW have you experience this issue with Poppy? 

cc: and  

Cannot Reproduce

Details

Assignee

Reporter

Priority

Story Points

Development Team

Spitfire

Release

Quesnelia (R1 2024)

RCA Group

Not a bug

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created November 13, 2023 at 9:01 PM
Updated February 1, 2024 at 12:52 PM
Resolved December 19, 2023 at 1:20 PM
TestRail: Cases
TestRail: Runs