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

https://folio-org.atlassian.net/browse/MODELINKS-158

After a database restart on an Orchid production cluster mod-data-export-worker started recording these errors in the logs.

There were no outages reported related to exporting. Problems were reported with mod-remote-storage and mod-entitities-links.

(mod-data-export-worker-3.0.13)

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

Restart the module.

Checklist

hide

TestRail: Results

Activity

Show:

Magda Zacharska April 25, 2024 at 8:17 PM

Hi - can we close this ticket as “cannot reproduce”?

Michelle Suranofsky March 27, 2024 at 7:19 PM

- I haven’t heard of this being reported lately. It seems to have been triggered in rare cases where we resize a db (for example).

Mikita Siadykh March 27, 2024 at 6:04 AM

hi
is it still an issue? from description it’s not clear how to reproduce (our ranchers go down at night - together with DB, and after restore everything works fine), additionally log that you provided is from mod-entities-links module, not from mod-data-export-worker

Oleksandr Bozhko March 22, 2024 at 8:59 AM

Hi , please update the status of this task.

Mamidi Likhitha December 19, 2023 at 5:41 AM

Hi  

This issue is not reproducible in poppy int environment. But I would also like to mention that, I checked the logs after the start of the poppy bugfest database and found the below error:
"org.springframework.jdbc.CannotGetJdbcConnectionException: Failed to obtain JDBC Connection".

Flagged
Cannot Reproduce

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Firebird

RCA Group

TBD

Affects versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created November 13, 2023 at 9:17 PM
Updated June 20, 2024 at 9:25 PM
Resolved May 9, 2024 at 7:57 PM
TestRail: Cases
TestRail: Runs