[Exist-open] eXist 4.5.0 & Journal log files amount limit exceeded

[Kuukka-Härmä R. <Rii...@fi...>]

Hi,

Any advice how to recover from this situation:

2021-03-23 13:51:18,493 [qtp395257482-764] ERROR (TransactionManager.java [lambda$beginTransaction$0]:103) - Failed to create transaction. Error writing to log
file.
org.exist.storage.journal.JournalException: Journal can only support 32767 log files
        at org.exist.storage.journal.Journal.writeToLog(Journal.java:341) ~[exist.jar:4.5.0]
        at org.exist.storage.journal.JournalManager.journal(JournalManager.java:86) ~[exist.jar:4.5.0]
        at org.exist.storage.txn.TransactionManager.lambda$beginTransaction$0(TransactionManager.java:101) ~[exist.jar:4.5.0]
        at org.exist.storage.txn.TransactionManager.withLock(TransactionManager.java:333) [exist.jar:4.5.0]
        at org.exist.storage.txn.TransactionManager.beginTransaction(TransactionManager.java:93) [exist.jar:4.5.0]
        at org.exist.xmlrpc.RpcConnection.withDb(RpcConnection.java:3927) [exist.jar:4.5.0]
        at org.exist.xmlrpc.RpcConnection.withDb(RpcConnection.java:3912) [exist.jar:4.5.0]
        at org.exist.xmlrpc.RpcConnection.retrieveFirstChunk(RpcConnection.java:2242) [exist.jar:4.5.0]
        at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source) ~[?:?]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_152]
        at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_152]
....

Where these journal log-entries/files are written? How database can end up to situation where this file number is exceeded? This database instance is in slave-role in our setup.

configuration for recovery:
<recovery enabled="yes"  group-commit="no"   journal-dir="/data/eXist-4.5.0"  size="100M" sync-on-commit="no"  force-restart="no"  consistency-check="yes"/>

What is not done is that we do not take currently backups from this slave db nor have the consistency checkup task activated in scheduler. Could the exceeding of log entries be caused by that?

Any ideas how to recover (except the obvious clean exist install & restore backup), and to prevent this to happen?

BR, Riina