Separates the concerns of Transactions and Recovery #989
Conversation
6818ed5
to
1a88730
Ooops, spoke too early. I tested a different one. Will have a look at this one. |
@wolfgangmm all good? |
I'm struggling to get my usual stress tests running on latest develop due to some API changes. I will report once I succeeded. |
A minor typo in the issue title: s/Seperates/Separates. |
@joewiz Fixed! |
@wolfgangmm We had hoped you would open source your stress tests. Then we could help with such changes :-) |
@adamretter In fact the best and most up to date stress test is currently the one against @joewiz https://history.state.gov site. The code for the entire site is available on github and builds automatically: https://github.com/HistoryAtState/hsg-project. jmeter tests based on real user traffic are here: https://github.com/joewiz/hsg-test/blob/master/src/test/jmeter/combined.jmx. That's basically what I'm testing against most of the time right now. It takes some time to set up, but any stress test which is worth to consider must contain a large amount of data and a representative set of user actions. |
0d90e30
to
9341815
@wolfgangmm any updates on this one? |
I did not forget it and still have the branch running. I'll try to test it as soon as I can. |
…now again possible to run eXist with recovery disabled by setting <recovery enabled="no" ... in conf.xml
9341815
to
39bb9ed
Until now if you set
<recovery enabled="no"...
inconf.xml
then eXist would not start up, instead throwing a series ofNullPointerExceptions
.This occurred because the use of
Txn
has become deeply embedded in eXist, however switching off recovery, would also disable theTransactionManager
(i.e. set it tonull
).This patch seperates the concerns of Transactions and Recovery. Enabling eXist still to work in terms of Transactions, yet just disabling the journal (and recovery of which) when recovery is disabled in
conf.xml
.This PR includes a few pieces of cleanup to related classes, however the main aspect of the change is in the commits: