Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Test 1. No FH and checking trace of transaction
org.apache.ignite.internal.processors.cache.SafeLogTxFinishErrorTest#testSafeLogTxFinishErrorWithFailureHandler{quote}org.apache.ignite.internal.processors.cache.SafeLogTxFinishErrorTest#testSafeLogTxFinishErrorWithoutFailureHandler{quote}
- Start cluster with no FH, load data, start transaction, start and call {
Unknown macro: {activeTx.logTxFinishErrorSafe}}
- Assert that log information doesn’t contains information about FH and no NPE occurs
- Assert that message starts with Failed completing the transaction: [commit=%s, tx= and tx_id is correct.
Test 2: FH and checking trace of transaction
- Start cluster with FH, load data, start transaction, start and call {
Unknown macro: {activeTx.logTxFinishErrorSafe}
}
- Assert that log information doesn’t contains information about FH and no NPE occurs
- Assert that message starts with Failed completing the transaction: [commit=%s, tx= and tx_id is correct.
Test 3: Failed String.format calling from tx
org.apache.ignite.internal.processors.cache.SafeLogTxFinishErrorTest#testSafeLogTxFinishErrorWithFailureHandlerAndRemoveTxState{quote}- Start cluster with FH, load data, start transaction with txState=null, start and call {
Unknown macro: {activeTx.logTxFinishErrorSafe}
}
- Assert that log information doesn’t contains information about FH and no NPE occurs
- Assert that message starts with Failed completing the transaction: [commit=%s, tx= and tx_id is correct.
Attachments
Issue Links
- is related to
-
IGNITE-11959 NullPointerException If transaction failed and failure handler doesn't configured explicitly
- Resolved
- links to