catbref a316b8a810 Potential HSQLDB deadlock fix ... After opening repository connection with RepositoryManager.getRepostory(), any 'read' from repository (e.g. SELECT) starts the transaction even though HSQLDB documentation states there are no shared/read locks in MVCC concurrency model. The work-around for this is to 'reset' HSQLDB's in-transaction flag by performing a ROLLBACK (Repository.discardChanges) immediately after acquiring the blockchain lock (which is used to ringfence changes that might collide like these). Also adding an extra check to prevent payments to nonexistent AT addresses as it touches Transaction.		2019-04-29 15:18:44 +01:00
..
Payment.java	Potential HSQLDB deadlock fix	2019-04-29 15:18:44 +01:00