Kyriakos Tharrouniatis 7f62046c2f CORDA-3329 Exceptions thrown in raw vault observers can cause critical issues (#5816) ... Observers registered on NodeVaultService#rawUpdates, if they throw an exception when called from serviceHub#recordTransactions and if this exception is not handled by the flow hospital, then this leads to the transaction not being recorded in the local vault. This could get the ledger in an out of sync state. In the specific case this happens within FinalityFlow#notariseAndRecord this leads to the transaction being notarized but not recorded in the local vault nor broadcasted in any counter party. The -failed to be recorded locally- transaction and its output states are not visible to any vault, and its input states not able to consumed by a new transaction, since they are recorded as consumed within the Notary. In this specific case we need not loose, by any means, the current transaction. We will handle all cases by catching all exceptions thrown from serviceHub#recordTransactions, wrapping them with a HospitalizeFlowException and throwing it instead. The flow will get to the hospital for observation to be retried from previous checkpoint on next node restart.		2020-01-24 18:21:07 +00:00
..
dbfcontracts	Fix VaultObserverExceptionTest due to differences between ENT and OS	2019-11-04 09:42:41 +00:00
dbfworkflows	CORDA-3329 Exceptions thrown in raw vault observers can cause critical issues (#5816)	2020-01-24 18:21:07 +00:00