Hi,
we use BaseX 7.9 and we have the problem that in some (non-replicable) situations no more data is written to the database. The database is still readable. Logfiles are currently not available.
If the problem is known, can changes to properties help?
For us, it is not an option to switch to a newer version of the baseX-DB because API changes would be a huge effort.
Thanks, Dorothea
Hi Dorothea,
On 13. Sep 2017, at 10:06, Steinhauer, Dorothea Dorothea.Steinhauer@proalpha.de wrote:
Hi,
we use BaseX 7.9 and we have the problem that in some (non-replicable) situations no more data is written to the database. The database is still readable. Logfiles are currently not available.
If the problem is known, can changes to properties help?
For us, it is not an option to switch to a newer version of the baseX-DB because API changes would be a huge effort.
Thanks, Dorothea
I think, you would have to detect the pattern that leads to the unwanted behaviour. Maybe the documentation on Transaction Management [1] can help to reason about the problem?
By the way, what do you mean with 'no more data is written to the database'. Never ever again after some situation or during a phase (and later on it possible again)?
Thanks, Alex
[1] http://docs.basex.org/wiki/Transaction_Management#Concurrency_Control
basex-talk@mailman.uni-konstanz.de